vCenter VAMI Redirects to /configurev2 Following Restore Failure at 97%

Products

• VMware vCenter Server

Issue/Introduction

 

• After restoring a vCenter Server Appliance from backup, navigating to the VAMI (https://<FQDN>:5480) redirects automatically to https://<FQDN>:5480/configurev2.

• The restore process reached approximately 97% before reporting a failure or timeout.

• The vSphere Client (https://<FQDN>/ui) is accessible and vCenter services appear functional.

• In /var/log/vmware/applmgmt/applmgmt.log, the following error is observed: twisted.python.failure.Failure vmware.vherd.base.pint.Error: pint.Error('com.vmware.applmgmt.err_status_does_not_exist')

 

Environment

VMware vCenter Server Appliance (VCSA) 7.x, 8.x

Cause

The restore process failed during the Stage 2 Reconciliation phase (typically at 97%). This phase is responsible for signaling the applmgmt service that the restore is complete. When this signal is missed, the Management Gateway defaults to the deployment wizard. Even if the manual fbInstall.json success flag is set, stale reconciliation history and backup markers in the file system can override the appliance state, forcing the redirect.

Resolution

To resolve this issue and restore VAMI functionality, the stale restore markers and reconciliation history must be cleared manually.

1. Open an SSH session to the vCenter Server Appliance and log in as root.

2. Stop the Management Service:

   service-control --stop applmgmt
   

3. Clear the Reconciliation and Backup History: Execute the following commands to remove the files preventing the VAMI from loading the dashboard:

   rm /storage/applmgmt/backup_restore/restoreReconciliation-history.json
   rm /storage/applmgmt/backup_restore/backup-history.json
   rm /var/vmware/applmgmt/backupRestore-history.json
   rm /etc/vmware/backupMarker.txt
   

4. Force the Success State: Ensure the firstboot installation status is set to success:

   echo '{ "progress" : 100, "status" : "success" }' > /var/log/firstboot/fbInstall.json
   chmod 644 /var/log/firstboot/fbInstall.json
   

5. Remove the Restore Pending Marker:

   rm /etc/vmware/restore_pending
   

   (Note: If the file does not exist, proceed to the next step.)

6. Restart Services:

   service-control --start applmgmt
   # For vCenter 7.x/8.0 pre-U3:
   service vami-lighttp restart
   # For vCenter 8.0 U3+:
   systemctl restart cap-lighttpd.service
   

7. Verification: Clear your browser cache or open an Incognito window and navigate to https://<vCenter_FQDN>:5480. The standard login page should now appear.