vStorage "Pre-Recovery Check" when performing restore to the original location will fail if the ESX or Virtual Center credential name was changed after the backup

Problem

When performing a restore to original location, the "Run Pre-Recovery Check" fails if the ESX server or Virtual Center server name that was configured in the NetBackup credentials was changed after the backup.  For example, if the Virtual Center server at backup time was VIRTUALCENTER, and then the credential was deleted from NetBackup and re-added as VIRTUALCENTER.hro.spt.Veritas.com.  Then the "Run Pre-Recovery Check" will fail when restoring back to the original location.

Error Message

bpvmutil:

13:13:30.554 [1896.2436] format_virtualserver_cred: read 1 VIRTUALCENTER01.symantec.com backup bb0223f21af0533cc6511d841f2f2450d9de3e26f0b71bff5b237234fc8bd4ad31a5844832e778234bb41b890e517976d5abdc80e02d280abf84dea97e391d7c 20400 0
13:13:30.554 [1896.2436] dovSphereDisconnect: disconnect for VIRTUALCENTER01.symantec.com completed with flags 0 and status 0
13:13:30.554 [1896.2436] find_virtual_server_cred: Couldn't find VIRTUALCENTER01

13:13:30.804 [1896.2436] format_virtualserver_cred: read 1 VIRTUALCENTER01.symantec.com backup bb0223f21af0533cc6511d841f2f2450d9de3e26f0b71bff5b237234fc8bd4ad31a5844832e778234bb41b890e517976d5abdc80e02d280abf84dea97e391d7c 20400 0
13:13:30.804 [1896.2436] validateProxyCredentials: find credential failed for ESX Server VIRTUALCENTER01 with 0.
13:13:30.804 [1896.2436] dovSphereDisconnect: disconnect for VIRTUALCENTER01.symantec.com completed with flags 0 and status 0
 

Cause

The issue occurs because the backup stored the Virtual Center or ESX  server name, so at restore time.  If that credential does not exist, credentail validation will fail during the "Run Pre-recovery Check".

Solution

Solution #1:

Use the "Alternate Location" to restore the Virtual Machine.

Solution #2:

Delete and re-add the credential using the Virtual Center or ESX  server name as configured at backup time.