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