The system administrator backs up the vRealize Automation appliance by exporting or cloning the appliance. You can also copy configuration files to use to recreate the configuration that was in place at the time of the backup.

Back up appliances by exporting or cloning them.

As a best practice, back up your vRealize Automation appliance and databases on the same schedule.

You can use the following methods to create backups.

  • The vSphere Export function.

  • Cloning.

  • VMware vSphere Data Protection, to create backups of the entire appliance.

  • vSphere Replication, to replicate the virtual appliance to another site.

  • VMware Recovery Manager, to enable high availability by backing up the appliance to a different data center.

You can use snapshots to backup virtual appliances only if you store or replicate them to a location other than the appliance location. If the snapshot image is accessible after a failure, using it is the most direct way to recover the appliance.

To preserve only the configuration information for the appliance, back up the following files, preserving the owner, group, and permissions for each file. These files are also backed up as part of exporting or cloning an appliance.

  • /etc/vcac/encryption.key

  • /etc/vcac/vcac.keystore

  • /etc/vcac/vcac.properties

  • /etc/vcac/security.properties

  • /etc/vcac/server.xml

  • /etc/vcac/solution-users.properties

  • /etc/apache2/server.pem

  • /etc/vco/app-server/sso.properties

  • /etc/vco/app-server/plugins/*

  • /etc/vco/app-server/vmo.properties

  • /etc/vco/app-server/js-io-rights.conf

  • /etc/vco/app-server/security/*

  • /etc/vco/app-server/vco-registration-id

  • /etc/vco/app-server/vcac-registration.status

  • /etc/vco/configuration/passwd.properties

  • /var/lib/rabbitmq/.erlang.cookie

  • /var/lib/rabbitmq/mnesia/**