Consider additional storage and io requirements for longer data retention For those times when longer data retention periods are required, consider additional storage and increased I0 requirements. For example, retail businesses may need to keep more than one year to account for seasonal peaks Leverage the additional time series retention to keep longer historical data while minimizing the time series data The default setting for additional time series retention is thirty-Six mon Adjust the default value to a necessary Only install Management Packs that are available on the VMware Solution Exchange There are several management packs available for vRealize Operations Manager, however, only management packs certified and supported by VMware are available on the VMware Solution Exchange Before adding Management Packs, verify the additional metrics they will providing The metric name may look correct but may not al ways mean it is what you want. Be sure that the metrics from management packs are what you really need and used properly; otherwise, disable unnecessary metrics Architecture High Availability(HA) Understand what HA provides(or does not provide) before enabling(or disabling) Enabling HA may require double the resources, as data is stored redundantly in two nodes as opposed to only on one node when Ha is disabled. Since the data is being stored in two nodes, this limits the total capacity by 50% For example, a deployment of 6 extra-large nodes will support the maximum number of objects rEalize HA DIsabled HA Enabled 6.6 180.000 240.000 120,000 7.0 HA will allow losing only one data node for the cluster to remain functional. It is important to understand and Enable ha only after all nodes in the cluster have been added and are online fit the appropriate sizing and then enable HA. If adding new data nodes to an existing cluster, add as many dal o dd all data nodes to the cluster before enabling HA. On new deployments, add data nodes to build the cluster nodes as necessary, then enable HA. The goal is to minimize the number of times for enabling HA; the process to enable Ha can be very disruptive so perform only when necessary Deploy analytics cluster nodes on separate hosts for redundancy and isolation If possible, establish a 1: I mapping for nodes to hosts. This will protect the cluster if one host goes down, then vRealize Operations Manager Best Practices/vRealize Operations Manager Best Practices /7 • Consider additional storage and IO requirements for longer data retention For those times when longer data retention periods are required, consider additional storage and increased IO requirements. For example, retail businesses may need to keep more than one year to account for seasonal peaks. • Leverage the additional time series retention to keep longer historical data while minimizing the time series data retention period. The default setting for additional time series retention is thirty-six months. Adjust the default value to a necessary period and lower the time series data retention period to save on the amount of data being retained. • Only install Management Packs that are available on the VMware Solution Exchange There are several management packs available for vRealize Operations Manager; however, only management packs certified and supported by VMware are available on the VMware Solution Exchange. • Before adding Management Packs, verify the additional metrics they will providing The metric name may look correct but may not always mean it is what you want. Be sure that the metrics from management packs are what you really need and used properly; otherwise, disable unnecessary metrics. Architecture High Availability (HA) • Understand what HA provides (or does not provide) before enabling (or disabling) Enabling HA may require double the resources, as data is stored redundantly in two nodes as opposed to only on one node when HA is disabled. Since the data is being stored in two nodes, this limits the total capacity by 50%. For example, a deployment of 6 extra-large nodes will support the maximum number of objects: vRealize Operations Manager HA Disabled HA Enabled 6.6 180,000 90,000 6.7 240,000 120,000 7.0 240,000 120,000 • HA will allow losing only one data node for the cluster to remain functional. It is important to understand and weigh the cost of the extra resources to the benefits that HA provides. • Enable HA only after all nodes in the cluster have been added and are online Add all data nodes to the cluster before enabling HA. On new deployments, add data nodes to build the cluster to fit the appropriate sizing and then enable HA. If adding new data nodes to an existing cluster, add as many data nodes as necessary, then enable HA. The goal is to minimize the number of times for enabling HA; the process to enable HA can be very disruptive so perform only when necessary. • Deploy analytics cluster nodes on separate hosts for redundancy and isolation If possible, establish a 1:1 mapping for nodes to hosts. This will protect the cluster if one host goes down, then