NVP-vProxy: VBA policy migration fails - Unable to load hypervisor inventory: Hypervisor resource not found

Summary: The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. When trying to migrate a policy from a VBA policy to vProxy, it fails with error message "Workflow failed: Unable to convert protection group: Unable to load hypervisor inventory: Hypervisor resource '' not found. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. When trying to migrate a policy from a VBA policy to vProxy, it fails with error message "Workflow failed: Unable to convert protection group: Unable to load hypervisor inventory: Hypervisor resource '<vCenter FQDN>' not found.
  
158738:nsrvbaupgrade: Starting VBA migrate utility...
157559:nsrvbaupgrade: Initialized job '128012'.
159206:nsrvbaupgrade: Run the pre-check command.
157560:nsrvbaupgrade: Processing policy 'Windows VMs 01'.
157561:nsrvbaupgrade: Processing policy 'Windows VMs 01' with VMware VBA action.
158731:nsrvbaupgrade: Processing workflow 'Windows VMs 01' with VMware VBA action.
159276:nsrvbaupgrade: Workflow 'Windows VMs 01' check failed while processing workflow components.
158746:nsrvbaupgrade: Policy 'Windows VMs 01' check status: Failed.
158898:nsrvbaupgrade: Pre-check failed:
159282:nsrvbaupgrade:    Policy 'Windows VMs 01' Failed.
159284:nsrvbaupgrade:       Workflow 'Windows VMs 01' Failed.
159289:nsrvbaupgrade:          Passed Storage node 'nsrserverhost': Storage node version 9.1.1.0 has passed the minimum version check (9.1.0.0).
159287:nsrvbaupgrade:          Passed Backup pool 'VMwareprod'.
159289:nsrvbaupgrade:             Passed DD 'emcdd2500.testlab.dellemc.com': DD version Data Domain OS 5.7.4.0-552828 has passed the minimum version check (5.6.0.0).
159289:nsrvbaupgrade:          Failed Protection group 'Windows VMs 01': Unable to query NSR hypervisor 'vcenter01.testlab.dellemc.com' for version.
159209:nsrvbaupgrade: Run the migration command.
159374:nsrvbaupgrade: Migrating policy 'Windows VMs 01': Pre-check failure is ignored by force flag.
159155:nsrvbaupgrade: Migrating policy 'Windows VMs 01' with VMware VBA action.
158349:nsrvbaupgrade: Migrating protection group 'Windows VMs 01'.
159167:nsrvbaupgrade: Unable to convert protection group 'Windows VMs 01': Unable to load hypervisor inventory: Hypervisor resource 'vcenter01.testlab.dellemc.com' not found.
.
159164:nsrvbaupgrade: Workflow 'Windows VMs 01' migration failed: Unable to convert protection group 'Windows VMs 01': Unable to load hypervisor inventory: Hypervisor resource 'vcenter01.testlab.dellemc.com' not found.
.
159156:nsrvbaupgrade: Policy 'Windows VMs 01' migrate status: Failed.
159205:nsrvbaupgrade: Migrate failed:
159282:nsrvbaupgrade:    Policy 'Windows VMs 01' Failed.
159285:nsrvbaupgrade:       Workflow 'Windows VMs 01' Failed: Unable to convert protection group 'Windows VMs 01': Unable to load hypervisor inventory: Hypervisor resource 'vcenter01.testlab.dellemc.com' not found.
.
158741:nsrvbaupgrade: VBA migrate utility completed with errors.

Cause

Reviewing the NSR Hypervisor resource via nsradmin reveals that the NSR Hypervisor was created with the vCenter short hostname. During migration, it is looking for NSR Hypervisor with the vCenter FQDN.
  
C:\Users\Administrator>nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show
nsradmin> print type: nsr hypervisor
                        type: NSR hypervisor;
                        name: vcenter01;
                     version: 6.0.0;
                     comment: ;
                     service: VMware VirtualCenter;
                    endpoint: "https://vcenter01/sdk";
                    username: administrator@vsphere.local;
                    password: *******;
                     command: nsrvim;
                       proxy: vcenter01.testlab.dellemc.com;

Resolution

Remove the short hostname NSR Hypervisor / vCenter entry from NMC VMware View and recreate it with the FQDN.

If you are unable to remove the NSR Hypervisor / vCenter entry from the NMC VMware View, see NetWorker: Removing vCenter entry from NMC VMware View/Removing NSR Hypervisor

Additional Information

To find more information about VBA to vProxy policy migration, search for any of the following sections in the NetWorker 9.1 VMware Integration Guide.
- Migrating policies from VMware Backup appliance to vProxy appliance
- Co-existence of the VMware Backup appliance and vProxy appliance
- Migration pre-requisites
- Policy migration to vProxy by using NMC
- Policy migration to vProxy by using the command line

NetWorker 9.1 VMware Integration Guide:
https://support.emc.com/docu81544_NetWorker_9.1_VMware_Integration_Guide.pdf?language=en_US
 

Affected Products

NetWorker

Products

NetWorker
Article Properties
Article Number: 000061929
Article Type: Solution
Last Modified: 28 Nov 2023
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.