cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup NDMP Restore Error

Seonix
Level 3

Hi,

I'm attemping to complete an NDMP restore but am receiving the following error in the job log (I've had to sanitise for security reasons):

24/09/2014 9:54:52 AM - begin Restore
24/09/2014 9:54:53 AM - 1 images required
24/09/2014 9:54:53 AM - media DY0003 required
24/09/2014 9:54:53 AM - restoring image 10.11.2.51_1411374688
24/09/2014 9:54:53 AM - Info bpbrm(pid=5796) <media server> is the host to restore to      
24/09/2014 9:54:53 AM - Info bpbrm(pid=5796) telling media manager to start restore on client     
24/09/2014 9:54:54 AM - Info bpbrm(pid=568) <media server> is the host to restore to      
24/09/2014 9:54:55 AM - Info bpbrm(pid=568) start tar32 on client         
24/09/2014 9:54:55 AM - Info tar32(pid=2192) Restore started.           
24/09/2014 9:54:55 AM - connected
24/09/2014 9:54:55 AM - Info bptm(pid=5284) Waiting for mount of media id DY0003 (copy 1) on server <media server>.
24/09/2014 9:54:55 AM - started process bptm (5284)
24/09/2014 9:54:55 AM - mounting DY0003
24/09/2014 9:54:55 AM - Info bptm(pid=5284) INF - Waiting for mount of media id DY0003 on server <media server> for reading.
24/09/2014 9:54:55 AM - requesting resource DY0003
24/09/2014 9:54:55 AM - granted resource DY0003
24/09/2014 9:54:55 AM - granted resource IBM.ULT3580-HH5.000
24/09/2014 9:55:38 AM - mounted; mount time: 00:00:43
24/09/2014 9:55:38 AM - Info bptm(pid=5284) DY0003            
24/09/2014 9:55:38 AM - Info bptm(pid=5284) INF - Waiting for positioning of media id DY0003 on server <media server> for reading.
24/09/2014 9:55:38 AM - positioning DY0003 to file 36
24/09/2014 9:57:55 AM - positioned DY0003; position time: 00:02:17
24/09/2014 9:57:55 AM - begin reading
24/09/2014 9:57:57 AM - Info ndmpagent(pid=2192) INF - Restoring NDMP files from /vol/source/.../4.01.04/ to [See line below]  
24/09/2014 9:57:57 AM - Info ndmpagent(pid=2192) INF - Restoring NDMP files from [See line above] to /E/Restore  
24/09/2014 9:58:19 AM - Error ndmpagent(pid=2192) failed to connect to NDMP server <media server>, connect error = -1003 (Unable to connect to NDMP server)
24/09/2014 9:58:19 AM - Error ndmpagent(pid=2192) NDMP restore failed from path /vol/source       
24/09/2014 9:58:19 AM - Info ndmpagent(pid=2192) done. status: 25: cannot connect on socket      
24/09/2014 9:58:19 AM - restored image 10.11.2.51_1411374688 - (the restore failed to recover the requested files(5)); restore time 00:03:26
24/09/2014 9:58:19 AM - Info bpbrm(pid=5796) got ERROR 5 from media manager       
24/09/2014 9:58:19 AM - Info bpbrm(pid=5796) terminating bpbrm child 568 jobid=6357        
24/09/2014 9:58:19 AM - end Restore; elapsed time: 00:03:27
Restore error(2850)

From the media/master server:

- tpautoconf -verify media_server completes successfully.

- I can telnet to the netapp filer on port 10000 successfully.

There is no record on the netapp filer of an NDMP session attempting to start so I'm presuming the issue is with the netbackup server.

Any ideas?

1 ACCEPTED SOLUTION

Accepted Solutions

Amol_Nair
Level 6
Employee
You are seeing this error because you are trying to restore NDMP data to a non NDMP machine in your case the Windows media server... NDMP data cannot be restored to non-NDMP machines. It is even vendor specific. This means data backed up from a NetApp filer can only be restored back to a NetApp filer, EMC data can be restored only to EMC filer. This is how NDMP works and is not a limitation from NetBackup side but from NDMP Itself..

View solution in original post

3 REPLIES 3

Amol_Nair
Level 6
Employee
You are seeing this error because you are trying to restore NDMP data to a non NDMP machine in your case the Windows media server... NDMP data cannot be restored to non-NDMP machines. It is even vendor specific. This means data backed up from a NetApp filer can only be restored back to a NetApp filer, EMC data can be restored only to EMC filer. This is how NDMP works and is not a limitation from NetBackup side but from NDMP Itself..

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Lets check the logs

 

Windows platform: <install path>\Veritas\NetBackup\bin\vxlogview -p 51216 -o 134 > C:\temp\ndmpagent.log

UNIX/Linux platfrom: /usr/openv/netbackup/bin/vxlogview -p 51216 -o 134 > /tmp/ndmpagent.log

Seonix
Level 3

Thanks Amol,

Thought this might be the case (or something similar) after checking the Netbackup NDMP logs and saw it trying to connect to the master server on port 10000.

Successfully completed a restore back to the filer.