You can deploy and configure additional nodes so that vRealize Operations can support larger environments. Figure 1. Workflow - Resize your cluster Gathering More Data by Adding a vRealize Operations Remote Collector NodeYou deploy and configure remote collector nodes so that vRealize Operations can add to its inventory of objects to monitor without increasing the processing load on vRealize Operations analytics. Adding High Availability to vRealize OperationsYou can dedicate one vRealize Operations cluster node to serve as a replica node for the vRealize Operations primary node. Adding Continuous AvailabilityContinuous availability prevents data loss in the event of one or more node failures. This mode requires one witness node, one primary node, and one data node divided across two fault domains. The witness node lies outside the fault domains. By default, the primary node is assigned to Fault Domain 1. The data node becomes the replica node and is assigned to Fault Domain 2. The primary node and the replica node create a pair. The number of data nodes including the primary node should always be an even number not exceeding 16. Each data node added to Fault Domain 1 must have a pair in Fault Domain 2 to preserve and replicate data that is added to its peer. vRealize Operations Cluster and Node MaintenanceYou perform cluster and node maintenance procedures to help your vRealize Operations perform more efficiently cluster and node maintenance involves activities such as changing the online or offline state of the cluster, fault domains, or individual nodes, enabling or disabling high availability (HA) or continuous availability (CA), reviewing statistics related to the installed adapters, and rebalancing the workload for a better performance. Troubleshooting