A system administrator backs up the full vRealize Automation installation on a regular basis.

Users 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. 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:

  • IaaS MS SQL database.

  • PostgreSQL database. (Applicable only for legacy installations that do not use an Appliance Database.)

  • Identity Appliance or other SSO appliance.

  • vRealize Appliance.

  • IaaS components.

  • Application Services 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 the Identity Appliance, all instances of the vRealize Appliance, and databases at the same time.

  • Minimize the number of active transactions before you begin a backup.

  • Back up all databases at the same time.

  • Back up the virtual appliance load balancer at the same time you back up the Identity Appliance.

  • Create a backup of instances of the vRealize Appliance when you update certificates.

  • Create a backup of IaaS components when you update certificates.

In addition, back up the Identity Appliance in the following cases:

  • You change the configuration.

  • You add or delete a tenant.

  • You create, delete, or modify an identity store.