Failover Recovery
Introduction
Failover Log Analysis
Replication Policy Failover Preparation
DFS Mode
Networking Operations
Replication Policy Failover
Replication Policy Failover Finalize
info
This step runs one child step per policy, listed as “Finalize quota for path <policy source path>”. The table below describes failures on those steps, and the following should be done for any failed steps, or steps that did not run.
| Step That Failed | Impact on Failover | Recovery Steps | Notes or Data Loss Impact |
|---|---|---|---|
| Finalize quota for path: Delete Quotas on Source | - Could not delete quotas from the source. - Policy is failed over. - Target cluster is now active. - Failover status: Failure. | 1. On the SOURCE OneFS, locate all quotas for data protected by the SyncIQ policy. 2. Verify these quotas exist on the TARGET cluster. 3. Delete these quotas from the SOURCE. | - This step isn’t required during uncontrolled failover. - No data loss impact: Policies can failover even without completing this step. - Note: Not completing this step may affect re-protecting due to leftover quotas on the source cluster. |
| Enable configuration replication for policies | - Unable to enable Eyeglass Configuration Replication Jobs. - Policy is failed over. - Target cluster is now active. - Failover status: Failure. | 1. Open the Eyeglass Jobs window. 2. Select the configuration replication job and enable it. 3. Use logs to find the reason for failure. | - This step activates the newly configured mirror policies after failover (if they weren’t already active). - No data loss impact: Eyeglass will detect and enable the new policy even after failure. - Note: If this step fails, configuration syncing from the source cluster may be blocked, but it can be enabled manually in the jobs window. |
Post Failover Script Execution
| Step That Failed | Impact on Failover | Recovery Steps | Warnings or Data Loss Impact |
|---|---|---|---|
| Eyeglass Script Engine | - A user-provided post-failover script failed. - Failover status: Failure. | 1. Use the script engine to correct errors in the failing scripts and re-run the scripts that failed. 2. Use the test script function to validate output and error codes returned to failover jobs. | - This step relies on user-supplied implementations. - Review the script output to ensure proper execution. - If the script fails, it should halt the failover job if set up correctly. - Data Loss Impact: This step mainly affects remounting or starting applications after failover. Logs should be reviewed to confirm all steps completed and correct any script failures manually if needed. |
note
See Pre Post Failover Scripting Guide on proper script exit code values to indicate failure vs successful execution.