xHA with Server Groups - BlueCat Address Manager - 9.1.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.1.0

An xHA pair can be linked to a Server Group to inherit deployment options configured on the Server Group. The following describes the scenarios and behaviours of xHA pairs in Server Groups.

Creating xHA pairs with one server in a Server Group

When you create an xHA pair where one server is linked to a Server Group while the other server is not, the resulting xHA pair will be linked to the Server Group only if the Active node belongs to a Server Group. If the Passive node in the xHA pair belongs to the Server Group, the resulting xHA pair will not belong to a Server Group

Example 1

You have two DNS/DHCP Servers: Server 1 and Server 2 — Server 1 is linked to Server Group A. You create an xHA pair with Server 1 and Server 2 where Server 1 is the Active node and Server 2 is the Passive node. The resulting xHA pair will be linked to Server Group A, as the Active node (Server 1) was linked to Server Group A before the xHA pair was created.

Example 2

You have two DNS/DHCP Servers: Server 1 and Server 2 — Server 1 is linked to Server Group A. You create an xHA pair with Server 1 and Server 2 where Server 1 is the Passive node and Server 2 is the Active node. The resulting xHA pair will not be linked to a Server Group, as the Active node (Server 2) was not linked to a Server Group before the xHA pair was created.

Creating xHA pairs with two servers in separate Server Groups

When you create an xHA pair where one server is linked to a Server Group while the other server is linked to a different Server Group, the resulting xHA pair will be linked to the Server Group to which the Active node was linked. The Passive node is not linked to the Server Group and is hidden from the list of servers in the Server Group in which it belongs. Deployment options configured on the xHA pair will apply to the Active node and continue to replicate to the Passive node to ensure that the data on the Passive node is up-to-date.

If a failover occurs, the Passive node will become the Active node and the former Active node will become the Passive node, but the now Active node will be linked to the former Active node's Server Group while the now Passive node will not be linked to the Server Group and is hidden from the server list.

Example 3

You have two DNS/DHCP Servers: Server 1 and Server 2 — Server 1 is linked to Server Group A and Server 2 is linked to Server Group B. You create an xHA pair with Server 1 and Server 2 where Server 1 is the Active node and Server 2 is the Passive node. The resulting xHA pair will be linked to Server Group A, as the Active node (Server1) was linked to Server Group A before the xHA pair was created. The Passive node (Server 2) is hidden from the list of servers in Server Group B.

When an xHA failover occurs, the now Active node (Server 2) is linked to Server Group A while the now Passive node (Server 1) remains in Server Group A but is hidden from the list of servers in Server Group A.

Attention: If you break an xHA pair that is linked to a server group, the Passive server returns to the server group state that it was in when the xHA pair was created. For more information, refer to Breaking xHA with server groups.