[-]
  
  
  
  
  
  
  
  
  
  
  
  
[+]
[+]
[+]
 
Updated on 7/29/2019
Operations Guides
Replication Policy Failover Preparation (Data Sync and Config Sync)
Direct link to topic in this publication:
Home

Replication Policy Failover Preparation (Data Sync and Config Sync)

Failure to Complete StepDescription of Impact to FailoverRecovery StepsSpecial Instructions or Warnings
Wait for other failover jobs to complete

Eyeglass only runs one failover job at a time.

Failover has not started.

  1. Wait until no Failover jobs are present in the running jobs window.  
  2. Restart failover
This step will wait for up to two hours in the running state before timing out. 
SOURCE get POLICY info

Eyeglass cannot communicate with source cluster.

Failover fails.

  1. Validate connectivity between Eyeglass and the source cluster.
  2. Restart failover

This step is not run during uncontrolled failover.

Data Loss Impact - Failover cannot proceed, data loss scenario until resolved.

Wait for existing policy jobs to complete. Failover fails if this step times out. Default timeout failover timeout  in the current release is 180 minutes, this can be increased with igls cli command see Admin Guide to increase timeout for each step in failover. Also see Best Practices for Failover with Eyeglass.  
  1. Validate no other failover jobs are running on eyeglass.
  2. Restart failover.
  3. NOTE: SyncIQ policies that return error from the cluster will require EMC support case to be opened to resolve policies that will not start or run resync prep or execute make writeable operations

The timeout on this step read from the failover timeout value in minutes.

Data Loss Impact - Failover cannot proceed, data loss scenario until resolved.

SOURCE remove schedule POLICY

Eyeglass cannot communicate with source cluster.

Failover fails.

  1. Validate connectivity between Eyeglass and the source cluster.
  2. Restart failover.

This step is not run during uncontrolled failover.

Data Loss Impact - Failover cannot proceed, data loss scenario until resolved.

Replication Policy Failover run all policies

(SyncIQ Data Sync option enabled on failover job and multiple policies failed over)

Final incremental sync of data on the filesystem has failed.

Failover Aborted.

Source and targets still in initial state meaning target cluster is read-only still

  1. Use the Eyeglass Job Details tree to determine which policies ran successfully, and which failed.
  2. Open OneFS on the source to determine the reason for policy failure(s).
  1. If policy job is still running, wait for it to complete, or cancel the job in OneFS.
  2. Manually run the policy, and see if it can be completed.
  1. Open Case with EMC for SyncIQ jobs failing to run.
  2. Restart Failover.

Eyeglass waits for up to failover over timeout value in minutes for each policy to run.  It will abort with a timeout if the incremental sync takes longer than an hour.  Wait for this job to finish, then restart the failover job to try again.

If the unsynced data on the source filesystem is unimportant and it's more important to get the target cluster file system writable, the Failover can be restarted with the “Data Sync” box unchecked.  This will skip the final incremental sync, and will result in data loss for any data not previously replicated with SyncIQ.

NOTE: This step is not run during uncontrolled failover. 

Run Configuration Replication now.

(Config Sync enabled in failover job)

 Final sync of configuration shares/exports/aliases has failed.

Failover wil continue.

Source and targets still in initial state meaning target cluster is read-only still

  1. Open the Eyeglass Jobs window, and switch to the running jobs tab.
  2. Select the most recent configuration replication job.
  3. Use the Job Details to determine the reason for failure.
  4. Address the config replication failure OR make note of the unsynced configuration data
  5. Restart failover.

If the configuration on source and target are known to be identical, the Config Sync option can be unchecked when restarting failover to skip this step.

If the unsynced configuration on the source is unimportant and it's more important to get the target cluster file system writable, the Failover can be restarted with the “Config Sync” box unchecked.  This will skip this step.

Note This step is not run during uncontrolled failover.   

                               

Copyright Superna LLC