nbrestorevm -R

[cc1702004]

Hello,

We need to do a VM instance recovery test for a customer. May I know for the nbrestorevm -R (rename_file).

Can anyone please share with me how to use this (rename_file) ?

(1) What file extension should this file ended with ? Can it be a txt example, RenameConf.txt..or it should end with other extension ?

(2) Where should this file be placed ? Can I placed it on any location, example C:\temp, or it should be one of the Netbackup location, example, the Netbackup log directory ?

Can someone please be kind to share with me?

Thank you

[sdo]

Maybe this will help you:

How to manually test VMware Instant Recovery NFS connections between media server and ESX host

https://www.veritas.com/support/en_US/article.100038380

[cc1702004]

Hello SDO,

(1) Ok thanks for the clarification, I will try not to change any NFS settings..based on your feedback it is not required for VM instance recovery

(2) I will try to get the Vcenter and ESX hosts patch level from my colleague.

(3) I will read up on the logging.

[cc1702004]

Hello SDO,

I was reviewing the VM instance recovery job triggered by us (which resulted in failures) as compared to a job ran by current. I notice that for our failed job, the ESX IP address to recover the VM was logged but a job ran by the current vendor, all the devices, including the ESX hostname was logged. Do you have any idea why is this happening ? I am beginning to suspect some hostname resolution thingy. In our own company environment we used hosts file to resolve the hostname but in the customer environment, they use DNS to resolve hostname..n

Job failure triggered by Us
12/12/2019 18:28:43 - Info bprd (pid=10444) Waiting for Instant Recovery job to end
12/12/2019 18:28:43 - Info bprd (pid=10444) Starting to export a backup image on the media server svr03msbackup
12/12/2019 18:28:45 - Info bprd (pid=10444) Backup image has been successfully exported on the media server svr03msbackup
12/12/2019 18:28:50 - Info bprd (pid=10444) Backup image has been successfully mounted on the server 10.168.128.57
12/12/2019 18:28:50 - Info bprd (pid=10444) Starting to activate a virtual machine on the server 10.168.128.57
12/12/2019 18:28:56 - Error bprd (pid=10444) Failed to activate a virtual machine on the server 10.168.128.57
12/12/2019 18:28:56 - Info bprd (pid=10444) Starting to unmount a backup image on the server 10.168.128.57
12/12/2019 18:28:56 - Info bpVMutil (pid=45495) INF - vmwareLogger: CreateVirtualMachineExAPI: SYM_VMC_ERROR: FAILED_TO_GET_DS_MOR
the restore failed to recover the requested files (5)

Job success triggered by current vendor :
=================================================

12/04/2019 18:27:26 - Info bprd (pid=18148) Waiting for Instant Recovery job to end
12/04/2019 18:27:26 - Info bprd (pid=18148) Starting to export a backup image on the media server svr03msbackup
12/04/2019 18:27:26 - Info bprd (pid=18148) Backup image has been successfully exported on the media server svr03msbackup
12/04/2019 18:27:31 - Info bprd (pid=18148) Backup image has been successfully mounted on the server esx07.adr.abc.com
12/04/2019 18:27:31 - Info bprd (pid=18148) Starting to activate a virtual machine on the server esx07.adf.abc.com
12/04/2019 18:27:57 - Info bprd (pid=18148) Virtual machine has been successfully activated on the server esx07.adf.abc.com and the Instant Recovery identifier is 3
12/04/2019 18:27:57 - Info bprd (pid=18148) Job completed successfully
the requested operation was successfully completed (0)

vendor.

[cc1702004]

I am suspecting this issue might be due to some hostname resolution issue.

Example 

Could be that the ESX server has no name resolution for the media server or vice versa so it cannot mount the nfs image.

I recalled when my colleague showed me in the Vsphere client, the ESX hosts are displayed as IP address..

[cc1702004]

Hello,

We did attempt to run the VM instance recovery on a VM from the other ESX host cluster, with all the ESX hosts having a hostname and we managed to perform that on the same ESX host in that cluster.

So I was wondering does this have to do with the ESX hostname issue where we failed to perform VM instance recovery on the ESX host with just IP address.

[sdo]

It has to be worth configuring similar naming constructs for the host with no naming.

[fmatzinger1]

Please find below an example of a rename file.

The VM cltocpw01 has been backed up and is still running.

To avoid to erase the running VM, I've instantly restored a new cltocpw01.vmtempo VM.

# nbrestorevm -vmw -ir_activate -C cltocpw01 -temp_location "datastore_local" -R /tmp/rename_vm_cltocpw01

# cat /tmp/rename_vm_cltocpw01

change vmname to cltocpw01.vmtempo