{"id":47663,"date":"2021-04-13T09:00:12","date_gmt":"2021-04-13T07:00:12","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=47663"},"modified":"2021-04-20T09:08:06","modified_gmt":"2021-04-20T07:08:06","slug":"vrealize-operations-manager-8-3-enable-continuous-availability-pt-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vrealize-operations-manager-8-3-enable-continuous-availability-pt-1\/","title":{"rendered":"vRealize Operations Manager 8.3 enable Continuous Availability - pt.1"},"content":{"rendered":"

\"vrops-enable-continuous-availability-01\"<\/p>\n

vRealize Operations Manager<\/span><\/a> (vROps) supports Continuous Availability (CA) feature that separates the vROps cluster<\/strong> into two Fault Domains.<\/p>\n

Fault Domains<\/strong>\u00a0are composed by\u00a0one or more analytics nodes<\/strong>\u00a0grouped according to their\u00a0physical location<\/strong>, and this configuration allows to stretch vROps nodes across vSphere<\/span> clusters<\/strong> protecting the analytics cluster against the loss of an entire Fault Domain.<\/p>\n

 <\/p>\n

Blog Series<\/h2>\n

vRealize Operations Manager 8.3 enable Continuous Availability - pt.1
\nvRealize Operations Manager 8.3 enable Continuous Availability - pt.2<\/a>
\nvRealize Operations Manager 8.3 enable Continuous Availability - pt.3<\/a><\/p>\n

 <\/p>\n

Pre-requisites<\/h2>\n

To implement vRealize Operations Manager CA three main components are required:<\/p>\n

    \n
  1. Master Node<\/strong> - it collects and stores data and by default is assigned to Fault Domain 1<\/strong>.<\/li>\n
  2. Replica Node<\/strong> - it is the replica of the Master Node and is assigned to Fault Domain 2<\/strong>. Master and Replica creates a pair. In case the Master Node fails, the replica node can take over all functions<\/strong> that the primary node provides.<\/li>\n
  3. Witness Node<\/strong> - it doesn't store or collect any data but it serves as tiebreaker<\/strong> in case the communication between the two Fault Domains is lost avoiding the split-brain situation<\/a>. The Witness brings one of the Fault Domains offline to avoid data inconsistency<\/strong> issues. Once the connection has been restored, the offline Fault Domain can be resumed through the Bring Online<\/strong> button. The Witness must be located in a third location<\/strong> which would not be affected by the loss of either Fault Domain 1 or 2.<\/li>\n<\/ol>\n

    \"vrops-enable-continuous-availability-02\"<\/p>\n

    The number of Data Nodes must always be an even number<\/strong> with a maximum of 16<\/strong> (8 pairs). If a Data Node is added to Fault Domain 1 it must have a pair<\/strong> in Fault Domain 2 to preserve and replicate data that is added to its peer.<\/p>\n

    \"vrops-enable-continuous-availability-03\"<\/p>\n

    If Data Nodes cannot be split into different\u00a0vSphere<\/span> clusters<\/strong>, do not enable CA.<\/p>\n

    If Remote Collectors<\/strong> are deployed, they are added outside the Fault Domain.<\/p>\n

    Since several factors must be considered to size a vRealize Operations Manager cluster, you can use the online sizing tool<\/a> to properly size your vROps cluster<\/strong>.<\/p>\n

     <\/p>\n

    How Continuous Availability works<\/h2>\n

    In case of a Fault Domain failure, the remaining active Fault Domain and the Witness Node will keep the cluster alive by promoting the Replica Node<\/strong> as the new Master Node. The cluster will run in degraded mode<\/strong>.<\/p>\n

    \"vrops-enable-continuous-availability-04\"<\/p>\n

    The failover procedure is automatic and takes two\/three minutes to resume<\/strong> vROps operations and restart data collection.<\/p>\n

    Since the cluster runs in degraded mode, you need to perform the following actions to fix:<\/p>\n