In Microsoft Exchange Server environment without CCR cluster or DAG yours databases are not protected enough.
During Exchange Server damage you can lost your databases or those databases can be corrupted after damage.
To recover corrupted database you can try to use Stellar Phoenix Mailbox Exchange Recovery.
Below we present product review:
Introduction
There is always some room for unpredictable behavior when it comes down to managing MS Exchange Server databases. The primary goal of managing these databases is ensuring database availability so that users can get what is required in a timely fashion. Surprisingly, you have to deal with the reality that corruption may creep in your system anytime and disrupt the services for an invariable length of time. Stellar Phoenix Exchange Mailbox Recovery comes in handy at the same time providing you a simple solution to repair the corrupt Exchange databases and ensure continuous uptime of Exchange data. The software helps Exchange administrators handle the most serious scenarios of database corruption and resume normal activity in no time.
Environment
I asked for a full version of the tool to the company and they provided me with a product key for the same. I decided to write a review of the product with an objective to reveal all its positives and negatives.
I planned to prepare a separate system running MS Exchange Server 2007 in a Windows Server 2008 environment. I took different databases showing different types of corruption and throwing database errors. The tests were carried out on each database by running the software and results were examined to know about the program’s capabilities.
Installation
I prepared the new system considering the minimum system requirements for the software. I headed for the company website and downloaded the executable for the demo version. Next, I activated the product by using a serial key that was received on email from the company. The activation needed a working Internet connection and the software managed the rest of the things for me.
Testing Stellar Phoenix Mailbox Exchange Recovery Under Different Corruption Scenarios:
TEST 1: Error code: MapiExceptionBusy: Unable to unmount database
In this test, I took an Exchange database that had an issue with a mailbox store. The database reported an error everytime I tried to dismount it for a clean restart of the Information Store. The error was as follows:
Error code: MapiExceptionBusy: Unable to unmount database. (hr=0x8004010b, ec=-2147221237)
This error indicated that the database had suffered from corruption in the past. I quickly launched Stellar Phoenix Mailbox Exchange Recovery and ran the tool against this database to fix the problem. The software carried out the scan smoothly on the entire database and brought it back to normalcy. I had to wait for a few minutes, but was finally happy to see all the data back in place. The software saved the output in PST files, which was quite disappointing though.
TEST 2: ERROR -1206 Database is Corrupt
This test was a good deal of effort for me as the database I took had something structurally wrong with it. The scenario was like this:
I had configured to run a VSS FULL BACKUP, but the process failed with an error. Next, I dismounted the store to run ISINTEG -ALLTESTS to examine this database. The process failed and aborted at TEST 5. When I ran ESEUTIL /G to check its integrity, the following error was reported:
ERROR -1206 Database is Corrupt
Now, I opened Stellar Phoenix Mailbox Exchange Recovery and let it do the repair job. The software performed the scan to completion without a hitch and had me see all the data in its interface screen. I saw the mail items all intact while previewing the database in the application. And, after saving the recovered data to my desired destination, I got this message:
‘Mailbox Recovered Successfully‘
The software surprised me this time also by performing a flawless recovery of a seemingly unrepairable Exchange database.
Test 3: ERROR: database was not shutdown cleanly (dirty shutdown)
The error above is a fair occurrence with all Exchange users. So, I decided to go ahead with this one. The error indicates dirty or disgraceful shutdown of the Exchange Server. The database was in a dirty shutdown state after the Exchange was forced to shut down because of a problem. The command ‘eseutil /r <log file name>’ was run against the database, which failed due to dirty shutdown and gave the following error message:
Error -550 (JET_errDatabaseDirtyShutdown, Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown.)
Following it, I gave this tool a try at making the necessary repairs to restore the database to a healthy state. I chose to do a ‘Deep Scan’ with the tool. However, the results were not as what the previous tests have showed till now. The process winded up quickly recovering most (not all) of the mailbox items from the database. This was quite expected of the tool as the corruption in the database was severe. Due to dirty shutdown, the mailbox store was all messed up. Though the software failed the test, but did a decent job at recovery.
Test 4: Bad page link (error -327)
The next test was intended to fix problems at the Information Store level. I took a database that had some kind of logical corruption and raised event id 447 in the Application log on the Windows 2008 Server. The details of the error are shown below:
MSExchangeIS (5036) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 19, PgnoRoot: 50) of database D:\Exchange\Mailbox Database.edb
This database failed the Isinteg test. I also did a hard repair, but it did not do any needful and the database was in the same inconsistent state. I launched Stellar Phoenix Mailbox Exchange Recovery and ran the software against the corrupt file. The software proved its worth this time also by reading maximum information off the troubled database. There were only one or two mailbox items that couldn’t be seen here. The tool did a phenomenal job in recovering rest of the database file.
Technical Support
The Technical Support staff of Stellar Data Recovery relentlessly provided me assistance in carrying out these repair procedures. They helped me behind the scenes in making this review a success. I appreciate their commitment to understanding customer feedback and developing cutting-edge solutions for the big industry.
Conclusion
After going through a detailed evaluation of the product, I found that Stellar Phoenix Mailbox Exchange Recovery is a promising choice to go for. Most data recovery apps are hit and miss, but this software edged out the other competing products. The tool seemed easy, fast, and successful in almost every test that was performed for analysis. The tool is reasonably priced given its unique capabilities and a wide array of advanced recovery features. An inherent disadvantage of the tool is it repairs STM files only when they are placed in the same folder as the EDB files. Additionally, it gives the output as Outlook PST files and does not support the latest MS Exchange 2013.
Ratings
| Category | Rating | Comment |
| Ease of Use | 5 | Incorporates a good range of flexible options for users |
| Feature Set | 4 | Includes a variety of features for improved scalability |
| Lack of Bugs | 5 | Did not find any |
| Technical Support | 5 | Phenomenal service that guided me throughout |
| Documentation | 5 | Gives a better and detailed understanding of the product |
| Performance | 4 | Exceptional |
| Installation | 5 | Took a few mouse clicks, the software managed it quite easily |
| Learning Curve | 5 | Easy for the first timers |
| Overall | 4 | An reliable piece of utility for all Exchange users |
English 
polski