Dell PowerVault NX3600 - Manual (Page 47)

NOTE: FluidFS 1.1 supports auto generate target volume during addition of the replication policy. For FluidFS 1.0,
you must create the target volumes in cluster B and make sure that the volume size is big enough to accommodate
the corresponding source volume data in cluster A.
4. Start the replication scheduler to ensure that at least one successful replication has occurred for all the source
volumes in cluster A.
If the replication fails, fix the problems encountered and restart the replication process. This ensures that all
source volumes in cluster A have at least one successful replication copy in cluster B. Set up a regular replication
schedule, so the target volumes in cluster B always have most up to date replication copy for cluster A.
CAUTION: Replication restore is not a complete BMR restore, settings such as network configuration (client, SAN,
and IC) cannot be backed up and restored using the replication method. Note all cluster A settings (for use when
restoring cluster A) including network configuration, cluster wide settings such as volume name, alert settings, and
so on for future use. If the system restore operation fails to restore these settings, you can manually restore the
cluster A settings back to their original values.
Phase 2—Cluster A Fails And Client Requests Fail Over To Backup Cluster B
If source cluster A stops responding because of an unexpected failure (hardware, disk, and so on), you must:
1. Log on to backup cluster B.
2. Delete the existing replication policy for all replication target volumes.
FluidFS replication manager tries to contact source cluster A, which fails.
3. Confirm replication policy deletion on backup cluster B and apply the source volume configuration from cluster A.
Currently the following volume configurations can be restored:
– NFS exports
– CIFS shares
– Quota rules
– Snapshot schedule
– NAS volume alerting, security style and related parameters
– NAS volume name
– NAS volume size
This transforms target volumes (B1, B2, .. B n ) to standalone volumes. Repeat this procedure to bring all target
volumes in cluster B to standalone volumes with volume configuration applied from cluster A.
4. From the NAS Manager web interface, restore the NAS system configuration from cluster A.
For more information on restoring the NAS system configuration, see Restoring Cluster Configuration.
This restores cluster B configuration to cluster A settings. Currently the following cluster system configuration can
be restored:
– Protocols configuration
– Users and Groups
– User mappings
– Monitoring configuration
– Time configuration
– Antivirus hosts
5. Ensure that cluster B is used to temporarily serve client requests during the fail over time.
Administrators must perform the following steps to set up DNS and authentication:
a) Point the DNS names from customer DNS server to cluster B instead of cluster A.
47