A system administrator uses backups to restore vRealize Operations Manager to a functional state after a system failure.

You must start the vRealize Operations Manager components in a specifiedd order after the restore is complete.

vRealize Operation Manager Startup Order

The common restore scenarios for vRealize Operations Manager systems include a full restore of a single-node virtual appliance system and restore of multiple-node virtual appliance clusters.

This scenario restores a single node system on the same host.

1

After the restore is complete, power on the VM.

2

Verify that you have set up a static IP address for the node and that the IP address is restored.

3

Log in to the node to verify that all your data is preserved and that all vmware-vcops services are running.

4

If your root password was reset, you must change it now.

For incremental backups, a user must create a cumulative differential policy. Every backup after a full backup is an incremental backup.

Note

If you restore to another host, you must power off the environment at the original location and start the environment on the new host.

This scenario restores multiple-node virtual appliance clusters.

1

The restore can start in any order, but after the restore is complete, you must power on the nodes in the following order:

a

master

b

replica

c

data

d

remote collector

Ensure that each node is online before attempting to start the next component.

2

Verify that you have set up a static IP address for the node and that the IP address is restored.

3

Log in to the administrator interface of the master node and verify that all the nodes are online and running. Log in to each node to verify that all your data is preserved and all of the vmware-vcops services are up and running by using the vmware-vcops status command.

4

Log in to the administrator interface of the master node.

a

Verify that high availability is enabled. If the Enable High Availability button appears, high availability was disabled during the backup and restore process. Enable high availability.

b

Verify that all nodes are collecting metrics.

5

If your root password was reset, you must change it now.

6

(Optional) If a node in a non-high availability cluster does restart, you must take it offline with the administrator interface.

7

(Optional) If the replica node in a high availability cluster does not restart, you must assign a new master-replica node.

8

(Optional) You can execute an incremental backup only if a full backup already exists. After an incremental backup, you can choose to restore to either the full or incremental backup.

Note

If you restore to another host, you must power off the environment at the original location and start the environment on the new host.

After the restore operation of the VM is finished, verify that vRealize Operations Manager is in a functional state.

Note

Do not power on any vRealize Operations Manager nodes during the restore operation. Wait until the entire cluster restore has finished before you power on any node.

1

For a non-HA cluster, power on the master node followed by the data nodes. For an HA environment, power on the master node followed by replica and other data nodes.

2

Use SSH to log in to the vRealize Operations Manager master node to verify the vRealize Operations Manager service status.

a

Use SSH to switch to the vRealize Operations Manager master node and enter the service vmware-vcops status command.

# service vmware-vcops status
Slice Online-true
admin Role Enabled-true
        vRealize Operations vPostgres Replication Database is running (31810).
        vRealize Operations Gemfire Locator is running (31893).
data Role Enabled-true
        vRealize Operations vPostgres Database is running (32013).
        vRealize Operations Cassandra Distributed Database is running (21062).
        vRealize Operations Analytics is running (32142).
        vRealize Operations Collector is running (32225).
        vRealize Operations API is running (32331).
ui Role Enabled-true
remote collector Role Enabled-false

b

Confirm that the admin, data, and UI roles are running.

3

Log in to the administration UI of the master node and verify that all nodes in the cluster are up and collecting data.

a

Open a browser and go to the administration UI of the master node: https://<Master_Node_IP>/admin/login.action.

b

Log in as administrator.

c

Verify that each node is in the Online status.

d

Click each node and verify that adapter instances are in the Data receiving status.

4

If the High Availability state indicates Enabled, degraded after the restore, one or more nodes are inaccessible, and you must power on the nodes or you must restart the cluster.

a

Open a browser and go to the administration UI of the master node: https://<Master_Node_IP>/admin/login.action.

b

Verify that all nodes are in Running state and Online .

1

If a node is not in Running state and Online, power on the node and start it online.

2

If all nodes are in Running state and Online, but HA is still Enabled, degraded, restart the cluster.