Using the StorageHostIds attribute

If the bunker site is a cluster, make sure that the bunker RVG group is never online when the bunker disk group is imported on the Primary cluster. Otherwise, the bunker disk group would be imported on two hosts at the same time, which results in split brain.

If an automatic failover occurs in the Primary cluster, the agent refers to the StorageHostIds attribute to help ensure that the bunker RVG is not imported on both a bunker host and a host in the Primary cluster at the same time. The Primary cluster does not import the bunker disk group if the disk group is already imported on a host in the bunker cluster.

To determine the hostid, issue the following command on each node:

# vxdctl list
        Volboot file
        version: 3/1
        seqno:   0.5
        cluster protocol version: 60
        hostid:  vvrnode1
        defaultdg:  pdg

If the hostid of a bunker node changes, you must change the StorageHostIds attribute to reflect the new value using the following command:

# hares modify RvgPriResName StorageHostIds value