Forum Discussion

dicky_23's avatar
dicky_23
Level 3
7 years ago

NBU VM Alternate Restore Error 2820

Hi All,

Need guide for below error. i am running restore of VM vmware to alternate host of esxi. and get below error :

May 11, 2018 4:04:33 PM - begin Restore
May 11, 2018 4:04:42 PM - Info bprd (pid=10924) Found (135,657) files in (1) images for Restore Job ID 70.xxx
May 11, 2018 4:04:42 PM - restoring from image 35.200.168.192.in-addr.arpa_1525939990
May 11, 2018 4:04:43 PM - requesting resource  @aaaab
May 11, 2018 4:04:43 PM - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=DPOO-POOL;Path=PureDiskVolume;StorageServer=nbu;MediaServer=nbu
May 11, 2018 4:04:44 PM - Info bprd (pid=10924) Searched (      2) files of (135,657) files for Restore Job ID 70.xxx
May 11, 2018 4:04:44 PM - Info bprd (pid=10924) Restoring from copy 1 of image created 05/10/18 15:13:10 from policy Vm-Backup
May 11, 2018 4:04:45 PM - Info bprd.sfr (pid=10924) Restoring to vCenter server esxnbu.xxxx.xxxx, ESX host esxnbu.xxxx.xxxx, Datacenter None, Folder None, Display Name TV REMOTE1, Resource Pool/vApp /ha-datacenter/host/esxnbu.xxxx.xxxx/Resources, Datastore/Datastore Cluster NetappDS01
May 11, 2018 4:04:46 PM - Info bpdm (pid=7612) started
May 11, 2018 4:04:46 PM - started process bpdm (pid=7612)
May 11, 2018 4:04:46 PM - Info bpdm (pid=7612) reading backup image
May 11, 2018 4:04:47 PM - Info bpdm (pid=7612) requesting nbjm for media
May 11, 2018 4:04:48 PM - Info bpdm (pid=7612) using 30 data buffers
May 11, 2018 4:04:48 PM - Info bpdm (pid=7612) spawning a child process
May 11, 2018 4:04:48 PM - Info bpbrm (pid=7612) child pid: 11172
May 11, 2018 4:04:48 PM - Info bpdm (pid=11172) started
May 11, 2018 4:04:48 PM - started process bpdm (pid=11172)
May 11, 2018 4:04:51 PM - begin reading
May 11, 2018 4:04:52 PM - end reading; read time: 0:00:01
May 11, 2018 4:04:53 PM - Info bpdm (pid=7612) completed reading backup image
May 11, 2018 4:04:53 PM - Info bpdm (pid=7612) EXITING with status 0
May 11, 2018 4:04:53 PM - Info nbu (pid=7612) StorageServer=PureDisk:nbu; Report=PDDO Stats for (nbu): read: 12563 KB, CR received: 47186 KB, CR received over FC: 0 KB, dedup: 0.0%
May 11, 2018 4:04:54 PM - end Restore; elapsed time 0:00:21
May 11, 2018 4:04:54 PM - Info bpVMutil (pid=9396) Unable to determine if the VM already exists under Folder , Resource Pool /ha-datacenter/host/esxnbu.veritas.local/Resources.
NetBackup VMware policy restore error  (2820)

Please need advice . thanks in advance

8
Windows Server 2016
  • Marianne's avatar
    Marianne
    7 years ago

    dicky_23

    Did you click on 'Run Pre-Recovery Check' before starting the restore? 

    Extract from the manual:

    Verifies the credentials and appropriate paths and connectivity, determines whether the datastore or datastore cluster has available space, and reviews other requirements.
    You must run this check at least once.

    It appears that you have specified the vCenter and ESX servers as: esxnbu.xxxx.xxxx
    Is this correct?

    May 11, 2018 4:04:45 PM - Info bprd.sfr (pid=10924) Restoring to vCenter server esxnbu.xxxx.xxxx, ESX host esxnbu.xxxx.xxxx, Datacenter None, Folder None, Display Name TV REMOTE1, Resource Pool/vApp /ha-datacenter/host/esxnbu.xxxx.xxxx/Resources, Datastore/Datastore Cluster NetappDS01

    Error:

    May 11, 2018 4:04:54 PM - Info bpVMutil (pid=9396) Unable to determine if the VM already exists under Folder , Resource Pool /ha-datacenter/host/esxnbu.veritas.local/Resources.

    Doing the 'Pre-Recovery Check' may help you to pinpoint the problem.

4 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    7 years ago

    dicky_23

    Did you click on 'Run Pre-Recovery Check' before starting the restore? 

    Extract from the manual:

    Verifies the credentials and appropriate paths and connectivity, determines whether the datastore or datastore cluster has available space, and reviews other requirements.
    You must run this check at least once.

    It appears that you have specified the vCenter and ESX servers as: esxnbu.xxxx.xxxx
    Is this correct?

    May 11, 2018 4:04:45 PM - Info bprd.sfr (pid=10924) Restoring to vCenter server esxnbu.xxxx.xxxx, ESX host esxnbu.xxxx.xxxx, Datacenter None, Folder None, Display Name TV REMOTE1, Resource Pool/vApp /ha-datacenter/host/esxnbu.xxxx.xxxx/Resources, Datastore/Datastore Cluster NetappDS01

    Error:

    May 11, 2018 4:04:54 PM - Info bpVMutil (pid=9396) Unable to determine if the VM already exists under Folder , Resource Pool /ha-datacenter/host/esxnbu.veritas.local/Resources.

    Doing the 'Pre-Recovery Check' may help you to pinpoint the problem.

    • dicky_23's avatar
      dicky_23
      Level 3
      7 years ago

      HI Marianne , thanks for your reply,

      below was the info from prereq recovery

      Verify vSphere server credential - Passed.
      Unsupported non-ASCII characters - Passed.
      VM exists overwrite - Error.
      Datastore path validation failed
      Adequate space on datastore/datastore cluster for configuration file - Passed.
      VMware connectivity test - Passed.
      Server Name esxnbu.veritas.local.
      Datastore/Datastore Cluster space available - Passed.
      339968 megabytes requested on datastore/datastore cluster NetappDS01, 10738037 available
      Validation tests completed.

      I see error

      VM exists overwrite - Error.

      Datastore path validation failed

      Does it because i add the host of esxi using https://www.veritas.com/support/en_US/article.100020483 Need your advise. Thanks

      • Marianne's avatar
        Marianne
        Level 6
        7 years ago

        Hi dicky_23

        Apologies for the late reply - I had to find some spare time to look at the TN you are referring to. 

        I need to point out here that I am not an expert with virtual backups and restores - I have only been able to assist with test restores by following steps in the manual.

        You can check this TN to know if the user that you have added have sufficient previleges:

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

        So, one of the requirements is that the user must have these permission on the Datastore:

         Datastore         
            Allocate space     
            Browse datastore     
            Configure datastore     
            Low level file operations     
            Update virtual machine files     
            Update virtual machine metadata     

        Validate above permissions. It may be causing the issue with failed 'Datastore path validation'.