In Region B, deploy 2 remote collector nodes for vRealize Operations Manager to monitor the Management and Compute vCenter Server instances, NSX for vSphere, and storage components in SDDC.
About this task
Deploying a separate group of remote collectors in Region B makes the data collection in each region independent from the location of the analytics cluster. If you fail over the analytics cluster, data collection continues for those nodes that are accessible in the active region.
Prerequisites for Deploying the Remote Collectors in Region B Before you deploy the remote collector nodes of vRealize Operations Manager in Region B, verify that your environment satisfies the requirements for this deployment.
Deploy the Remote Collector Virtual Appliances in Region B After you deploy and configure the analytics and remote collector cluster nodes in Region A, use the vSphere Web Client to deploy the two virtual appliances for the remote collectors in Region B. The remote collectors are used to forward data from the vCenter Server instances in Region B to the analytics cluster of vRealize Operations Manager.
Connect the Remote Collector Nodes to the Analytics Cluster in Region B After you deploy the virtual appliances for the remote collector nodes on the Management vCenter Server in Region B, configure the settings of the remote collectors and connect them to the analytics cluster.
Configure a DRS Anti-Affinity Rule for vRealize Operations Manager Remote Collectors in Region B To protect the vRealize Operations Manager virtual machines from a host-level failure, configure vSphere DRS to run the remote collector virtual machines on different hosts in the management cluster in Region B.
Group Remote Collector Nodes in Region B After you configure the remote collector nodes for vRealize Operations Manager in Region B, join the remote collectors in a group for adapter resiliency in the cases where the collector experiences network interruption or becomes unavailable.