Reviewing the configuration

Last published : Aug 05, 2026
This configuration overview highlights the active/passive high availability within a cluster and disaster recovery between two sites. In an active/passive configuration, one or more application virtual servers can exist in a cluster, but each server must be managed by a service group configured with a distinct set of nodes in the cluster.
Active/passive clusters involve one-to-one failover capabilities. For instance, if you have two nodes on each site (SYSTEM1 and SYSTEM2 on the primary site, SYSTEM5 and SYSTEM6 on the secondary site), SYSTEM1 can fail over to SYSTEM2, and SYSTEM5 can fail over to SYSTEM6.The figure that follows illustrates the cluster configuration on the primary site. For a view of the configuration that includes both sites, refer to the illustration in the topic:
Figure: DR configuration primary site
DR configuration primary site
This configuration does not include DMP. For information about DMP and clustering:
The following are some other key points about the configuration:
  • A Microsoft failover cluster must be running before you install InfoScale Storage.
Installing InfoScale Storage requires a reboot, but a reboot on the active cluster node causes it to fail over. Thus, Veritas recommends that you use a "rolling install" procedure to install InfoScale Storage first on the inactive cluster node, then move the active cluster resources to the other node, and install on the now inactive node.
  • SFW adds the advantage of the dynamic mirrored quorum. The quorum resource maintains the cluster database and critical recovery information in a recovery log.
Microsoft clustering only supports a basic physical disk and does not enable you to mirror the quorum resource. One advantage of SFW is that it provides a dynamic mirrored quorum resource for Microsoft clustering. If a quorum disk fails, a mirror on another disk (another plex) takes over and the resource remains online. For this configuration, Veritas recommends creating a three-way mirror for the quorum to provide additional fault tolerance. If possible, do not use the disks assigned to the quorum for any other purpose.
After InfoScale Storage is installed on the cluster nodes, the next task is to create one or more cluster disk groups with SFW and set up the volumes for your application. At the same time, you can create the disk group and mirrored volume for the dynamic quorum resource.
The quorum disk group on each site does not get replicated because each cluster has its own quorum.