The database administrator backs up the Infrastructure MSSQL Server and vRealize Automation appliance database.
As a best practice, back up the Infrastructure MSSQL and vRealize Automation appliance database or legacy PostgreSQL databases as nearly simultaneously as possible to prevent or minimize data loss. Also, when applicable, back up databases with Point-in-Time enabled. By using Point-in-Time recovery, you ensure that the two databases are consistent with each other. If only one database fails, you must restore the running database to the most recent backup so that the databases are consistent.
Infrastructure MSSQL Database
Follow your in-house procedures to back up the Infrastructure MSSQL database outside of the vRealize Automation framework.
Use the following guidelines when creating a backup:
If possible, check that all IaaS workflows are complete and that all IaaS services are stopped or that activity is minimized.
Back up with Point-in-Time enabled.
Back up the MSSQL database at the same time that you back up the other components.
Back up the passphrase for your database.
Your database is protected by a passphrase. Have the passphrase available when you restore the database. Typically, you record the passphrase in a safe and accessible location at install time.
Appliance Database or Legacy PostgreSQL Database
If you are using an Appliance Database or a legacy PostgreSQL database embedded in a vRealize Automation appliance, you can back up the database by backing up the entire appliance with one of the methods described in vRealize Automation appliance. If you are using a legacy PostgreSQL database, you can also backup the database separately. See the VMware Knowledge Base article Migrating from external vPostgres appliance to vPostgres instance located in the vCAC appliance (2083562) at http://kb.vmware.com/kb/2083562 for more information.
A standalone legacy PostgreSQL appliance must be backed up separately. See the VMware Knowledge Base article Migrating from external vPostgres appliance to vPostgres instance located in the vCAC appliance (2083562) at http://kb.vmware.com/kb/2083562 for more information.