Administrator Guide

8. From Cluster A, restore the users and groups configuration from Cluster B. This restores the Cluster A users and groups configuration
to Cluster B settings.
NOTE: If the system configuration 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.
Ensure that the DNS server on Cluster A is the same as the DNS server or in the same DNS farm as the DNS server of Cluster
B. Existing client connections might break and might need to be re-established. You must unmount and re-mount the NFS
Exports on the client.
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 B to Cluster A, 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 A, you must delete the SMB shares and NFS exports on
Cluster B. This forces the SMB and NFS clients to reconnect, at such time they are connected to Cluster A. After restoring the
source volume’s configuration on Cluster A, all of the SMB shares and NFS exports will be present on the target volume (on
Cluster A), so no SMB share/NFS export configuration 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 B, except now it is hosted on Cluster A.
d) Join Cluster A to the AD server or LDAP/NIS.
e) From Cluster A, configure replication between the original source volumes (A1, A2,.. , An) and the original target volumes (B1, B2,.. ,
Bn) to prepare for the next disaster recovery.
File Access Notification
File access notification occurs when both systemwide file access auditing configuration is enabled and file operation matches any active
(enabled) preconfigured file access notification policy for the volume. Auditing events are generated after permissions check for the file
operation and before the actual execution of the operation.
About this task
NOTE:
Third-party software is required to provide auditing capabilities. The following third-party software applications
are supported:
Varonis DataAdvantage
Dell Quest ChangeAuditor
See the FluidFS Support Matrix for the latest supported third-party software applications.
Steps
1. From the Storage view, select a FluidFS cluster.
2. Click the File System tab.
3. In the File System view, select Cluster Connectivity.
4. In the Cluster Connectivity panel, click the External Servers tab.
5. Under External Audit, click Edit Settings.
The External Audit Settings dialog box opens.
6. Select the External Audit checkbox.
7. Provide the information for the Subscriber Name and Auditing Server Hosts fields.
8. Click OK.
434
FluidFS Administration