Administrator Guide

Ensure that the DNS server on Cluster B is the same as the DNS server or in the same DNS farm as the DNS server of
Cluster A. Existing client connections might break and might need to be re-established. You must unmount and re-mount the
NFS exports on the clients.
b (Single NAS volume failovers) Manually update the DNS entry for the NAS volume that was failed over. This redirects clients
that are accessing this volume from Cluster A to Cluster B, while other clients keep accessing other volumes using the same
DNS name. Client systems might need to refresh their DNS cache.
c (Single NAS volume failovers) To force SMB and NFS clients to Cluster B, you must delete the SMB shares and NFS exports on
Cluster A. This forces the SMB and NFS clients to reconnect, at such time they are connected to Cluster B. After restoring the
source volume’s conguration on Cluster B, all of the SMB shares and NFS exports will be present on the target volume (on
Cluster B), so no SMB share/NFS export conguration information is lost.
The failed over volume can now be accessed using the exact same DNS name and SMB share/NFS export name as it was when
hosted on Cluster A, except now it is hosted on Cluster B.
d Join Cluster B to the AD server or LDAP/NIS.
Ensure that the AD server and LDAP server are in the same AD/LDAP farm or same server.
Phase 3—Restore Cluster A and fail back from Cluster B to Cluster A
After you have xed the reason that caused Cluster A to fail, fail back over to Cluster A.
1 Fix the reason that caused Cluster A to fail and if required reinstall FluidFS.
2 Rebuild the FluidFS cluster:
• IP address-based failovers: Use the settings for Cluster A that you recorded earlier, but change the IP addresses for Cluster A to
match the IP addresses originally used by Cluster B.
• DNS-based failovers: Use the settings for Cluster A that you recorded earlier.
3 From Cluster B, set up a replication partnership between Cluster B and Cluster A.
4 Congure replication for all the promoted recovery volumes in Cluster B, and specify that they replicate back to the original source
volumes in Cluster A.
The replication policy must be a one-to-one match on a volume basis, for example:
Source volume B1 (Cluster B) to target volume A1 (Cluster A)
Source volume B2 (Cluster B) to target volume A2 (Cluster A)
Source volume Bn (Cluster B) to target volume An (Cluster A)
5 Manually perform replication on the promoted recovery volumes in Cluster B (B1, B2, .., Bn). Proceed to the next step when replication
completes.
If the replication fails, x the problems encountered and restart the replication process. Ensure that all the NAS volumes are
successfully replicated to Cluster A.
6 From Cluster A, promote the original source volumes (A1, A2, .., An).
7 From Cluster B, delete replication for the promoted recovery volumes (B1, B2, .., Bn) and apply the source volume conguration from
Cluster B to Cluster A. Repeat this procedure to delete all the replication policies and bring all target volumes in Cluster A to standalone
NAS volumes.
8 From Cluster A, restore the users and groups conguration from Cluster B. This restores the Cluster A users and groups conguration
to Cluster B settings.
NOTE
: If the system conguration restore fails, manually set the system back to the original settings (use the settings for
Cluster A that you recorded earlier).
9 Start using Cluster A to serve client requests.
a Choose one of the following options:
• IP address-based failovers: Change the IP addresses for Cluster A to match the IP addresses originally used by Cluster A and
change the IP addresses for Cluster B to match the IP addresses originally used by Cluster B. Existing client connections
might break and might need to be re-established.
• DNS-based failovers: Point the DNS names from your DNS server to Cluster A instead of Cluster B.
FluidFS Administration
471