Implement all best practices when you deploy a production instance of vRealize Operations Manager.
Analytics nodes consist of a master node, replica nodes, and data nodes.
Deploy analytics nodes in the same vSphere Cluster.
Deploy analytics nodes on storage of the same type.
Depending on the size and performance requirements for analytics nodes, apply Storage DRS Anti-Affinity rules to ensure that nodes are on separate datastores.
Set Storage DRS to manual for all vRealize Operations Manager analytics nodes.
If you deploy analytics nodes into a highly consolidated vSphere cluster, configure resource reservation to ensure optimal performance. Ensure that the virtual CPU to physical CPU ratio is not negatively impacting the performance of analytic nodes by validating CPU ready time and CPU co-stop.
Analytics nodes have a high number of vCPUs to ensure performance of the analytics computation that occurs on each node. Monitor CPU Ready time and CPU Co-Stop to ensure that analytics nodes are not competing for CPU capacity.
If the sizing guideline provides several configurations for the same number of objects, use the configuration which has the least number of nodes. For example, if the number of objects is 120, 000, configure the node size as 4 extra large nodes instead of 12 large nodes.
Management Packs and Adapters
Various management packs and adapters have specific configuration requirements. Ensure that you are familiar with all prerequisites before you install a solution and configure the adapter instance.
Deploy vRealize Operations Manager with VMware virtual appliance.
vRealize Operations Manager 6.5 was the final version of the product to support RHEL installations. vRealize Operations Manager 6.4 was the final version of the product to support Microsoft Windows installations.