A typical disaster recovery configuration requires that you have a source host on the primary site and a destination host on the secondary site. The application data is stored on the primary site and replicated to the secondary site by using a tool such as the Volume Replicator. The primary site provides data and services during normal operation. If a disaster occurs on the primary site and its data is destroyed, a secondary host can take over the role of the primary host to make the data accessible. The application can be restarted on that host.

This Disaster Recovery section includes a SFW-Microsoft clustering-Volume Replicator configuration. The configuration is described with a generic database application that includes both data and a database log.

The illustration below shows the SFW HA-Volume Replicator configuration with Microsoft clustering. For a SFW-Microsoft clustering-Volume Replicator configuration, at least two disk groups are necessary - one for the application and one for the quorum resource volume, which has to be in a separate disk group, as shown in the illustration that follows.

The quorum volume is not replicated from the primary site to the secondary site. Each site has its own quorum volume. A two-way or four-way mirror is recommended for the quorum volume for redundancy.