We use Data Protector 6.11 to backup our exchange server 2007 MB.Everything was fine, but then Exchange Full backup sessions started to hang at the end of backup sessions. I had to abort the sessions manualy. We tried to restore but got the following result:
[Normal] From: RSM@BackupServerXXXX.XXX "" Time: 9/1/2011 22:35:15 Restore session 2011/XX/XX-XX started. [Critical] From: OB2BAR_main@Exchange2007Server "Microsoft Exchange Server (Microsoft Information Store)" Time: 9/1/2011 10:35:17 PM Specified object could not be restored. It is missing or could be corrupted. [Normal] From: RMA@BackupServerXXXX.XXX "LTO 5" Time: 9/1/2011 22:36:26 STARTING Media Agent "LTO 5" [Normal] From: RMA@BackupServerXXXX.XXX "LTO 5" Time: 9/1/2011 22:36:30 By: UMA@BackupServerXXXX.XXX@Changer2:0:14:1 Loading medium from slot XX to device TapeTapeX:Y:ZZ:MM [Normal] From: RMA@BackupServerXXXX.XXX "LTO 5" Time: 9/1/2011 22:39:07 Drive based decryption enabled. [Normal] From: OB2BAR_DatabaseStore1 MBX@Exchange2007Server "Microsoft Exchange Server (Microsoft Information Store)" Time: 9/1/2011 22:39:09 Starting OB2BAR Restore: Exchange2007ClusterInstancexxx.xxxx:/Microsoft Exchange Server (Microsoft Information Store)/DatabaseStore1/STORE/Database MBX/0 "MSESE" [Normal] From: OB2BAR_DatabaseStore1 MBX@Exchange2007Server "Microsoft Exchange Server (Microsoft Information Store)" Time: 9/1/2011 23:38:22 Completed OB2BAR Restore: Exchange2007ClusterInstancexxx.xxxx:/Microsoft Exchange Server (Microsoft Information Store)/DatabaseStore1/STORE/Database MBX/0 "MSESE" [Major] From: OB2BAR_DatabaseStore1@Exchange2007Server "Microsoft Exchange Server (Microsoft Information Store)" Time: 9/1/2011 23:38:23 Aborting connection to RSM. Abort code 6. [Normal] From: RSM@BackupServerXXXX.XXX "" Time: 9/1/2011 23:38:28 OB2BAR application on "Exchange2007ClusterInstancexxx.xxxx" disconnected. [Normal] From: RMA@BackupServerXXXX.XXX "LTO 5" Time: 9/1/2011 23:39:54 By: UMA@BackupServerXXXX.XXX@Changer2:0:14:1 Unloading medium to slot XX from device TapeX:Y:ZZ:MM [Normal] From: RMA@BackupServerXXXX.XXX "LTO 5" Time: 9/1/2011 23:40:18 COMPLETED Media Agent "LTO 5"
============================================================================ Session completed with failures!
At the end we have a restored database in dirty shutdown state, but no logs at all.(logs that were created at the time of database backup process). Hard Recovery is painful.
Someone with similar problem? Thanks in advance.
Best Regards,
< Message edited by neconnn -- 5.Aug.2011 10:16:00 AM >
Yes, hard recovery (eseutil /p) is painful as users have to face some precious data loss problems after completing the process. If you do not want to run hard repair process, then you can take help of a third party tool to repair corrupt Exchange database file. Third party applications are designed with advance scanning technology to scan the damaged database bit by bit; if it finds any, they will repair them. Thus, after using third party tool , there is chance that you can get upto 100 % data. One such advance and globally used application that you may use, is:http://www.recover-computerdata.com/exchange-server-recovery.html This Exchange database recovery software help you to repair and rebuild the damaged database files.
I understand problem which you describe here and after reading all at the end I wish to recommend you a technically advance, cheap and Best EDB to PST converter. You can try this or get service from there to access all damaged and corrupted data as healthy format. Exchange Recovery can give you zero percent data lose surety. You can get more about Best EDB to PST (as user's view) tool here. http://www.edbpst.biz
_____________________________
Yasar Arafat Business Development Manager at Exchange Recovery
exchange server recovery corrupted/unreadable exchange folders, messages and rest data are damaged by power shortages or surges, physical damage and incorrect user's actions. Program finds out, analyzes and restore crashed exchange data. It uses step-by-step wizard, which allows you to control the recovery options and go back any time to make the necessary changes.