Forum Discussion

____111's avatar
____111
Level 3
12 years ago
Solved

ndmp restore error

Hi all 

There is a failure when i restore vol by ndmp (netapp ontap 3050),the error messages below.

11/25/2013 9:52:56 PM - begin Restore
11/25/2013 9:52:57 PM - 1 images required
11/25/2013 9:52:57 PM - media 6F0000 required
11/25/2013 9:53:01 PM - restoring image fas3050_1385387430
11/25/2013 9:58:13 PM - Error bpbrm(pid=4936) Cannot connect to fas3050         
11/25/2013 9:58:13 PM - Info bpbrm(pid=4936) telling media manager to start restore on client     
11/25/2013 10:03:13 PM - Error bptm(pid=5732) ndmp_open_and_auth() failed, return code 104        
11/25/2013 10:03:14 PM - Error bpbrm(pid=6608) Cannot connect to fas3050         
11/25/2013 10:03:14 PM - Info bpbrm(pid=4936) got ERROR 0 from media manager       
11/25/2013 10:03:14 PM - Info bpbrm(pid=4936) killing bpbrm child 6608.         
11/25/2013 10:03:14 PM - Error bptm(pid=5732) abnormal exit, but EXIT_Status == 0       
11/25/2013 10:03:14 PM - Info bptm(pid=5732) EXITING with status 174 <----------        
11/25/2013 10:03:15 PM - Info bpbrm(pid=6608) start tar32 on client         
11/25/2013 10:03:35 PM - Error ndmpagent(pid=5204) connection socket is invalid         
11/25/2013 10:09:01 PM - end Restore; elapsed time: 00:16:05
cannot connect on socket(25)
 
 
But ndmp backup is success.
 
 
The bptm logfile below:
19:36:52.489 [1864.2960] <2> vnet_connect_to_bpcd: ../../libvlibs/vnet_connect.c.237: 0: connect_to_service() failed: 18 0x00000012
19:36:52.489 [1864.2960] <2> local_bpcr_connect: Can't connect to client fas3050
19:36:52.489 [1864.2960] <2> ConnectToBPCD: bpcd_connect_and_verify(fas3050, fas3050) failed: 25
19:36:52.520 [1864.2960] <16> bpbrm start_bpcd_stat: Cannot connect to fas3050
 
bpclntcmd rely
C:\Users\Administrator>bpclntcmd -hn fas3050
host fas3050: fas3050 at 172.17.5.5
aliases:     fas3050     172.17.5.5
 
 
tpautoconf rely
C:\Users\Administrator>tpautoconf -verify fas3050
Connecting to host "fas3050" as user "root"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
  host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
  host name "fas3050"
  os type "NetApp"
  os version "NetApp Release 7.3.7"
  host id "0101187815"
Login was successful
Host supports LOCAL backup/restore
Host supports 3-way backup/restore
Host has SnapVault Secondary license installed
 
additional infoļ¼šthe ndmp is remote mode
 
 
plz help me to solve the problem.thankU
 
version 7.1 OS windows 2008r2  NetApp Release 7.3.7 
 
  • Hi Marianne,

    I found out the reason.The entry of client name = fas3050 is wrong in the bp.conf(in windows is regedit of symantec) .If i change it to airs(the hostname of master), then restore is success.

    But i have some question about it.

    First,i know it mode is remote,so the client is ndmpagent one.but why the option of backup is success before?

     

    Last,i don't change the regedit before,the installation is default and success.why it will change to the hostname of filer?

     

    laugh

  • Hi Marianne,

    The attachment is the word(microsoft office word 2007) about steps of my restore ndmp.

    plz check it and tell me anything options is incorrect?

    Thank U Marianne.

  • I don't see anything wrong with your steps...

    Hopefully someone else with more NDMP experience will see this post and be able to give better advice...

    All I can suggest at this point in time is to log a support call with Symantec.

  • Hi Marianne,

    I found out the reason.The entry of client name = fas3050 is wrong in the bp.conf(in windows is regedit of symantec) .If i change it to airs(the hostname of master), then restore is success.

    But i have some question about it.

    First,i know it mode is remote,so the client is ndmpagent one.but why the option of backup is success before?

     

    Last,i don't change the regedit before,the installation is default and success.why it will change to the hostname of filer?

     

    laugh

  • Someone must've done it. Registry entry will always match server hostname. The configured client name in registry/host properties is only used at restore time. When this name is not the same as local hostname, it tells NBU that you want to do a redirected restore. So, in your case, it tried to restore the data to the master server.