Forum Discussion

Vino_J's avatar
Vino_J
Level 4
14 years ago
Solved

SQL db restore issue

Hi All,

  Recieving errors while restoring a SQL db .Please find the details as follows:

Master/Media Server :

OS: Windows 2003 x64 Enterprise Edition SP2.

NBU: 6.5.6

Destination client: Windows 2008 x64 Enterprise Edition R2

NBU client: 6.5.6

The db was initially backedup on a Server running SQL 2005 server and we are trying to restore on a Target running SQL 2008 R2. We are able to restore all dbs except for one for which we are getting the following error:

Logs:

"8/11/2011 7:58:14 PM - Error bpbrm(pid=5016) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
8/11/2011 7:58:19 PM - restored image CTSINTBMCMUDB3_1312667425 - (file read failed(13)); restore time 04:49:36
8/11/2011 7:58:26 PM - end Restore; elapsed time: 04:51:21
the restore failed to recover the requested files(5)"

If any one had come across such issue, please let us know how it was resolved.

  • Hi All,

     The issue was resolved by making few changes in the Restore Script. Call was raised with Symantec as it was critical and the following were the two changes made.

    The value of MAXTRANSFERSIZE was set to 0 from 6 and NUMBUFS to 1 from 2.

    Reference:

    NetBackup for Microsft SQL Server restore failed with SQL Server error "SQL Server cannot process this media family" when restoring to SQL Server 2008

    http://www.symantec.com/docs/TECH74481                       

     

    DOCUMENTATION: Performance tuning for NetBackup for Microsoft SQL Server backups

    http://www.symantec.com/docs/TECH33423

                     

    Thanks to all for your time!!!!

9 Replies

  • The client read out time has been set to : 32000 secs. The total size of the db is close to 128 GB. the timeout settings were actually changed before we ran the restores. Still no go.

  • Please post the following logs as attachments:

    On media server: bptm and bpbrm

    On client: dbclient

    The job fails in less than 5 hours, indicating that it is not a NetBackup timeout that kicked in (32000 se = 8.89 hrs) : " end Restore; elapsed time: 04:51:21"
     

  • Hi All,

     The issue was resolved by making few changes in the Restore Script. Call was raised with Symantec as it was critical and the following were the two changes made.

    The value of MAXTRANSFERSIZE was set to 0 from 6 and NUMBUFS to 1 from 2.

    Reference:

    NetBackup for Microsft SQL Server restore failed with SQL Server error "SQL Server cannot process this media family" when restoring to SQL Server 2008

    http://www.symantec.com/docs/TECH74481                       

     

    DOCUMENTATION: Performance tuning for NetBackup for Microsoft SQL Server backups

    http://www.symantec.com/docs/TECH33423

                     

    Thanks to all for your time!!!!

  • Thankx for this information as i am not much good in SQL but hopefully above info will help me to next SQL troubleshoot.