Exchange Server users usually face errors when they are working on Exchange database. Let us consider a situation when user is about to extract an important file from the database and then system starts showing corruption errors.
For this moment user can run following commands to recover Exchange database:-
There are some default utilities that are stored in exchsvr\bin directory. Eseutil and Isinteg are the utilities that come with Exchange Server automatically.
User can move all the log files from the Transaction logs folder location and try to mount the stores.
For Dirty Shutdown:-
Then user should check the state of Log files. To examine that the log files that are required are in a Clean state, user can run Eseutil /ml command with Path of the log files\log prefix”. This command will help user to check the health of all the log files in the current location.
If the log files are healthy and there is no corruption, then perform the Soft recovery with the command Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database”.
Once the command completes successfully, mount the stores.
It may be possible when user run these commands this following error message will appear on the screen:
“Operation terminated with error -1216”
If user wants to resolve this on his basis then he can run soft recovery with the “/i ” switch.
ISINTEG Utility:- It helps to identify database as ESE database and verify all database tables, records and indexes.
If these utilities are not enough helpful for effective Exchange Server recovery then user must switch to a commercial third party tool like Stellar Phoenix Exchange Server Recovery software that comes at an affordable rate and provide excellent recovery from damage.
For this moment user can run following commands to recover Exchange database:-
There are some default utilities that are stored in exchsvr\bin directory. Eseutil and Isinteg are the utilities that come with Exchange Server automatically.
- Eseutil/p:- It repairs corrupted database.
- Eseutil/r:- It helps in recovering database.
- Eseutil/g:- It verifies the integrity of the database.
- Eseutil/d:- It performs offline compaction of the database.
- Eseutil/y:- It copies database streaming file or log file.
- Eseutil /mh:- It shows path of the database and checks the state of the database.
- Eseutil/c:- It restores information.
User can move all the log files from the Transaction logs folder location and try to mount the stores.
For Dirty Shutdown:-
Then user should check the state of Log files. To examine that the log files that are required are in a Clean state, user can run Eseutil /ml command with Path of the log files\log prefix”. This command will help user to check the health of all the log files in the current location.
If the log files are healthy and there is no corruption, then perform the Soft recovery with the command Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database”.
Once the command completes successfully, mount the stores.
It may be possible when user run these commands this following error message will appear on the screen:
“Operation terminated with error -1216”
If user wants to resolve this on his basis then he can run soft recovery with the “/i ” switch.
ISINTEG Utility:- It helps to identify database as ESE database and verify all database tables, records and indexes.
If these utilities are not enough helpful for effective Exchange Server recovery then user must switch to a commercial third party tool like Stellar Phoenix Exchange Server Recovery software that comes at an affordable rate and provide excellent recovery from damage.