Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SQL DB Restoration to alternate server fails

Created: 06 Sep 2010 | 2 comments
Deepak G's picture
0 0 Votes
Login to vote

I am trying to restore SQL DB from one prodn. server to a development server. I am able to browse the images of the backup of the source server from the destination server.
But when i initiate the backup it is failing with Err # 5.

LOG :

Error bpbrm (pid=13639) socket read failed: errno = 131 - Connection reset by peer

Can anybody help with this.

discussion Filed Under:

Comments

RahulG's picture
06
Sep
2010
0 Votes 0
Login to vote

refer the following document

refer the following document http://support.veritas.com/docs/287791
Check if the Sql version is the same on both the server
eq you might be restoring to different SQL host/instance (SQL 2000), not the same as original SQL client (SQL 2005).

If this response answers your concern, please mark it as a "solution"

Marianne van den Berg's picture
06
Sep
2010
0 Votes 0
Login to vote

Alternate Client Restore is

Alternate Client Restore is described in NBU for SQL guide, p.99.

Please verify requirements and steps in the manual carefully.

Ensure you have bprd log on master as well as dbclient log on destination client.

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