Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.
Version: 2.15.0

IP Pool Failover Configuration Prerequisites

Introduction​

IP Pool Failover offers enhanced flexibility for managing failover processes in active/active data configurations within an Access Zone across two clusters. This feature supports failover logic for DFS, SMB, and NFS data and builds upon the requirements for Access Zone failover, adding specific steps to align SyncIQ policies with SmartConnect names (IP pools). This document outlines the essential requirements and configurations needed to ensure a successful IP Pool Failover using Eyeglass.

IP Pool Failover Requirements​

To effectively implement IP Pool Failover, the following conditions must be met:

Cluster Configuration​

Each Access Zone involved in the failover must have an equal number of IP pools on both the source and target clusters. Mismatched IP pool counts between clusters are not supported. For example, if the source cluster has two pools, the target cluster must also have two pools.

Pool Configuration​

All IP pools within an Access Zone must be configured for failover. Partial pool failover within an Access Zone is not supported. When Pool Failover is configured for an Access Zone, that Access Zone will only appear in the Pool Readiness section of the DR Dashboard. It will not be displayed in the Zone Readiness section, and the associated SyncIQ policies will only be shown in the Pool Readiness view, not in the Policy Readiness or DFS Readiness views.

Unsupported Configurations​

  • Pool Failover is not supported for multi-site configurations, such as A -> B and A -> C scenarios.
  • Replication topologies where shares or NFS aliases have the same name on both clusters but are protected by different SyncIQ policies are not supported for any failover type, including IP Pool Failover. Configuration replication overwrites the share/alias path on one cluster, and failover then attempts to apply two SyncIQ policies with identical source paths, resulting in failure. This is an invalid DR configuration that will cause failover to be unsuccessful, with or without Superna Eyeglass.

Failover Type Restrictions​

Once an Access Zone is configured for IP Pool Failover, it must be managed in SmartConnect/IP Pool failover type from the Failover Wizard. The Access Zone will not be available for failover in Access Zone type, nor will the associated SyncIQ policies be available for failover in SyncIQ Policy or Microsoft DFS types.

Runbook Robot Compatibility​

The Basic Runbook Robot is not supported for Pool Failover in System Access Zones due to the lack of support for pool to SyncIQ Policy mapping. Advanced DR Robot configuration is required for managing Access Zone failover.

Eyeglass Version​

IP Pool Failover is available in Eyeglass release 2.0 and later.

SyncIQ Policy Mapping​

SyncIQ policies must be mapped to IP pools, ensuring that all SmartConnect names assigned to the pool failover alongside the SyncIQ policies. Multiple policies can be mapped to a single pool in Eyeglass. This may require adjustments to your existing policy design to accommodate pool-based failover.

Recommendations for Eyeglass Assisted IP Pool Failover​

To ensure a smooth and successful IP Pool Failover process, consider the following recommendations:

  • Verify that all IP pools within the Access Zone are properly configured and consistent across both clusters before initiating the failover.
  • Review and, if necessary, adjust your SyncIQ policy design to ensure it aligns with the requirements for pool-based failover.
  • Ensure that SmartConnect names are appropriately assigned and configured to support seamless data access during and after the failover process.

Next Steps​

For detailed procedures on configuring and executing IP Pool Failover, refer to the IP Pool Failover Configuration Procedures.