You can run the backup and restore script to ensure that VMware vRealize Operations Manager continues to receive data after the vRealize Application Remote Collector instance becomes unavailable. All the existing endpoints that are configured will automatically connect back to vRealize Application Remote Collector and continue to send data after you restore the vRealize Application Remote Collector instance. This is an optional task which you can run if you are facing issues with the vRealize Application Remote Collector appliance.

The task is divided into two parts. The first part involves performing an on-demand back up of the vRealize Application Remote Collector connection and configuration details. A cron job also performs the back up automatically every day.

The second part involves restoring the vRealize Application Remote Collector instance using the backup file that you created, or the backup file created by the cron job.

Prerequisites

  • vRealize Application Remote Collector appliance must be configured with a static I.P. or static FQDN. The endpoints must be configured.
  • Back up the network configuration details of the vRealize Application Remote Collector appliance. Capture the network configuration details of vRealize Application Remote Collector either using the VAMI UI or vCenter Server Tools. Keep the network details available when you restore the vRealize Application Remote Collector appliance from the backup.
  • The sizing of the new vRealize Application Remote Collector appliance that you are restoring a backup to, should be greater or equal to the old appliance. The network configuration, static I.P. or static FQDN should be the same. This is to enable the endpoint VMs to reach the new appliance.

Procedure

  1. Back up a running instance of vRealize Application Remote Collector by making a copy of the connection and configuration details.
    1. Connect to the virtual machine running vRealize Application Remote Collector using SSH.
    2. Enter the following command to access the scripts folder:
      cd /ucp/ucp-config-scripts
    3. Run the arc-state-bundle.sh script with the backup option. The script performs a back up or restore task based on the option you provide.
      ./arc-state-bundle.sh backup_state
      Running this script pushes the backup file to the /ucp-bkup/state-bundles folder. The filename is in the format Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar. This file contains the connection and configuration details for the endpoints.
    4. Archive the Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file to a remote location.
  2. A cron job also runs every day and backs up the Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file. The .tar file is stored for five days. On the sixth day, the oldest .tar file is deleted and replaced. In order to restore the vRealize Application Remote Collector appliance from the .tar file, archive the file to a remote location.
  3. Restore the backed up configuration files to a new vRealize Application Remote Collector appliance.
    1. Configure the new vRealize Application Remote Collector appliance with the same network and IP configuration as the previous appliance. This information is available in the network configuration file that you backed up.
    2. Connect to the VM running vRealize Application Remote Collector using SSH.
    3. Retrieve the latest Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file from the archive, and copy it to a location which is accessible by the vRealize Application Remote Collector appliance.
    4. Enter the following command to access the scripts folder:
      cd /ucp/ucp-config-scripts
    5. Run the arc-state-bundle.sh script. Use the restore option. Provide the location of the Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file.
      ./arc-state-bundle.sh restore_state <<location of the backed up tar file, with the filename.tar extension>>

      The above command looks for the file starting with Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar to load. The script configures the new vRealize Application Remote Collector appliance with the same settings as the instance that went down, and restarts all the containers.

      For example, the following command restores the appliance from the state bundle /tmp/fromArchive/Application-Remote-Collector-State-Bundle_2019-04-02-18:31:36.tar from the /tmp/fromArchive/ location:

      ./arc-state-bundle.sh restore_state "/tmp/fromArchive/Application-Remote-Collector-State-Bundle_2019-04-02-18:31:36.tar"

Results

The restoration of the vRealize Application Remote Collector is complete, and it is available again. The existing endpoints connect back to vRealize Application Remote Collector and continue to send data.

What to do next

If the vRealize Application Remote Collector instance was sending data to VMware vRealize Operations Manager, then adapter collection might fail when the vRealize Application Remote Collector instance stops working. In the VMware vRealize Operations Manager, the status of the adapter instances changes to indicate that it has failed. If this happens, you must manually start the adapter instance after restoring the vRealize Application Remote Collector appliance.