Video Screencast Help

Exchange 2010 backups getting failed with 2810

Created: 07 Nov 2013 • Updated: 07 Nov 2013 | 6 comments
This issue has been solved. See solution.

Exchange 2010 backups getting failed with 2810, please advice.

11/07/2013 06:03:51 - Info bptm (pid=4916) INF - Waiting for mount of media id CA4260 on server kek3bkvnnp01 for reading.
11/07/2013 06:03:51 - requesting resource CA4260
11/07/2013 06:03:51 - granted resource  CA4260
11/07/2013 06:03:51 - granted resource  HP.ULTRIUM3-SCSI.003
11/07/2013 06:04:34 - mounted CA4260; mount time: 0:00:43
11/07/2013 06:04:34 - Info bptm (pid=4916) CA4260
11/07/2013 06:04:34 - Info bptm (pid=4916) INF - Waiting for positioning of media id CA4260 on server kek3bkvnnp01 for reading.
11/07/2013 06:04:34 - positioning CA4260 to file 3
11/07/2013 06:05:14 - positioned CA4260; position time: 0:00:40
11/07/2013 06:05:14 - begin reading
11/07/2013 06:05:33 - Info bptm (pid=4916) waited for empty buffer 0 times, delayed 0 times
11/07/2013 06:05:33 - end reading; read time: 0:00:19
11/07/2013 06:05:33 - positioning CA4260 to file 6
11/07/2013 06:06:17 - positioned CA4260; position time: 0:00:44
11/07/2013 06:06:17 - begin reading
11/07/2013 06:20:59 - Error bpbrm (pid=11788) from client NAV8EMDAGP01: ERR - All Exchange databases must be manually dismounted prior to attempting the restore (or select Dismount in restore GUI).
11/07/2013 06:20:59 - Error bpbrm (pid=11788) from client NAV8EMDAGP01: ERR - Aborting restore: Error writing Exchange object: Microsoft Exchange Database Availability Groups:\ASCORP-DAG-1.ASROOT.ADS\Microsoft Information Store\Recovery Database\ Error: BEDS 0x0:
11/07/2013 06:20:59 - Info tar32 (pid=10156) done. status 5
11/07/2013 06:20:59 - Info tar32 (pid=10156) done. status: 185
11/07/2013 06:20:59 - Error bptm (pid=12084) cannot write data to socket, 10054
11/07/2013 06:20:59 - Error bptm (pid=12084) The following files/folders were not restored:
11/07/2013 06:20:59 - Error bptm (pid=12084) UTF - /Microsoft Exchange Database Availability Groups/ASCORP-DAG-1.ASROOT.ADS/Microsoft Information Store/General Users - India (G-L)/Database
11/07/2013 06:21:00 - Info bptm (pid=4916) EXITING with status 24 <----------
11/07/2013 06:21:00 - restored from image ASCORP-DAG-1_1378512889; restore time: 0:17:55
11/07/2013 06:21:00 - end Restore; elapsed time 0:18:00
11/07/2013 06:21:05 - Info tar32 (pid=10156) done. status: 24: socket write failed
11/07/2013 06:21:05 - Error bpbrm (pid=11788) client restore EXIT STATUS 24: socket write failed
MS-Exchange policy restore error  (2810)
 

Operating Systems:

Comments 6 CommentsJump to latest comment

Nicolai's picture

Are you trying to overwrite an active exchange database ?

 Error bpbrm (pid=11788) from client NAV8EMDAGP01: ERR - All Exchange databases must be manually dismounted prior to attempting the restore (or select Dismount in restore GUI).

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

You need to tell us what exactly you are trying to do. 

Your post says the backup is failing but Activity Monitor shows failed restore attempt.

Please list all the steps you have taken up to the point where the job failed.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Sathisp83@yahoo.com's picture

Exchange restorations are getting failed with error 2810. i'm not trying to overwrite the existing db.

New Db has been created for the restoration.

This was 5 attempt, every time it returns and fails half the way. Totally data is in 4 tapes. all the 4 tapes are in library.

If you see the logs it shows status "24: socket write failed" after writing half of the data.
 

Sathisp83@yahoo.com's picture

Todays is the last day of for the data to be expire from Tape. Please advice how to extend the exp date, so that it should list in backup history in backup,archive  and restoration tab.

Marianne's picture

To extend expiration date, run this command against each of the tapes:

bpexpdate -backupid ASCORP-DAG-1_1378512889 -d <new-date>

<new-date> format: mm/dd/yyyy

To troubleshoot the restore failure, ensure ALL of the following log folders exist:

On master: bprd (NBU needs to be restarted to enable the log)

On media server: bpbrm and bptm

On Exchange server: bpcd and bpbkar

Is there a firewall anywhere in the picture (e.g.  between client and media server or between master and media server)?
If so, what is the timeout set on the firewall?

Please also check the Client Read Timeout setting on the media server - change it to large setting, e.g. 3600.
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Sathisp83@yahoo.com's picture

Checked on master, media and exchnage server, every thing is fine.

As you mentioned i have changed client read timeout to 3600(it was 300 before), and this time the restoration is sucessful. Thanks Marianne.