Advanced Failover Modes
Cached Configuration Advanced Mode​
In some situations, pre-syncing configuration data from one cluster to the DR (Disaster Recovery) site may not be possible due to security concerns. Cached Configuration Advanced Mode ensures that all configuration data is stored locally on the Eyeglass appliance instead of being pre-synced to the DR cluster.
Eyeglass maintains a database of configuration changes, but this is not used for failover operations, as it could contain stale information. Starting from version 1.6, the Cached Configuration Advanced Mode enables Eyeglass to use locally cached configuration data for both controlled and uncontrolled failovers.
How Cached Configuration Advanced Mode Works​
-
Automatic Sync Every 5 Minutes
Eyeglass retrieves configuration changes every 5 minutes and updates local files on the appliance.
-
Failover Uses Cached Data Only
During failover (both controlled and uncontrolled), Eyeglass uses only the cached files. It does not communicate with the source cluster to create shares, exports, or quotas on the target DR cluster.
-
Potential Stale Data for Controlled Failover
In controlled failovers, cached data might be slightly outdated. However, it is used to ensure the failover process operates securely and efficiently.
How to Enable Cached Configuration Advanced Mode​
-
SSH into the Eyeglass appliance as an admin user.
-
Run the following command:
igls adv failoverSettings set --readfromfile=true -
Configuration is complete.