19. Restore the vCenter Server vPostgres database from the backup using the command
PGPASSWORD=<EMB_DB_PASSWORD> ./psql -d <EMB_DB_INSTANCE> -Upostgres
-f VCDBBackupFile
where
<EMB_DB_PASSWORD>
and
<EMB_DB_USER>
are the values
noted in the previous step.
20. Restart the vCenter Server using the command
service vmware-vpxd start
.
Related links
Troubleshooting software issues
on page 34
Recovering from a failed VCSA 5.5 upgrade
About this task
The following procedure provides steps for recovering from a failed upgrade to vCenter Server
Appliance (VCSA) Release 5.1 to 5.5. This procedure presents a high level overview of the process.
Refer to the appropriate documentation for procedures such as:
• Upgrading VCSA deployments.
• vPostgres database file backup and restoration.
• VCSA deployment.
• Host connection.
• Reverting to VCSA snapshots.
Procedure
1. Backup and restore the failed upgrade to a new 5.5 instance.
a. Backup the vPostgres database from the failed 5.5 upgrade.
b. Note the IP address, DNS settings, and Hostname of the failed upgrade.
c. Shutdown the failed 5.5 upgrade.
d. Deploy a new 5.5 instance with the same IP address, DNS settings, and Hostname as
the failed upgrade.
e. Restore the vPostgres database backup file to the new 5.5 instance.
f. Log in to the new vCenter instance.
g. Connect any hosts that display as disconnected using
root
credentials.
h. Proceed to the next step if the 5.5 upgrade does not complete successfully.
2. Perform a fresh upgrade from 5.1 to 5.5.
a. Revert back to the 5.1 snapshot.
b. Perform a fresh upgrade from 5.1 to 5.5.
c. Proceed to the next step if the 5.5 upgrade does not complete successfully.
Troubleshooting software issues
October 2017
Troubleshooting the Avaya Pod Fx
™
42