12-05-2016 10:05 PM - last edited on 12-05-2016 11:13 PM by Marianne
*** Moved to new discussion from https://vox.veritas.com/t5/NetBackup/Instant-Recovery-quot-Failed-to-export-a-backup-image-on-the/m-... ***
Hello All,
I am also facing the same issue, I have tried with below command and is not helping me:
c:\Program Files\Veritas\NetBackup\bin>nbrestorevm -vmw -ir_activate -C labvmclient -vmproxy labrecoveryhost -disk_media_server labrecoveryhost -vmserver vcentervc0
1 -temp_location 10.1.1.11:/data/col1/ir-test
labvmclient - VM client
labrecoveryhost - Windows 2012 R2 media server as well as recovery host with NFS service configured.
Destination where backup has been taken is on Basic Disk - Data Domain.
-temp_location - this is temporary location where we are trying to mount the backup image.
ESX in this vcenter is enabled with VMKernel NIC for NFS.
Telnet ports between ESX and Recovery host/Media Server has been checked for 111 and 7934
Error Message:
12/06/2016 06:37:42 - Info bprd (pid=13138) Waiting for Instant Recovery job to end
12/06/2016 06:37:42 - Info bprd (pid=13138) Starting to export a backup image on the media server labrecoveryhost
12/06/2016 06:37:42 - Error bprd (pid=13138) Failed to export a backup image on the media server labrecoveryhost
socket open failed (21)
Please help with this issue and what logs can be checked at what server roles.
Does anybody has got the process flow for instant reocvery
Solved! Go to Solution.
12-07-2016 04:46 AM
See if these TNs help:
About configuring Services for Network File System (NFS) on Windows 2012 and Windows 2012 R2
http://www.veritas.com/docs/000112361
Enabling Services for Network File System (NFS) on a Windows 2012 or Windows 2012 R2 media server
http://www.veritas.com/docs/000112075
12-06-2016 12:10 AM - edited 12-06-2016 01:47 AM
Here's a plan how to test IR https://www.veritas.com/support/en_US/article.000075362 You can check whole procedure step by step to understand what exaclty doesn't work (I think in your case step 3 couldn't finish
)
12-06-2016 05:26 AM
Thankyou Mike for the wonderful diagnostic link. My issue is with portmapper, now can you/anybody here help me please with the resolution:
c:\Program Files\Veritas\NetBackup\bin>nbfsd -k -v 5 -p -j 24 -B labvmclient_14
80937695 -U IR_ESX -c labmediacumproxy -O x/labesx01_labmediacumproxy
cannot contact portmapper - exiting
c:\Program Files\Veritas\NetBackup\bin>
12-07-2016 03:06 AM
Tried with restarting NFS service as well, no luck:
net stop nfsclnt
net stop nfsrdr
net start nfsrdr
net start nfsclnt
12-07-2016 03:33 AM
Someone,
Please suggest how to fix this portmapper issue here on media server with Win 2012 R2.
12-07-2016 04:46 AM
See if these TNs help:
About configuring Services for Network File System (NFS) on Windows 2012 and Windows 2012 R2
http://www.veritas.com/docs/000112361
Enabling Services for Network File System (NFS) on a Windows 2012 or Windows 2012 R2 media server
http://www.veritas.com/docs/000112075
12-07-2016 05:37 AM
Thankyou very much Marianne for providing the NFS configuration.
Yes indeed it was helpful, I am testing it further now !!!
The mistake I made is, enabled the NFS client instead of NFS Server. Corrected by disabling the NFS client and installing NFS Server.
12-08-2016 01:10 AM
Step1 and Step2 successful
Step 3 : I am running this from Win 2012 R2 media server which is a proxy host as well.
c:\Program Files\Veritas\NetBackup\bin>nbfs.exe vmmount -cred 187E48B007F22DDF3F76802321D5C8C4492A52F5A9FBB4E0B420ADFE6EFFBA0A61D63EEDAB -server labmediacumproxy -port 7394 -vmserver labvcenter01 -esxhost labesx01 NBU_IR_labmediacumproxy _labesx01
EXIT_STATUS=11
The below output is from media server **bleep** proxy host, PID=3584 is for nbfsd
c:\Program Files\Veritas\NetBackup\bin>netstat -ano |findstr 7394
TCP 0.0.0.0:7394 0.0.0.0:0 LISTENING 3584
UDP 0.0.0.0:7394 *:* 3584
12-16-2016 01:26 AM
Hello All,
I am still testing, my vcenter has gone down so getting it fixed first but will keep everyone posted with updates.
05-08-2017 04:24 AM
Thankyou very much @Marianne
It was a great help and I could finish my configuration and testing.
01-09-2019 09:45 AM
I also had an instant recovery vm problem with error 5 (before 130). The solution was to add in the ESXi the media server entry in the host file and restart the nfsclient service in the master server and media server. now a restore does not last more than 1 minute