Forum Discussion

Zing's avatar
Zing
Level 3
9 years ago

Exchange Restore is failing with 2810 status

Hi All,

Exchange restore is failing due to below error, seeking help from experts to fix the issue ...

Master server :- 7.5.0.7 W2k8

Media:- 7.5 2k3

Client :- 7.5.0.7 W2k8 with Exchange 2010 .

Restore path :- 

Actual Path:- 

Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\DB03\

 

Given Restore path as:-

Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\RDB_NEW\

Restore Log from Activity Monitor :-

23/03/2017 14:13:29 - begin Restore
23/03/2017 14:13:31 - media 123456 required
23/03/2017 14:13:31 - restoring image DAG_1488062678
23/03/2017 14:13:38 - Info bprd(pid=3244) Restoring from copy 1 of image created 02/25/17 22:44:38
23/03/2017 14:13:41 - Info bpbrm(pid=9496) XXXXX is the host to restore to
23/03/2017 14:13:41 - Info bpbrm(pid=9496) reading file list from client
23/03/2017 14:13:46 - connecting
23/03/2017 14:13:46 - Info bpbrm(pid=9496) starting bptm
23/03/2017 14:13:56 - Info tar32(pid=14680) Restore started
23/03/2017 14:13:56 - connected; connect time: 00:00:10
23/03/2017 14:13:56 - Info bptm(pid=12064) start
23/03/2017 14:13:56 - started process bptm (12064)
23/03/2017 14:13:56 - Info bpdm(pid=12064) reading backup image
23/03/2017 14:13:56 - Info bptm(pid=12064) using 64 data buffers
23/03/2017 14:13:56 - Info bptm(pid=12064) spawning a child process
23/03/2017 14:13:56 - Info bptm(pid=12064) child pid: 8444
23/03/2017 14:13:56 - Info bptm(pid=8444) start
23/03/2017 14:13:56 - started process bptm (8444)
23/03/2017 14:13:58 - requesting resource 123456
23/03/2017 14:13:58 - granted resource 123456
23/03/2017 14:13:58 - granted resource HP.ULTRIUM5-SCSI.007
23/03/2017 14:13:59 - mounted
23/03/2017 14:13:59 - Info bptm(pid=12064) XXXX
23/03/2017 14:14:01 - Info bptm(pid=12064) INF - Waiting for positioning of media id 0288L5 on server xxx for reading.
23/03/2017 14:14:01 - positioning 123456 to file 337
23/03/2017 14:15:09 - positioned 123456; position time: 00:01:08
23/03/2017 14:15:11 - begin reading
23/03/2017 14:15:17 - Info bptm(pid=12064) waited for empty buffer 1 times, delayed 1 times
23/03/2017 14:15:17 - end reading; read time: 00:00:06
23/03/2017 14:15:17 - Info bptm(pid=12064) completed reading backup image
23/03/2017 14:15:17 - Info bptm(pid=12064) EXITING with status 0 <----------
23/03/2017 14:15:24 - Error bpbrm(pid=9496) from client XXXXX ERR - Aborting restore: Error writing Exchange object: Microsoft Exchange Database Availability Groups:\DAG\Microsoft Information Store\RDB_NEW\Logs_1487988957 Error: BEDS 0x0:
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status 5
23/03/2017 14:15:24 - restored image DAG_1488062678 - (tar did not find all the files to be restored(185)); restore time 00:01:53
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status: 185
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status: 185: tar did not find all the files to be restored
23/03/2017 14:15:24 - Error bpbrm(pid=9496) client restore EXIT STATUS 185: tar did not find all the files to be restored
23/03/2017 14:15:25 - end Restore; elapsed time: 00:01:56
MS-Exchange-Server policy restore error(2810)

Restore Log from BAR GUI:-

 

 


14:13:06 23/03/2017: Restore Started

14:13:31 (4287238.xxx) Media id 123456 is needed for the restore.

14:13:38 (4287238.001) Restoring from copy 1 of image created 25/02/2017 22:44:38
14:13:58 (4287238.001) INF - If Media id 123456 is not in a robotic library administrative interaction may be required to satisfy this mount request.
14:14:00 (4287238.001) INF - Waiting for positioning of media id 123456 on server xxxxx for reading.
14:15:10 (4287238.001) INF - Beginning restore from server xxxxx to client xxxxx
14:15:18 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\
14:15:18 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\DAG01\
14:15:18 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\
14:15:18 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\DB03\
14:15:18 (4287238.001) MNR - The file was renamed to the following:
14:15:18 (4287238.001) UTF - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\RDB_NEW\
14:15:24 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\DB03\Database
14:15:24 (4287238.001) MNR - The file was renamed to the following:
14:15:24 (4287238.001) UTF - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\RDB_NEW\Database
14:15:24 (4287238.001) TAR - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\DB03\Logs_1487988957
14:15:24 (4287238.001) MNR - The file was renamed to the following:
14:15:24 (4287238.001) UTF - Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\RDB_NEW\Logs_1487988957
14:15:24 (4287238.001) (4287238.001) ERR - Aborting restore: Error writing Exchange object: Microsoft Exchange Database Availability Groups:\DAG01\Microsoft Information Store\RDB_NEW\Logs_1487988957 Error: BEDS 0x0:
14:15:24 (4287238.001) (4287238.001) INF - TAR EXITING WITH STATUS = 5
14:15:24 (4287238.001) (4287238.001) INF - TAR RESTORED 5 OF 6 FILES SUCCESSFULLY
14:15:24 (4287238.001) (4287238.001) INF - TAR KEPT 0 EXISTING FILES
14:15:24 (4287238.001) (4287238.001) INF - TAR PARTIALLY RESTORED 0 FILES

14:15:24 (4287238.001) Status of restore from copy 1 of image created 25/02/2017 22:44:38 = tar did not find all the files to be restored

14:15:25 INF - Server status = 2810
14:15:25 (4287238.xxx) INF - Status = MS-Exchange-Server policy restore error.

14:15:25 INF - Server status = 5
14:15:25 Status of restore from copy 1 of image created 25/02/2017 22:44:38 = the restore failed to recover the requested files

14:15:25 The following files/folders were not restored:
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/DAG01/
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/DAG01/Microsoft Information Store/
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/DAG01/Microsoft Information Store/DB03/
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/DAG01/Microsoft Information Store/DB03/Database
14:15:25 UTF - /Microsoft Exchange Database Availability Groups/DAG01/Microsoft Information Store/DB03/Logs_1487988957

14:15:25 (4287237.xxx) INF - Status = the restore failed to recover the requested files.

3 Replies

Sort By
  • Michal_Mikulik1's avatar
    Michal_Mikulik1
    Moderator
    9 years ago

    Hello,

    you cannot simply redirect Exchange restore to another new database. Refer to chapter "About Exchange server-directed and redirected restores " in documentation.

    Most likely reason is that RDB_NEW database does not exist or it is not flagged as Recovery Database.

    Regards

    Michal

  • Lowell_Palecek's avatar
    Lowell_Palecek
    Level 6
    9 years ago

    If your troubles persist after checking the prior suggestions, please provide a verbose tar log from the Exchange server where the restore is being attempted.

    Whenever you get a client-side error on backup or restore, please always look in the relevant client log for the root error. The error that bubbles up to the job details, the progress log in the BAR GUI, or the server-side logs is often the culmination or summary of an earlier error. Checking the client log should be your first resort, not your last.

    Note: For Windows clients, there are two log levels to set in the host properties. There is the 0 to 5 Global Logging Level on the Logging page, and the 0 to 2 "General level" on the Windows Client / Client Settings page. In the Windows BAR GUI, under Troubleshooting, these levels are called Verbose and General, respectively. Please set them both to their max to find the root error.

  • manatee's avatar
    manatee
    Level 6
    9 years ago

    make sure the destination exists and you have write access to it. also if the hd space is enough to accomodate restoring the whole db.

    and also read up on the above recommended documentation.