DR Configuration Guides
Operational Steps for Eyeglass Microsoft DFS Mode Failover

Operational Steps for Eyeglass Microsoft DFS Mode Failover


The Eyeglass Microsoft DFS Mode Failover solution for PowerScale OneFS fully automates execution of these steps:

  1. Performs SyncIQ Failover to Secondary Cluster and sync’s outstanding data.
  2. Creates and Renames ALL SMB Shares protected by the SyncIQ policy to the  Secondary Cluster.
  3. Deletes or Renames ALL SMB shares on the source cluster to ensure DFS clients can not mount the cluster See DFS Feature changes table (DFS Feature Changes and Share names used on DFS synced Shares   ) for version behaviour. 
  4. Creates ALL quotas on the target cluster protected by the SyncIQ policy.
  5. Deletes ALL quotas on the source cluster to ensure failback and SyncIQ operations from Secondary cluster to primary.
  6. Copies SyncIQ schedule to Secondary cluster.
  7. Runs Sync Prep on Source cluster to become the target of SyncIQ policy replication.

Procedure for Running Eyeglass Microsoft DFS Mode Failover

IMPORTANT: Making any changes to the SyncIQ Policies or related Eyeglass Configuration Replication Jobs being failed over during the failover may result in unexpected results.

IMPORTANT: Eyeglass Assisted Failover has a 1 hour timeout on each failover step.  Any step which is not completed within this timeout period will cause the failover to fail.

IMPORTANT: Deleting configuration data (shares, exports, quotas) or modifying Share name or NFS Alias name or NFS Export path on the target cluster before failing over without running Eyeglass Configuration Replication will incorrectly result in the object being deleted on the source cluster after failover.  You must run Eyeglass configuration replication before the failover OR select the Config Sync checkbox on failover to prevent this from happening.

For detailed steps consult the failover guide table here.

For detailed steps on execution and monitoring consult the How to Monitor the Eyeglass Assisted Failover

NOTE: On completion of the failover the DFS clients will no longer have a share on the primary cluster and will use the referral list to select a new mount which will be an active share on the target cluster.

© Superna Inc