VCSA VAMI based backup is failing when stats is not selected in configuration
search cancel

VCSA VAMI based backup is failing when stats is not selected in configuration

book

Article ID: 326439

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 6.0 VMware vCenter Server 7.0

Issue/Introduction

VAMI Backup fails without any specific error message in the GUI

You can see similar entries in /var/log/vmware/backup.log file -

YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] INFO: Successfully dump Postgres globals data. See complete log at /var/log/vmware/applmgmt/backup.log
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] INFO: Execute command: ['/opt/vmware/vpostgres/current/bin/pg_dumpall', '-U', 'postgres', '-p', '5432', '-s', '-c', '--if-exists']
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] ERROR: Password:
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] ERROR: pg_dump: [archiver (db)] connection to database "ssodb" failed:fe_sendauth: no password supplied
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] ERROR: pg_dumpall: pg_dump failed on database "ssodb", exiting
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] ERROR: Postgres schema data backup command "['/opt/vmware/vpostgres/current/bin/pg_dumpall', '-U', 'postgres', '-p', '5432', '-s', '-c', '--if-exists']" return non-zero exit status 1.
YYYY-MM-DDTHH:MM:SS [VCDBBackup:PID-8380] ERROR: Failed to backup VCDB.



Environment

VMware vCenter Server 6.x

VMware vCenter Server 7.x

 

Cause

The SSODB has been removed from version 5.5 onwards but as the upgrades happen from older vCenter versions, it can get carried along. This DB has been dropped in the later versions but can be carried along as an orphaned object. Dropping this manually will not cause any issues as this is not used anywhere.

Resolution

Note: Please take a snapshot of the VCSA VM before proceeding with below steps. If there are multiple vCenters in Enhanced Linked Mode, then power off all the VC nodes and take a offline snapshot.
 
  • SSH session(putty) to VCSA
  • Run the below command to drop that SSOSB from VCDB
           /opt/vmware/vpostgres/current/bin/psql -c 'DROP DATABASE ssodb;' -U postgres postgres
  • Run the Backup again.