Re: Missing Mails after Repair

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes, there is no doubt about that, last backup is 2 months old and they deleted logs files just coz they are ******* ...

Im trying to find them a solution, as best as possible, but telling them that the /p deleted 90% of their mails seems impossible, i dont understand why the database weight 150gb and only has 5gb in mails.
They have to be there, just need a way to "read" them....

Ideas?

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message news:%23qLhIO4HKHA.4168@xxxxxxxxxxxxxxxxxxxxxxx
well, yes, in circumstances like that, it's pretty much your only option, but why on earth was there no backup? and who is deleting transaction log files? I hope they learn some things from that incident...

--
Susan Conkey [MVP]



"Christian" <creizlein@xxxxxxxxxxx> wrote in message news:C1A55A5C-D5F9-4703-91C6-C4F91B5567FF@xxxxxxxxxxxxxxxx
i dont understand how can i issue a move mailbox if the database is not clean.... i found no other way than run the /p

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message news:eofCj43HKHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
eseutil /p almost always results in lost data...you'd have been much better off moving all the mailboxes to a new mailbox store/s...but doing that now will have no effect, and won't recover data. Can you restore the old database (prior to having run eseutil)? what made you decide to run eseutil /p? that is widely considered a last ditch effort, when no backup is available and/or you cannot (for some reason) move the mailboxes...

--
Susan Conkey [MVP]



"Christian" <creizlein@xxxxxxxxxxx> wrote in message news:BD36CCC1-DED2-4E3A-9DB1-BC61B81A380F@xxxxxxxxxxxxxxxx
I still with some issues after i had to run a eseutil /p on out mailbox database.
Basically, /p completed fine, then i run a /d which reduced the EDB size from 180gb to 150gb (maybe normal) and then i run isinteg -fix alltests

After all that, i was able to mount the database just fine, but what i discovered is that all the mailbox have less than 80% of the actuall mails they should have, i mean, they only have 100 mails for example when they are suposed to have 10000 ?

The odd thing is that the EDB still weight 150gb, i did run a defrag again on the database (after isinteg, which fixes some errors) but it still weights 150gb, so look like the mails "are there" but they are not visible for OWA....

Any ideas what i can do? is this a normal issue?

Andy David, you commented on my previous post that i should move the mailboxes to a new store and dont use the repaired database... if i move the mailboxes will all the emails come back? :)







.

Relevant Pages

  • Re: Exchange filling up my hard disk
    ... differential backup. ... the backup put duplicate messages back into the mailboxes. ... Because the database grown so rapidly we decided to do an offline ... Exchange database so 1) the log files are purged, ...
    (microsoft.public.exchange.admin)
  • Re: Exchange filling up my hard disk
    ... I was really not familiar with the ID "brick-level" backup. ... the backup put duplicate messages back into the mailboxes. ... Because the database grown so rapidly we decided to do an offline ...
    (microsoft.public.exchange.admin)
  • Re: Backups, Logs, Databases.. Logs written when? Serious Problem
    ... server the log size will continue to grow and the database size wont shrink ... If I run a full backup server will shut down? ... Do I need to move some mailboxes off ...
    (microsoft.public.exchange.admin)
  • Re: Exchange filling up my hard disk
    ... differential backup. ... the backup put duplicate messages back into the mailboxes. ... mailboxes where empty when the restore occurred. ... I used ESEUTIL with the /p option so the original database was preserved ...
    (microsoft.public.exchange.admin)
  • Re: Missing Mails after Repair
    ... why the database weight 150gb and only has 5gb in mails. ... The odd thing is that the EDB still weight 150gb, ... mailboxes to a new store and dont use the repaired database... ...
    (microsoft.public.exchange.admin)