Dell FluidFS NAS Solutions Administrator's Guide

• When deleting the replication policy from the destination cluster B — FluidFS replication manager tries to contact source cluster A, which fails. The volume on destination cluster B must have its configuration restored using Cluster Management > Restore NAS Volume Configuration.
• When deleting the replication policy from the source cluster A — You are given an option to apply the source volumes configuration to the destination volume. If you do not remember to select this, or it fails, the configuration of the source volume from cluster A can be restored onto the destination volume on cluster B using Cluster Management > Restore NAS Volume Configuration.

• NFS exports
• CIFS shares
• Quota rules
• Snapshot schedule
• NAS volume alerting, security style and related parameters
• NAS volume name
• NAS volume size

For more information on restoring the NAS system configuration, see Restoring Cluster Configuration .

• Protocols configuration
• Users and Groups
• User mappings
• Monitoring configuration
• Time configuration
• Antivirus hosts

1. Point the DNS names from customer DNS server to cluster B instead of cluster A. 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 may break and may need to be re-established. You must unmount and remount the NFS Exports on the client.
   • NOTE: Complete steps b, c, and d only for single volume failovers.
2. On DNS, manually update the DNS entry for the NAS volume that was failed over. This step is to repoint end users that are accessing this volume from cluster A to cluster B, while the end users keep accessing it using the same DNS name.
   • NOTE: Client systems may need to refresh DNS cache.
3. To force CIFS and NFS clients to cluster B, we also must delete the CIFS shares and NFS exports on cluster A. This forces the CIFS and NFS clients to reconnect, at such time they are connected to cluster B. After restoring the source volume’s configuration on cluster B, all of the shares and exports will be present on the destination volume (on cluster B), so no share/export configuration information is lost.
4. The failed over volume now can be accessed using the exact same DNS name and share name as it was when hosted on cluster A, except now it is hosted on cluster B.
   • NOTE: NFS mounts must be un-mounted and mounted again. Active CIFS transfers fail during this process, but if CIFS shares are mapped as local drives, they automatically reconnect once the replication is deleted, DNS is updated, and NFS/CIFS shares are deleted on cluster A.
5. Join AD server or LDAP/NIS. Ensure that the AD and LDAP are in the same AD/LDAP farm or same server.