If a failure occurs, a system administrator restores the vRealize Automation appliance. If a load balancer is used, the administrator restores the load balancer and the virtual appliances that it manages. If a host name changes during restoration, you must update configuration files appropriately.

About this task

You might need to restore a failed virtual appliance in the following circumstances:

  • You are running a minimal deployment and your only vRealize Automation appliance fails or becomes corrupted.

  • You are running a distributed deployment and some, but not all, virtual appliances fail.

  • You are running a distributed deployment and all virtual appliances fail.

How you restore a vRealize Automation appliance or virtual appliance load balancer depends on your deployment type and on which appliances failed.

  • If you are using a single virtual appliance whose name is unchanged, restore the virtual appliance, or redeploy it and restore a set of backed up files. No further steps are required.

  • If you are running a distributed deployment that uses a load balancer, and you change the name of the virtual appliance or the IP address of the load balancer, you must redeploy the appliance and restore its backup files. Also, you must regenerate and copy certificates for your deployment.

If you are redeploying, reconfiguring, or adding virtual appliances to a cluster, see the Installing vRealize Automation 7.0 documentation for vRealize Automation appliance for more information.

Procedure

  1. Redeploy the virtual appliance.

    You must also configure the Appliance Database after redeploying the vRealize Automation appliance if it is applicable to your system configuration.

  2. Restore all backed up files.
  3. Check the file permissions and owners for the restored files.
    1. Verify that the vcac user owns the files in the vcac directory and that only the vcac user has read and write permissions. Update any settings that have changed.
    2. Verify that the root user owns the files in the apache2 directory and that only the owner has read and write permissions. Update any settings that have changed.
    3. Verify that the vco user owns the files in the vco directory and that only the owner has read and write permissions. Update any settings that have changed.

    If the hostname or virtual IP address is unchanged, the restore procedure is finished.

  4. If the hostname of a stand-alone virtual appliance has changed, or if you are using a load balancer and its virtual IP address has changed, regenerate and copy certificates for each of the virtual appliances.
    1. Obtain a certificate by using a command of the following form:
      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe 
      \Vcac-Config.exe GetServerCertificates -url https://VA FQDN 
      --FileName .\Vcac-Config-time-stamp.data -v
    2. Register your solution user certificate by using a command of the following form:
      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe 
      \Vcac-Config.exe RegisterSolutionUser -url https://VA FQDN --Tenant vsphere.local 
      -cu administrator@vsphere.local -cp vmware --FileName .\Vcac-Config-time-stamp.data -v
    3. Register the event topics with the new solution user by using a command of the following form:
      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe RegisterCatalogTypes -v
    4. Move your solution user certificate information to the database by using a command of the following form:
      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe 
      \Vcac-Config.exe MoveRegistrationDataToDB -d vcac -s localhost 
      -f .\Vcac-Config-time-stamp.data -v
  5. Navigate to the vRealize Automation appliance management console and verify that the host, SSL, database, and SSO settings are correct.
  6. Update settings that changed.
  7. Start the vRealize Automation server service or save the SSO settings page.
  8. Configure the load balancer to distribute traffic to the virtual appliances.

What to do next

Restore the IaaS Website Service or Web Load Balancer