Limitations of eseutil /p in Repairing Exchange Database
Andrew Watson
July 31, 2008
The MS Exchange Server database corruption can be result of the range of the reasons. But handling each of the situations is mandatory. For the EDB recovery, Microsoft has availed the users an inbuilt utility –eseutil/p.
The eseutil/p is the repair mode for the MS Exchange Sever. This mode corrects some of the database corruption problems and hence enables Exchange recovery. This inbuilt utility works at the page and the ESE (Extensive Storage Engine) table level but not at the application level. The repair goes through the database and checks the critical structures and damaged pages inside the database. After the repair, for the application-level repair, the ISInteg utility must be used.
But the hard fact is that the utility has some limitations which restrict its usage in some of the circumstances. Some of them are enlisted below:
One of the major disadvantages is that if this finds any damaged page then it deletes it. Any of the relevant information may get lost in this case like an e-mail message, a calendar appointment and even a part of the system table.
The utility is unable to perform Exchange Server recovery if the database is in the dirty shutdown state. The utility demands the clean shutdown state to repair.
The incorrect procedures carried out during the run of the command can lead to the severe not repairable exchange database corruption situations.
Next limitation is the time consuming nature of the scanning procedure. The repair runs at about 4 to 6 GB per hour and thus eats much valuable time and for the ISInteg, speed is 3 to 6 GB per hour.
Thus the limitations indicate that the application of the utility will not give the useful results, if applied. The repaired database is not productive as it is not complete and also the time which is used may be disastrous. If some of the business related demands get generated during this long period of repair time then the results could be hazardous to the business if not got fulfilled.
Thus this is required that some other alternative must be considered that can end at the perfect EDB recovery. This alternative comes in the form of the Exchange Server Recovery software which, without altering the contents of the database, repair it intact.
These software are applicable in each case of the database corruption, contrary to the eseutil/p which is not applicable at the dirty shutdown state. The interactive user interface of these Exchange recovery software makes the part of the users quite simple as they need not to put much efforts in knowing the technical details to use the software.
Stellar Phoenix Mailbox Exchange Recovery is the most developed and accepted utility for Exchange Server recovery. The software makes use of the best algorithms for scanning of the corrupted database and ends up at the perfect and complete EDB recovery.
The recovered data will get stored in the PST file format and thus usable with MS outlook. You can use this software with Microsoft Exchange Server 5.5, 2000 and 2003.
The eseutil/p is the repair mode for the MS Exchange Sever. This mode corrects some of the database corruption problems and hence enables Exchange recovery. This inbuilt utility works at the page and the ESE (Extensive Storage Engine) table level but not at the application level. The repair goes through the database and checks the critical structures and damaged pages inside the database. After the repair, for the application-level repair, the ISInteg utility must be used.
But the hard fact is that the utility has some limitations which restrict its usage in some of the circumstances. Some of them are enlisted below:
One of the major disadvantages is that if this finds any damaged page then it deletes it. Any of the relevant information may get lost in this case like an e-mail message, a calendar appointment and even a part of the system table.
The utility is unable to perform Exchange Server recovery if the database is in the dirty shutdown state. The utility demands the clean shutdown state to repair.
The incorrect procedures carried out during the run of the command can lead to the severe not repairable exchange database corruption situations.
Next limitation is the time consuming nature of the scanning procedure. The repair runs at about 4 to 6 GB per hour and thus eats much valuable time and for the ISInteg, speed is 3 to 6 GB per hour.
Thus the limitations indicate that the application of the utility will not give the useful results, if applied. The repaired database is not productive as it is not complete and also the time which is used may be disastrous. If some of the business related demands get generated during this long period of repair time then the results could be hazardous to the business if not got fulfilled.
Thus this is required that some other alternative must be considered that can end at the perfect EDB recovery. This alternative comes in the form of the Exchange Server Recovery software which, without altering the contents of the database, repair it intact.
These software are applicable in each case of the database corruption, contrary to the eseutil/p which is not applicable at the dirty shutdown state. The interactive user interface of these Exchange recovery software makes the part of the users quite simple as they need not to put much efforts in knowing the technical details to use the software.
Stellar Phoenix Mailbox Exchange Recovery is the most developed and accepted utility for Exchange Server recovery. The software makes use of the best algorithms for scanning of the corrupted database and ends up at the perfect and complete EDB recovery.
The recovered data will get stored in the PST file format and thus usable with MS outlook. You can use this software with Microsoft Exchange Server 5.5, 2000 and 2003.
Print
Email
