only one node is lost and the cluster remains functional. If it is not possible to establish a 1: I mapping for nodes to host, make sure to separate the master node and master replica node on different hosts. This will safeguard the cluster if one of these hosts were to go down. Use anti-affinity rules that keep nodes on specific hosts in the vSphere cluster To keep nodes separately on different hosts, use anti-affinity rules to prevent grouping of nodes on specific hosts The idea is to prevent multiple nodes from going down if hosted on one node Roles may change for nodes so statically naming a node a specific name may be confusing. For example, a node named" may no longer be the actual master node after promoting the replica node. This will avoid user confusion associated with poor naming convention. Ha is not a Disaster Recovery(dr)strategy Hsed os e ealize hopera tons Ma nager is not a disaster revere mechanism sh a separate a wis alton me st ontinue running if either the master node, the replica node or one data node fails. The entire cluster does not recover if multiple nodes fail at the same time · Hosts need to be on th For performance and consistency, use of the same storage is required Remote Collectors Consider using Remote Collectors for local collections with larger vEnters(7K objects) Using remote collectors will help to reduce bandwidth across data centers and reduce the load on the rEalize Operations Manager analytics cluster Create collector groups when using multiple Remote Collectors When utilizing multiple remote collectors for one vCenter, create a collector group to provide high availability and Deploy or update Remote Collectors to the same version of the Analytics nodes Do not utilize mixed versions of Remote Collectors and Analytics nodes. Not only is a cluster running mixed versions unsupported, it may exhibit potential problems Use Remote Collectors when using End Point Operations Manager(EPOps)agents Use remote collectors to isolate collection from End Point Operations Manager agents and reduce the load on the Remote Collectors based on number of collecting objects/metrics remote collectors using the default sizing of standard and large nodes to accommodate the number of objects Remote Collectors are necessary to be included in the backup strategy nclude all remote collectors when taking a backup to restore the entire cluster health. Load Balancers Use load balancers to provide a single Ul entry for users vRealize Operations Manager Best Practices/svRealize Operations Manager Best Practices /8 only one node is lost and the cluster remains functional. If it is not possible to establish a 1:1 mapping for nodes to host, make sure to separate the master node and master replica node on different hosts. This will safeguard the cluster if one of these hosts were to go down. • Use anti-affinity rules that keep nodes on specific hosts in the vSphere cluster To keep nodes separately on different hosts, use anti-affinity rules to prevent grouping of nodes on specific hosts. The idea is to prevent multiple nodes from going down if hosted on one node. • Name nodes independent of role Roles may change for nodes so statically naming a node a specific name may be confusing. For example, a node named ‘Master’ may no longer be the actual master node after promoting the replica node. This will avoid user confusion associated with poor naming convention. • HA is not a Disaster Recovery (DR) strategy HA for vRealize Operations Manager is not a disaster recovery mechanism so a separate DR solution must be used. See https://www.vmware.com/support/pubs/vmware-vrealize-suite-pubs.html . HA will allow the cluster to continue running if either the master node, the replica node or one data node fails. The entire cluster does not recover if multiple nodes fail at the same time. • Hosts need to be on the same storage For performance and consistency, use of the same storage is required. Remote Collectors • Consider using Remote Collectors for local collections with larger vCenters (>7K objects) Using remote collectors will help to reduce bandwidth across data centers and reduce the load on the vRealize Operations Manager analytics cluster. • Create collector groups when using multiple Remote Collectors When utilizing multiple remote collectors for one vCenter, create a collector group to provide high availability and redundancy. • Deploy or update Remote Collectors to the same version of the Analytics nodes Do not utilize mixed versions of Remote Collectors and Analytics nodes. Not only is a cluster running mixed versions unsupported, it may exhibit potential problems. • Use Remote Collectors when using End Point Operations Manager (EPOps) agents Use remote collectors to isolate collection from End Point Operations Manager agents and reduce the load on the vRealize Operations Manager analytics cluster. • Size Remote Collectors based on number of collecting objects/metrics Size remote collectors using the default sizing of standard and large nodes to accommodate the number of objects and metrics, which it will be collecting. • Remote Collectors are necessary to be included in the backup strategy Include all remote collectors when taking a backup to restore the entire cluster health. Load Balancers • Use load balancers to provide a single UI entry for users