Use of a load balancer to provide multiple users a single URL for accessing the vRealize Operations Manager Use a load balance to group multiple remote collectors when using End Point Operations Manager agents to igh availability and redundan Depl The Windows installer is no longer an available deployment option after rEalize Operations Manager 6.4. The RHEL installer is available in vRealize Operations Manager 6.5 but is now deprecated in vRealize Operations Manager 6.6. There is no migration path from either Windows or RhEL to the Virtual Appliance Do not modify or install third party applications on the appliance When using the virtual appliance, installation or modifications of third party applications is unsupported and may ause problems to rEalize Operations Manager · Deploy the Va with FQDN for the vRealize Operations Manager node. Simply using hostname may communication problems with the node Use Thick Provisioning Eager Zeroed When deploying nodes, set disk provisioning to"Thick Provision Eager Zeroed for most optimum performance When deploying Medium size nodes, increase the VM hardware level The default hardware is set to"7 and limits the number of vCPUs per node. To increase the number of vCPUs when scaling a medium node to a large node, as example, the hw level must be set to a higher value Leverage remote collectors Use remote collectors where possible to navigate firewalls, reduce bandwidth across data centers, connect to remote data sources, or reduce the load on the vRealize Operations Manager analytics cluste Upgrade If upgrading to rEalize Operations Manager 6.7 or vRealize Operations Manager 7.0, run the appropriate versioned Pre-Upgrade Assessment Tool on your current vRealize Operations Manager before performing the grade to view the possible impact on your custom content and to plan appropriate maintenance efforts for Seehttps://www.vmware.com/products/vrealize-operations/upgrade-center.html Ensure the environment is fully functional before starting an upgrade. It is recommended to make a list of what works(or does not work ) to confirm the same functionality post upgrade Customized content should be backed up and saved for any potential overwrites or losses during upgrade Snapshot VMs with cluster offline before upgrading vRealize Operations Manager Best Practices/svRealize Operations Manager Best Practices /9 Use of a load balancer to provide multiple users a single URL for accessing the vRealize Operations Manager cluster alleviates the need for users to remember logging into separate node names and accessing specific nodes. • Use load balancers to provide high availability for remote collectors with End Point Operations Manager agents Use a load balance to group multiple remote collectors when using End Point Operations Manager agents to provide high availability and redundancy. Deployment • Use the Virtual Appliance (VA) The Windows installer is no longer an available deployment option after vRealize Operations Manager 6.4. The RHEL installer is available in vRealize Operations Manager 6.5 but is now deprecated in vRealize Operations Manager 6.6. There is no migration path from either Windows or RHEL to the Virtual Appliance. • Do not modify or install third party applications on the appliance When using the virtual appliance, installation or modifications of third party applications is unsupported and may cause problems to vRealize Operations Manager. • Deploy the VA with FQDN Register a fully qualified domain name for the vRealize Operations Manager node. Simply using hostname may not properly resolve and may experience communication problems with the node. • Use Thick Provisioning Eager Zeroed When deploying nodes, set disk provisioning to “Thick Provision Eager Zeroed” for most optimum performance. • When deploying Medium size nodes, increase the VM hardware level The default hardware is set to “7” and limits the number of vCPUs per node. To increase the number of vCPUs when scaling a medium node to a large node, as example, the HW level must be set to a higher value. • Leverage Remote Collectors Use remote collectors where possible to navigate firewalls, reduce bandwidth across data centers, connect to remote data sources, or reduce the load on the vRealize Operations Manager analytics cluster. Upgrade • If upgrading to vRealize Operations Manager 6.7 or vRealize Operations Manager 7.0, run the appropriate versioned Pre-Upgrade Assessment Tool on your current vRealize Operations Manager before performing the upgrade to view the possible impact on your custom content and to plan appropriate maintenance efforts for adjusting impacted custom content. See https://www.vmware.com/products/vrealize-operations/upgrade-center.html. • Verify existing functionality before upgrading Ensure the environment is fully functional before starting an upgrade. It is recommended to make a list of what works (or does not work) to confirm the same functionality post upgrade. • Backup customized content before upgrade Customized content should be backed up and saved for any potential overwrites or losses during upgrade. • Snapshot VMs with cluster offline before upgrading