MS SQL failed to restore backup with Status Code 5

Posted on July 14, 2011

0


PROBLEM

I took the backup of MS SQL Server via Netbackup 6.5 successfully but when I tried to restore it on a alternate PC, I got the below error. I also made a folder altname with a empty .txt file name norestriction. i also did all initial checks as much as possible as i could do but remain got the same error

Note:

The Status Code 5 is a gernel error. There may be so many other reasons of Status Code 5

ERROR
Restore failed
6/8/2009 5:29:28 PM – begin Restore
6/8/2009 5:29:34 PM – restoring image dbcluster_1244419813
6/8/2009 5:29:35 PM – requesting resource Fibre Transport
6/8/2009 5:29:35 PM – Warning nbjm(pid=2524) NBU status: 800, EMM status: Fibre Transport resources are not available
6/8/2009 5:29:35 PM – Warning nbjm(pid=2524) NBU status: 800, EMM status: Fibre Transport resources are not available
6/8/2009 5:35:39 PM – Error bpbrm(pid=4916) listen for client protocol error – couldn’t accept from data socket, The operation completed successfully. (0)
6/8/2009 5:35:44 PM – Error bpbrm(pid=4916) client restore EXIT STATUS 25: cannot connect on socket
6/8/2009 5:37:38 PM – restored image clusterSrv_1244419813 – (cannot connect on socket(25)); restore time 00:08:04
6/8/2009 5:37:43 PM – end Restore; elapsed time: 00:08:15
the restore failed to recover the requested files(5)

MY Environment
Operating System win2003 Server 32bit with service pack2, Netbackup Server6.5

Problem Resolution
Check the Name Resolution
On the Master Server:
• …Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -hn Client name

On the client:
• ….Program Files\Veritas\NetBackup\bin>bpclntcmd.exe –pn

• ….Program Files\Veritas\NetBackup\bin>bpclntcmd -ip <clients ip address>

Error Found
when i ran the below command at the Master Server i found suspecious
• …Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -hn Client name

i also like to show the figure:

imagebrowser image

Conclusion
Basically when i was doing redirected restore the PC  has a IP 10.10.2.58 but the DNS server has a bad record against the PC(IP 10.10.2.245) thats why the restoring failed because the restore process was trying to restore on 10.10.2.245 and the .245 does nt exist 🙂


SomeThing More

i did the above as per the below link in the step 4 of  How can we do Basic Netbackup TroubleShooting for Windows in any aspect
https://www-secure.symantec.com/connect/forums/how…

Advertisements