DR Configuration Guides
Controlled Failover Option Results Summary
Home

Controlled Failover Option Results Summary

The following table indicates which failover steps are executed based on whether or not the Controlled failover option was selected when the SyncIQ Policy failover was initiated.

StepsDescriptionExecuted onSyncIQ Policy Controlled Failover selected Controlled Failover NOT selected
1 - Ensure that there is no live access to data

Check for open files.

If Open files found, decide whether to failover or wait to be closed.

SourceManualNot applicable - manual stepNot applicable - manual step
2 - Begin FailoverInitiate Failover from Eyeglass EyeglassManualNot applicable - manual stepNot applicable - manual step
3 - ValidationWait for other Eyeglass Failover jobs to completeEyeglassAutomated by EyeglassStep ExecutedStep Executed
4 - Synchronize dataRun all OneFS SyncIQ policy jobs related to the Access Zone being failed over SourceAutomated by EyeglassStep ExecutedStep NOT Executed
5 - Synchronize configuration (shares/export/alias)Run Eyeglass configuration replication 1 EyeglassAutomated by Eyeglass (configuration exists on source and target)Step Executed

Step Executed based on last known data in Eyeglass

*If you do not want this, uncheck the “Config Sync” option to skip this step

6 - Synchronize quota(s)Run Eyeglass Quota Jobs related to the SyncIQ Policy or Access Zone being failed overEyeglassAutomated by Eyeglass (deleted on source cluster and created on target cluster)Step ExecutedStep Executed based on last known data in Eyeglass
7 - Record schedule for SyncIQ policies being failed overGet schedule associated with the SyncIQ policies being failed over on OneFS SourceAutomated by EyeglassStep ExecutedStep NOT Executed
8 - Prevent SyncIQ policies being failed over from runningSet schedule on the SyncIQ policy(s)  to manual  on source clusterSourceAutomated by EyeglassStep ExecutedStep NOT Executed
9 - Provide write access to data on targetAllow writes to SyncIQ policy(s) related to failover2TargetAutomated by EyeglassStep ExecutedStep Executed
10 - Disable SyncIQ on source and make active on targetResync prep SyncIQ policy related to failover (Creates MirrorPolicy on target) from OneFSSourceAutomated by EyeglassStep ExecutedStep NOT Executed
11 - Set proper SyncIQ schedule on targetSet schedule on MirrorPolicy(Target) using schedule from step 6 from OneFS for policy(s) related to the FailoverTargetAutomated by EyeglassStep ExecutedStep NOT Executed
12 - Remove quotas on directories that are target of SyncIQ (PowerScale best practice)Delete all quotas on the source for all the policiesSourceAutomated by EyeglassStep ExecutedStep NOT Executed
13 - Change SmartConnect Zone on Source so not to resolve by ClientsRename SmartConnect Zones and Aliases (Source)SourceManualNot applicable - manual stepNot applicable - manual step
14 - Avoid SPN CollisionSync SPNs in all AD providers to current SmartConnect Zone names and aliases (Source)Source Manual (deletes smartconnect SPN from source cluster machine account)Not applicable - manual stepNot applicable - manual step
15 - Move SmartConnect Zone to TargetAdd source SmartConnect Zone(s) as  Aliase(s) on  (Target)TargetManualNot applicable - manual stepNot applicable - manual step
16 - Update SPN to allow for authentication against targetSync SPNs in all AD providers to current SmartConnect Zone names and aliases (Target)TargetManual (adds new SmatrConnect alias SPN’s to target cluster machine account)Not applicable - manual stepNot applicable - manual step
17 - Repoint DNS to the Target cluster IP addressUpdate DNS delegations for all SmartConnect Zones that are members of the Access ZoneDNSManualNot applicable - manual stepNot applicable - manual step
18 - Refresh session to pick up DNS changeRemount the SMB share(s)SMB Client MachinesManual on clientsNot applicable - manual stepNot applicable - manual step
  1. Initiates Eyeglass Configuration Replication task for all Eyeglass jobs
  2. SyncIQ does NOT modify the ACL (Access control settings on the file system).  It locks the file system.   ls -l   will be identically on both source and target



© Superna LLC