A system administrator backs up the full vRealize Automation installation on a regular basis.
You can employ several strategies, singly or in combination, to back up vRealize Automation system components. For virtual machines, you can use the Snapshot function to create snapshot images of critical components. If a system failure occurs, you can use these images to restore components to their state when the images were created. You can perform full, differential, and incremental backups and restores of virtual machines. Alternatively, and for non-virtual machine components, you can create copies of critical configuration files for system components, which can be used to restore these components to a customer configured state following reinstallation.
A complete backup includes the following components:
Infrastructure MS SQL database.
PostgreSQL database. (Applicable only for legacy installations that do not use an appliance database.)
Identity management components as applicable.
vRealize Automation appliance.
Software load balancers.
Load balancers that support your distributed deployment. Consult the vendor documentation for your load balancer for information about backup considerations.
Guidelines for Planning Backups
Use these guidelines to plan backups:
When you back up a complete system, back up all instances of the vRealize Automation appliance, and databases as near simultaneously as possible, preferably within seconds.
Minimize the number of active transactions before you begin a backup. Schedule your regular backup to when your system is least active.
Back up all databases at the same time.
Back up the virtual appliance load balancer at the same time you back up the vRealize Automation appliance.
When you back up the vRealize Automation appliance and the IaaS components using snapshots, disable in-memory snapshots and quiesced snapshots.
Create a backup of instances of the vRealize Automation appliance when you update certificates.
Create a backup of IaaS components when you update certificates.