General Requirements

VMware Aria Operations
version. All nodes must run the same
VMware Aria Operations
version.
For example, do not add a version 6.1 data node to a cluster of
VMware Aria Operations
6.2 nodes.
Analytics Cluster Deployment Type. In the analytics cluster, all nodes must be the same kind of deployment.
Witness Node Deployment Type. The witness node must be the same kind of deployment.
Analytics Cluster Node Sizing. In the analytics cluster, CPU, memory, and disk size must be identical for all nodes.
Primary, replica, and data nodes must be uniform in sizing.
Witness Node Sizing. The witness node has only one size and may be of different sizes from the uniform analytics cluster node size
Geographical Proximity. You may place analytics cluster nodes in different
vSphere
clusters, but the nodes must reside in the same geographical location.
Different geographical locations are not supported.
Witness Node Placement. You may place the witness node in a different
vSphere
cluster separate from the analytics nodes.
A
VMware Aria Operations
cluster can have only one witness node.
Virtual Machine Maintenance. When any node is a virtual machine, you may only update the virtual machine software by directly updating the
VMware Aria Operations
software.
For example, going outside of
VMware Aria Operations
to access
vSphere
to update VMware Tools is not supported.
Redundancy and Isolation. If you expect to activate HA, place analytics cluster nodes on separate hosts. See About VMware Aria Operations High Availability.
If you expect to activate CA, place analytics cluster nodes on separate hosts in fault domains, stretched across
vSphere
clusters. See About VMware Aria Operations Continuous Availability.

Requirements for Solutions