You prepare for vRealize Operations installation by evaluating your environment and deploying enough vRealize Operations cluster nodes to support how you want to use the product. Workflow of vRealize Operations InstallationThe vRealize Operations virtual appliance installation process consists of deploying the vRealize Operations OVA, 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 ClusterThe resources needed for vRealize Operations 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 EnvironmentWhen you deploy vRealize Operations, 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 Cluster NodesAll vRealize Operations clusters consist of a master node (primary node), an optional replica node for high availability or continously availability, optional data nodes, and optional remote collector nodes. About vRealize Operations Remote Collector NodesA remote collector node is an additional cluster node that allows vRealize Operations to gather more objects into its inventory for monitoring purposes. Unlike the data nodes, the remote collector nodes only perform the collector role of vRealize Operations. These remote collectors do not store data or process any analytics functions. Remote collectors collect data from integrated objects and then forward the data back to the primary node. The primary node then processes the data which you then view as reports and analytics. About vRealize Operations High AvailabilityvRealize Operations supports high availability (HA). HA creates a replica for the vRealize Operations primary node and protects the analytics cluster against the loss of a node. About vRealize Operations Continuous AvailabilityvRealize Operations supports continuous availability (CA). CA separates the vRealize Operations cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain.