Malekhasan
asked on
Exchange server 2007 mailbox database can not be mounted
Hi there,
I can not mount mailbox database, it gives me error: MapiExceptionJeterrorReadV
Event id: 419 Source: ESE
MSExchangeIS (2372) First Storage Group: Unable to read page 33687313 of database D:\EXDatabase\Mailbox Database.edb. Error -1018.
Event id: 454 Source ESE
MSExchangeIS (2372) First Storage Group: Database recovery/restore failed with unexpected error -1018.
Event id: 9518 Source MSEchangeIS
Error Read verification error starting Storage Group /DC=local/DC=MBSJHB/CN=Con
Storage Group - Initialization of Jet failed.
Before one week, i have deleted a lot of transaction logs because i ran out of disk space and then i mounted the database successfully and did windows full backup, circular logging is enabled, i found out that transaction logs are not filing the drive since one week and today i have done a restart and now i can not mount the database any more.
Please help me as soon as possible to fix this issue
I can not mount mailbox database, it gives me error: MapiExceptionJeterrorReadV
Event id: 419 Source: ESE
MSExchangeIS (2372) First Storage Group: Unable to read page 33687313 of database D:\EXDatabase\Mailbox Database.edb. Error -1018.
Event id: 454 Source ESE
MSExchangeIS (2372) First Storage Group: Database recovery/restore failed with unexpected error -1018.
Event id: 9518 Source MSEchangeIS
Error Read verification error starting Storage Group /DC=local/DC=MBSJHB/CN=Con
Storage Group - Initialization of Jet failed.
Before one week, i have deleted a lot of transaction logs because i ran out of disk space and then i mounted the database successfully and did windows full backup, circular logging is enabled, i found out that transaction logs are not filing the drive since one week and today i have done a restart and now i can not mount the database any more.
Please help me as soon as possible to fix this issue
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have tried Eseutil /mh and i have got an error -514 (JET_errBadLogVersion, version of the log file in not compatible with the jet version), i only see three log files in the logs folder, i think i need to regenerate these logs again, what can i do?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had backup one week ago, i have tried eseutil /p on public folder database (44MB) that repaired successfully but i could not mount the database, the mailbox database is (270GB) with 75GB white space so you think it will work?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have only 85GB as free space so you think it is enough?
u will need 110% free space as the db size
ASKER
I do not have that space available so what you suggest?
get an external usb disk an use it as temp location
ASKER
I have checked Microsoft web site and they mentioned that we need 20% for esetutil /p so i will go for it tonight and hopefully it will be repaired tomorrow.
it needs 110% not 20
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
well i need to update my Knowledge base ... last time i checked was back to 2003 times and it was 110%
"Keeping 20 percent of the size of the database files being repaired is suggested, although the size of the temporary file will vary widely depending on the nature of the repairs made."
Real situation may need more free space, then 20%.
Try again eseutil /p to be sure edb is OK.
What error you get while mounting it? Same or new one?
Real situation may need more free space, then 20%.
Try again eseutil /p to be sure edb is OK.
What error you get while mounting it? Same or new one?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
great news
Make sure to delete old logs and check file befor you try to mount it.
If all goes well i suggest you create a new clean db and move all users to it (oops free space issue again on sight). A db that has been repaired with the /p is a db that suffered severe corruption i wldnt trust it as my operational database
Make sure to delete old logs and check file befor you try to mount it.
If all goes well i suggest you create a new clean db and move all users to it (oops free space issue again on sight). A db that has been repaired with the /p is a db that suffered severe corruption i wldnt trust it as my operational database
ASKER
I am planning to move critical users to another storage group and to do Eseutil /p on the repaired Database with temporary bath to a USB external HDD.
well if u do have a usb create a new db on the usb, move all users to it. Delete the old one and move the new edb back to internal disk.
Running eseutil /p again is useless
Running eseutil /p again is useless
ASKER
sorry, i meant i want to run eseutil /d on the repaired database, do you think that i can trust USB in this process and how long is it going to take?
yes u can trust the usb i ve done it many times never had an issue
ASKER
Akhater:
I have 270GB database, 135GB white space, how long do you think it will take from me to move each mailbox to another storage group which will be on USB External HDD then i will redirect the path to the physical HDD after i remove the previous Database and log files, right?
I have 270GB database, 135GB white space, how long do you think it will take from me to move each mailbox to another storage group which will be on USB External HDD then i will redirect the path to the physical HDD after i remove the previous Database and log files, right?
it will take less time than the /p or the /d for sure..
one good thing is that when you create a new database and start moving mailboxes users operation will not be stopped during this time, only the user who's mailbox is being copied will not be able to send/receive all the rest will work fine.
If the USB is a 2.0 and the disk has an external power the time wouldn't be much more than a few hours.
1. create a new storage group (put the log file path on the internal disk)
2. create a new database (put the edb path on the usb disk)
3. make a backup/copy of the edb file (the one us just repaired)
4. enable circular logging on the corrupted database storage group and on the new storage group
5. get-mailbox -database CorruptedDatabase | move-mailbox -targetdatabase newdatabase
6. after it all finishes dismount the old database and delete the edb file (also delete the storage group if it is empty)
7. use the wizard to move back the edb file to the internal disk
8. disable ciruclar logging
if all goes well you have now a brand new database defraged and not corrupted
good luck
one good thing is that when you create a new database and start moving mailboxes users operation will not be stopped during this time, only the user who's mailbox is being copied will not be able to send/receive all the rest will work fine.
If the USB is a 2.0 and the disk has an external power the time wouldn't be much more than a few hours.
1. create a new storage group (put the log file path on the internal disk)
2. create a new database (put the edb path on the usb disk)
3. make a backup/copy of the edb file (the one us just repaired)
4. enable circular logging on the corrupted database storage group and on the new storage group
5. get-mailbox -database CorruptedDatabase | move-mailbox -targetdatabase newdatabase
6. after it all finishes dismount the old database and delete the edb file (also delete the storage group if it is empty)
7. use the wizard to move back the edb file to the internal disk
8. disable ciruclar logging
if all goes well you have now a brand new database defraged and not corrupted
good luck
ASKER
Akhater,
How can we know the extent of corruption? why we can not rely on corrupted database anymore, regarding point no. 6:
6. after it all finishes dismount the old database and delete the edb file.
What about the OAB and other system information in the old DB?
Your help is much appreciated
How can we know the extent of corruption? why we can not rely on corrupted database anymore, regarding point no. 6:
6. after it all finishes dismount the old database and delete the edb file.
What about the OAB and other system information in the old DB?
Your help is much appreciated
if a database has been corrupted I wouldn't rely on it anymore even after repair, it could, of course, serve you for years without issue but I think I'm a bit parano about these stuff.
you have nothing to worry about all the info on the old db will be moved to the new one or else exchange won't let you delete it
(OAB is, by the way, published in the public folder and in the CAS not in the mailbox database)
you have nothing to worry about all the info on the old db will be moved to the new one or else exchange won't let you delete it
(OAB is, by the way, published in the public folder and in the CAS not in the mailbox database)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it should be fine
ASKER
Akhtar,
I have installed Exchange management tool and run eseutil /d but i get an error that jcb.dll is not a windows valid image, please assist me here.
I have installed Exchange management tool and run eseutil /d but i get an error that jcb.dll is not a windows valid image, please assist me here.
ASKER
I run the process on x64 Server so everything went smoothly.
ASKER