You prepare for vRealize Operations Manager installation by evaluating your environment and deploying enough vRealize Operations Manager cluster nodes to support how you want to use the product.
Workflow of vRealize Operations Manager Installation vRealize Operations Manager virtual appliance installation process consists of deploying the vRealize Operations Manager OVF, once for each cluster node, accessing the product to set up cluster nodes according to their role, and logging in to configure the installation. Sizing the vRealize Operations Manager Cluster vRealize Operations Manager depend on how large of an environment you expect to monitor and analyze, how many metrics you plan to collect, and how long you need to store the data. Complexity of Your Environment vRealize Operations Manager , the number and nature of the objects that you want to monitor might be complex enough to recommend a Professional Services engagement. About vRealize Operations Manager Cluster Nodes vRealize Operations Manager clusters consist of a master node (primary node), an optional replica node for high availability, optional data nodes, and optional remote collector nodes. About vRealize Operations Manager Remote Collector Nodes vRealize Operations Manager to gather more objects into its inventory for monitoring. Unlike data nodes, remote collector nodes only include the collector role of vRealize Operations Manager , without storing data or processing any analytics functions. About vRealize Operations Manager High Availability vRealize Operations Manager supports high availability (HA). HA creates a replica for the vRealize Operations Manager primary node and protects the analytics cluster against the loss of a node. About vRealize Operations Manager Continuous Availability vRealize Operations Manager supports continuous availability (CA). CA separates the vRealize Operations Manager cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain.
