You can use the following information specific to disaster recovery for vRealize Operations Manager 6.6 and later.
Guidelines for vRealize Operations Manager Migration and Recovery
You can use the following guidelines for recovering vRealize Operations Manager by using Site Recovery Manager.
All examples for scripts and directory paths assume that the default parameters were accepted for installation. The actual path needs to be modified, if you have not used default parameters during installation.
In some cases, SRM might not restore the vApp properties needed by vRealize Operations Manager. In such case, see KB article 57091.
Migrate or recover vRealize Operations Manager virtual machines to an identical network configuration.
If the recovery site is configured to have the same network configuration as the protected site and a mapping is created between the identical networks, configure all replicated vRealize Operations Manager virtual machines to be started with the same IPs, because these virtual machines are the protected nodes. The recovered system will become operational after the planned migration or disaster recovery has finished successfully.
Migrate or recover vRealize Operations Manager virtual machines to a different network configuration (DHCP). If the recovery site is configured to have a different network configuration than the protected site and a DHCP server exists, all protected vRealize Operations Manager instances must be reconfigured to use the new network addresses.
Migrate or recover vRealize Operations Manager virtual machines to a different network configuration (static IPs). The recovery site might be configured to have a different network configuration than the protected site and the Site Recovery Manager might explicitly configure the static IPs for the vRealize Operations Manager instances. As a result, you must reconfigure all the nodes to use the new network addresses.
Testing a recovery plan. After you execute a test recovery plan, the virtual machines on the protected site remain powered on. The powered on state can cause some communication issues between the vRealize Operations Manager nodes on both sites. Always clean up the executed recovery test.
vRealize Operations Manager does not support quiesced snapshots. If you are using a disaster recovery tool that supports quiesced snapshots, make sure to disable quiescing.
The load balancing configuration for vRealize Operations Manager disaster recovery is out of scope for this document.