[-]
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 [+]
  
  
  
  
  
  
 [+]
  
  
  
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
Updated on 5/17/2019
Administration Guides
Failover Readiness
Direct link to topic in this publication:
Home

Failover Readiness

    Monitor DR Readiness

    To view and manage your DR readiness, use the DR Dashboard window:

    Policy Readiness: Provides a view of your readiness for SyncIQ Policy Failover.

    Zone Readiness: Provides a view of your Access Zone Failover Readiness.

    DFS Readiness: Provides a view of your readiness for a SyncIQ Policy DFS Mode Failover.

    Policy Readiness and DFS Readiness

    The DR Failover Status on the Policy or DFS Readiness tabs provides you with a quick and easy way to assess your Disaster Recovery status for a SyncIQ Policy Failover (non-DFS mode) or SyncIQ Policy Failover (DFS mode).  

    Each row contains the following summary information:

    ColumnDescriptionNotes
    NameName of the Eyeglass configuration Replication Job

    Eyeglass configuration replication Job created automatically for each SyncIQ Policy detected with exactly the same name + prefixed with Isilon Cluster name.

    Quota Jobs are suffixed with “quotas”.

    SyncIQ PolicyName of the SyncIQ Policy associated with the Eyeglass Job 
    SourceThe Isilon cluster that is the source configured in the SyncIQ PolicyEyeglass Job will have same source
    DestinationThe Isilon cluster that is the target configured in the SyncIQ PolicyEyeglass Job will have same target
    DR Failover StatusA status calculated by Eyeglass based on the failover validation criteria for the Policy or DFS Failover mode

    This column displays the overall status.  Select the link to see individual status for each validation criteria.

    New option shows “Failed Over” for any policy that is read-only status in SyncIQ.

    Click on the DR Failover Status link to see the details for each of the failover validation criteria for a selected Job.

    The DR Failover Status will be one of the following:

    StatusFailover Impact
    OKAble to Failover
    WARNING

    Warning state does NOT block failover.

    IMPORTANT: While failover is not blocked, the issue(s) causing this Warning may cause the failover to fail.  Recommendation is to understand and resolve these issues prior to failover.

    ERRORError state BLOCKS failover.
    DISABLEDDisabled state DOES block failover.
    FAILED OVERFailed Over state DOES block failover.

    The DR Failover Status is based on Status for each of the following areas for Policy and DFS Failover:

    OneFS SyncIQ ReadinessHave the SyncIQ policies in the Access Zone been successfully run and are they in a supported configuration?
    Eyeglass Configuration Replication ReadinessHave the Eyeglass Configuration Replication jobs in the Access Zone been successfully run to sync configuration data for all policies that are members of the Access Zone?
    Zone Configuration Replication ReadinessHas the Eyeglass Zone Configuration Replication job been successfully run to create target cluster Access Zones that don't already exist for configuration sync complete?
    Date-Time ValidationAre the date-time differences between nodes and between Eyeglass and the clusters within an acceptable range that will not affect SyncIQ operations?

    Additional information for Policy / DFS Readiness criteria is provided in the following sections.

    Policy/DFS Readiness - OneFS SyncIQ Readiness

    The OneFS SyncIQ Readiness criteria is used to validate that the SyncIQ policy has been successfully run and that it is in a supported configuration.   For each SyncIQ Policy the following checks are done:  





    New Validations in Release 2.0 and later

    SyncIQ Policy:Notes:

    Previous Failed DFS faiover share prefix

    This detects any prefexed dfs shares on the active cluster.  The active cluster should not have any prefexed share on the SyncIQ policy.  This validation will indicate if prefixed shares are detected that should be cleaned up prior to any failover.

    Policy Source Nodes Restriction

    Validate Isilon best practices that recommend that SyncIQ Policies utilize the Restrict Source Nodes option to control which nodes replicate between clusters.

    SyncIQ Policy Status Validations

    DR Status is “OK” when all of the conditions below are met:

    • Your SyncIQ Policy is enabled.
    • Your SyncIQ Policy last state was finished or needs attention.

    DR Status is “Warning” when the condition below is met:

    • SyncIQ Policy has a last state that was not successful.
    • SyncIQ Policy has a last state that was paused or cancelled.
    • SyncIQ Policy does not not have a last state (has never been run).
    • SyncIQ Policy has Excluded Directories and/or Included Directories configured.

    IMPORTANT: SyncIQ Policy in Warning state MAY NOT be able to be run by Eyeglass assisted failover depending on it’s current status.  If not run, you will incur data loss during failover.  

    • Example 1: SyncIQ Policy has an error state.  If it cannot be run from the OneFS, it will also not be able to run from Eyeglass.  
    • Example 2: SyncIQ Policy is paused.  Eyeglass failover cannot RESUME a paused SyncIQ Policy - this must be resumed from OneFS

    You must investigate these errors and understand their impact to your failover solution.

    DR Status is “Disabled” when either of the conditions below are met:

    • Eyeglass configuration replication Job is user disabled.
    • Or the SyncIQ policy in OneFs is disabled.

    Quota Domain Validation

    Detects a quota with needs scanning flag set.  This flag will fail SyncIQ steps (run policy, Make Writeable, and Resync prep) for any policy with a quota that has not been scanned and is missing a quota domain.  Failover should not be started with this validation warning.  Quota scan job should be run manually or verify if a quota scan job is in progress.

    SyncIQ File Pattern Validation

    SyncIQ policies with file patterns set cannot be failed back and any files that do not match the file pattern will be read-only after failover.  This file pattern is not failed over by Resync prep to mirror policies and Eyeglass does not support copying file access patterns to mirror policies.

    This setting should not be used for DR purposes. This validation will show warning for any policy with a file pattern set.  The file pattern should be removed from the policy to clear the warning.

    Corrupt Failover Snapshots

    Validate that Target Cluster does not have an existing SIQ-<policyID>-restore-new or SIQ-<policyID>-restore-latest snapshot from previous failovers/synciq jobs for the Policy.

    Policy Local Target Validation :

    • Duplicate SyncIQ Local Targets

    Validate that there is only 1 Local Target per SyncIQ policy.

    Policy Local Target Validation:

    • Target Writes Disabled

    Validate that the target folder of SyncIQ policy has writes disabled.
    Policy EnablingValidate that the SyncIQ Policy is enabled in OneFS.

    Policy/DFS Readiness - Eyeglass Configuration Replication Readiness

    The Eyeglass Configuration Replication Readiness criteria is used to validate that the Eyeglass Configuration Replication job related to the SyncIQ Policy has been successfully run to sync the related configuration data.  For the Eyeglass Configuration Replication Job the following check is done:

    <Eyeglass Configuration Replication Job Name>

    Validate that the Eyeglass Configuration Replication Job status is not in error state.

    DR Status is “OK” when:

    • Your Eyeglass configuration replication Job is enabled.
    • Your Eyeglass configuration replication Job Last Run and Last Success timestamp are identical.
    • Your Eyeglass configuration replication Job Audit Status is OK.

    DR Status is “Warning” when either of conditions below are met:

    • Eyeglass configuration replication Job is new and has not been run yet.
    • Eyeglass configuration replication Job has been successfully executed but not audited.
    • Eyeglass configuration replication Job Last Run was not successful.
    • Eyeglass configuration replication Job Audit was not successful.

    DR Status is “Disabled” when either of the conditions below are met:

    • Eyeglass configuration replication Job is user disabled
    • OR the SyncIQ policy in OneFs is disabled

    Policy / DFS Readiness - Zone Configuration Replication Readiness

    The Zone Configuration Replication Readiness criteria is used to validate that the Zone Configuration Replication job, related to the SyncIQ Policy, has successfully run, in order to create a new target cluster Access Zone  for configuration sync completion.  

    Policy/DFS Readiness - Date-Time Validation

    The Date-Time Validation is used to validate that the time difference between the cluster nodes, and between clusters and Eyeglass, are within an acceptable range that will not affect SyncIQ operations.  SyncIQ commands, like re-sync prep, can fail if the time between cluster nodes is greater than the time between the Eyeglass VM and the cluster with regards to latency of issuing the API call (a scenario where a node returns a timestamp for a step status message is earlier than the beginning of the Re-sync prep request).  API calls can return different completion times between clusters.  Differences here can cause resync prep failover commands to fail, if the difference between Eyeglass and the source cluster is greater than the time it takes for a resync prep command to complete.

    NOTE: This condition under which timing differences cause resync failover commands to fail is rare and hard to detect manually.  In release 1.8 Eyeglass can detect this condition.  It's best practise to use NTP on clusters and the Eyeglass appliance.  This allows failover logs and the new feature in release 1.8 or later to collect cluster SyncIQ reports for each step and append to the failover log. This will make debugging multi step multi cluster failover simpler.  This process will require time to be synced.

    For each Cluster the following checks are done:  

    Date-Time ValidationNotes:
    Nodes ValidationValidation that the maximum time difference between the nodes of a cluster is less than the time required for the cluster node time request made by Eyeglass to complete.
    Eyeglass & Clusters Validation

    NOTE: Only applicable if Nodes Validation is OK. Validation that the earliest node time for a cluster and the Eyeglass appliance time are less than the time required for the cluster node time request made by Eyeglass to complete plus a default additional skew factor (default 1s).

    Executed if Nodes Validation is OK.

    DR Dashboard Job Details

    Each Policy or DFS Job can be expanded in the DR Dashboard Policy Readiness or DFS Readiness view to see Job Details:

    DR Dashboard Configuration Replication Job Details

    ColumnDescriptionNotes
    SyncIQ PolicyAll information in the SyncIQ Policy details section comes from the Isilon Cluster itself.If this section is empty then the Job is a custom Eyeglass job not associated with a SyncIQ policy.
    Job NameName of the SyncIQ Policy.Same name on the Isilon cluster.
    Last StartedDate/time when the last SyncIQ Policy job was started.Information retrieved from SyncIQ Policy details on the Isilon Cluster.
    Last SuccessDate/time when SyncIQ Policy last ran successfully on the Isilon.Information retrieved from SyncIQ Policy details on the Isilon Cluster. 
    Last Job StateStatus for Last SyncIQ Policy Job.Information retrieved from SyncIQ Policy details on the Isilon Cluster used to determine Overall DR Status.
    EnabledIndicates whether the Isilon SyncIQ policy is enabled. 
    Eyeglass Configuration ReplicationAll information in the Eyeglass Configuration Replication details section comes from Eyeglass. 
    Job NameName of the Eyeglass Configuration Replication Job.

    Eyeglass Configuration Replication Job created automatically for each SyncIQ Policy detected with exactly the same name and prefixed with Isilon Cluster name.

    Quota Jobs also suffixed with “quotas”.

    Last RunDate/time when the last Eyeglass Configuration Replication Job was started.Information used to determine Overall DR Status.
    Last SuccessDate/time when Eyeglass Configuration Replication Job was last run successfully.Information used to determine Overall DR Status.
    Audit StatusIndicates status of the Eyeglass Configuration Replication Job Audit.  After the Eyeglass Configuration Replication Job has completed, Eyeglass performs an audit to compare source and destination configuration and ensures that replicated configurations are identical.
    EnabledIndicates whether the Eyeglass Configuration Replication Job is enabled. 
    Last Successful Readiness CheckDate/time when Eyeglass last successfully ran the Readiness Check Job. 

    Zone Readiness

    The Zone Readiness DR Failover Status provides you with a quick and easy way to assess your DR Status for an Access Zone Failover.   The Zone Readiness check is performed for both directions of a replicating Isilon cluster pair to ensure that you have your status not only for failover but also for failback.  

    The Zone Readiness Status will be one of the following:

    StatusDescription
    OKAll Required and Recommended conditions that are validated by Eyeglass software have been met.
    WARNING

    One or more Recommended conditions that are validated by Eyeglass software have not been met.

    Warning state does NOT block failover.

    Review the Access Zone Failover Guide Recommendations to determine impact for recommendations that have not been met.

    ERROR

    One or more of the Required conditions that are validated by Eyeglass software have not been met.

    Error state DOES block failover.

    Review the Access Zone Failover Guide Requirements for failover to determine resolution for these error conditions.

    FAILED OVER

    This Access Zone on this cluster has been failed over.

    You will be blocked from initiating failover for this Access Zone on this Cluster.

    IMPORTANT:  Not all conditions are validated by Eyeglass software.  Please refer to the Eyeglass Access Zone Failover Guide for complete list of requirements and recommendations.

    Notes:

    1. For the case where the Target cluster pool that has the Eyeglass hint mapping for failover does not have a SmartConnect Zone defined:
    1. On Failover the Access Zone will be in Warning state due to SPN inconsistencies.
    2. On Failback it will not have the FAILED OVER status displayed.
    1. For the case where there is no Eyeglass Configuration Replication Job enabled in an Access Zone there will be no entry in the Zone Readiness table for that Access Zone.

    The DR Failover Status is based on Status for each of the following areas for Access Zone Failover:

    OneFS SyncIQ ReadinessHave the SyncIQ policies in the Access Zone been successfully run and are they in a supported configuration.
    Eyeglass Configuration Replication ReadinessHave the Eyeglass Configuration Replication jobs in the Access Zone been successfully run to sync configuration data for all policies that are members of the Access Zone.
    SPN ReadinessIs Active Directory delegation completed for cluster machine accounts  to detect missing  SPNs and remediate existing and newly created SmartConnect Zones as short and long SPN’s created for cluster Active Directory machine accounts.
    SmartConnect Zone Failover Mapping ReadinessValidation that confirms if all IP pools in the Access Zone have an Eyeglass  hint (SmartConnect alias using igls syntax).  Each SmartConnect Zone name associated to the IP pools (and any SmartConnect aliases) must be mapped to a target cluster IP pool prior to any failover.  This ensures all SmartConnect names used to access source cluster data will failover to a target cluster IP pool.  It is best practice and requirement to create IP pools in matched pairs on source and destination cluster.
    SmartConnect/IP Pool ReadinessSmartConnect/IP Pool Failover Readiness provides the status of whether the IP pool is ready for the failover or, has been already failed over.   It also verifies each IP pool has a SmartConnect name applied.  This validation will be used for IP pool based failover in addition to Access Zone failover where all pools must have a SmartConnect name defined.
    Zone Configuration Replication ReadinessHas the Eyeglass Zone Configuration Replication job been successfully run to create target cluster Access Zones that don't already exist for configuration sync complete.
    Target Cluster ReachabilityIs Eyeglass able to connect to the Failover Target Cluster using API
    Date-Time ValidationAre the date-time differences between nodes and between Eyeglass and the clusters, within an acceptable range that will not affect SyncIQ operations.
    Zone Path ValidationZone Path Validation provides the status of whether Access Zones have colliding paths. Status of OK indicates that the Access Zone paths have no conflicts. Status of ERROR indicates that this Access Zone collides with another Access Zone's path.
    FQDN Alias ValidationIf a cluster was added to Eyeglass with FQDN SmartConnect name for management, this SmartConnect zone must have an igls-ignore hint applied to avoid a failover impacting Eyeglass access. An ERROR means no igls-hint was found on the IP pool for the SmartConnect zone used for cluster management. OK means igls-ignore hint was found.

    IMPORTANT

    By default the Failover Readiness job which populates this information is disabled.  Instructions to enable this Job can be found in the Eyeglass Isilon Edition Administration Guide.  

    Note: If there are no Eyeglass Configuration Replication Jobs enabled there is no Failover Readiness Job.

    Preparation and planning instructions for Zone Readiness can be found in the Access Zone Failover Guide:

    Requirements for Eyeglass Assisted Access Zone Failover

    Unsupported Data Replication Topology

    Recommended for Eyeglass Assisted Access Zone Failover

    Preparing your Clusters for Eyeglass Assisted Access Zone Failover

    Additional information for Zone Readiness criteria is provided in the following sections.

    Zone Readiness - OneFS SyncIQ Readiness

    The OneFS SyncIQ Readiness criteria is used to validate that the SyncIQ policies in the Access Zone has been successfully run and that they are in a supported configuration.   You will find one entry per SyncIQ Policy in the Access Zone.  For each SyncIQ Policy the following checks are performed:  



    New Validations in Release 2.0 and later

    SyncIQ Policy CheckNotes:
    Policy Hot/Hot ValidationFor Hot-Hot (Active-Active data) replication topology, validate that there is a dedicated Access Zone for each replication direction.

    Policy Zone Path Check

    • Policy Source Path Check
    • Policy Target Path Check
    Validate that the SyncIQ Policy(s) source root and target directories are at or below the Access Zone Base Directory.
    Policy Source Nodes RestrictionValidate Isilon best practices that recommend that SyncIQ Policies utilize the Restrict Source Nodes option to control which nodes replicate between clusters.
    Policy Hostname ValidationValidate the the SyncIQ Policy target host hostname is associated with a subnet pool that is NOT going to be failed over.
    Corrupt Failover SnapshotsValidate that Target Cluster does not have an existing SIQ-<policyID>-restore-new or SIQ-<policyID>-restore-latest snapshot from previous failovers/synciq jobs for the Policy.
    System Zone Config RestrictionValidate that all shares, exports and alias have been created in the Access Zone that is being failed over.  It is not supported to have shares, exports and alias with a path that is outside (higher in the file system) than the Access Zone base path.
    Policy EnablingValidate that the SyncIQ Policy is enabled in OneFS.
    Quota Domain ValidationDetects a quota with needs scanning flag set.  This flag will fail SyncIQ steps (run policy, Make Writeable, and Resync prep) for any policy with a quota that has not been scanned and is missing a quota domain.  Failover should not be started with this validation warning.  Quota scan job should be run manually or verify if a quota scan job is in progress.
    SyncIQ File Pattern Validation

    SyncIQ policies with file patterns set cannot be failed back and any files that do not match the file pattern will be read-only after failover.  This file pattern is not failed over by Resync prep to mirror policies and Eyeglass does not support copying file access patterns to mirror policies.

    This setting should not be used for DR purposes. This validation will show warning for any policy with a file pattern set.  The file pattern should be removed from the policy to clear the warning.

    Policy StatusValidate that the SyncIQ Policy is not in error state in OneFS.

    Policy Local Target Validation :

    • Duplicate SyncIQ Local Targets
    Validate that there is only 1 Local Target per SyncIQ policy.
    • Policy Local Target Validation:
    • Target Writes Disabled
    Validate that the target folder of SyncIQ policy has writes disabled.

    Zone Readiness - Eyeglass Configuration Replication Readiness

    The Eyeglass Configuration Replication Readiness criteria is used to validate that the Eyeglass Configuration Replication jobs in the Access Zone have been successfully run, to sync configuration data for all policies members of the Access Zone.  For each Eyeglass Configuration Replication Job in the Access Zone, the following check is performed:

    <Eyeglass Configuration Replication Job Name>Validate that the Eyeglass Configuration Replication Job status is not in the ERROR state.

    Note: With both enabled and disabled Eyeglass Configuration Jobs in the Access Zone, the Eyeglass Configuration Replication Readiness validation will only display status for the Enabled jobs.

    Zone Readiness - SPN Readiness

    The SPN Readiness criteria is used to:

    1. Validate that the Active Directory delegation is completed for cluster machine accounts.  
    2. Detect missing  SPNs .
    3. Remediate existing and newly created SmartConnect Zones as short and long SPN’s created for each  cluster Active Directory machine account.  

    This check is done for each domain for which each cluster is a member.

    Note: For the case where the Isilon Cluster is not joined to Active Directory, the SPN Readiness will show the following:

    • For OneFS 7.2 the SPN Readiness check is displayed with message “Cannot determine SPNs”.
    • For OneFS 8 the SPN Readiness check is not displayed in the Zone Readiness window.

    Zone Readiness - SmartConnect Zone Failover Mapping Readiness

    The SmartConnect Zone Failover Mapping Readiness criteria is used to validate that the SmartConnect Zone alias hints have been created between source and target cluster subnet IP pools.  This check is done for each subnet:pool in the Access Zone.

    For details on configuring the Smartconnect Zone Failover Mapping Hints, please refer to the Eyeglass Access Zone Failover Guide.

    Use the Zone Readiness View Mapping feature to display pools in the Access Zone and how they have been mapped using the SmartConnect Zone Alias hints.

    Zone Readiness - View Mapping

    Use the Zone Readiness View Mapping link to display the subnet:pool mappings with configured hints for the Access Zone.

    Zone Readiness - Zone Configuration Replication Readiness

    The Zone Configuration Replication Readiness criteria is used to validate that the Zone Configuration Replication jobs in the Access Zone have been successfully run to create target cluster Access Zones that don't already exist for configuration sync complete.  

    Zone Readiness - Target Cluster Reachability

    The Target Cluster Reachability criteria is used to validate that Eyeglass is able to connect to the Failover Target Cluster using Onefs API.

    Zone Readiness - Date-Time Validation

    The Date-Time Validation is used to validate that the time difference between the cluster nodes, and between clusters and Eyeglass are within an acceptable range that will not affect SyncIQ operations.  SyncIQ commands like re-sync prep can fail if the time between cluster nodes is greater than the time between the eyeglass vm and the cluster with regards to latency of issuing the API call (a scenario where a node returns a timestamp for a step status message is earlier than the beginning of the Re-sync prep request).  API calls can return different completion times between clusters.  Differences here can cause resync prep failover commands to fail, if the difference between Eyeglass and the source cluster is greater than the time it takes for a resync prep command to complete.

    NOTE: This condition under which timing differences cause resync failover commands to fail is rare and hard to detect manually.  In release 1.8 Eyeglass can detect this condition.  It's best practise to use NTP on clusters and the Eyeglass appliance.  This allows failover logs and the new feature in release 1.8 or later to collect cluster SyncIQ reports for each step and append to the failover log. This will make debugging multi step multi cluster failover simpler.  This process will require time to be synced.

    For each Cluster the following checks are done:  

    Date-Time ValidationNotes:
    Nodes ValidationValidation that the maximum time difference between the nodes of a cluster is less than the time required for the cluster node time request made by Eyeglass to complete.
    Eyeglass & Clusters Validation

    Validation that the earliest node time for a cluster and the Eyeglass appliance time are less than the time required for the cluster node time request made by Eyeglass to complete plus a default additional skew factor (default 1s).

    Executed if Nodes Validation is OK.

    Zone Path Validation

    Zone Path Validation provides the status of Access Zones. Status of OK indicates that the Access Zone paths have no conflicts. Status of ERROR indicates that this Access Zone collides with another Access Zone's path.

    FQDN Alias Validation

    If cluster was added to Eyeglass with FQDN SmartConnect name for management, this SmartConnect zone must have an igls-ignore hint applied to avoid a failover impacting Eyeglass access. Error indicates that no igls-hint was found on the IP pool for the SmartConnect zone used for cluster management. OK indicates that  igls-ignore hint was found.


    IP Pool Failover Readiness

    This interface shows each Access zone and the IP pool defined within the access zone.  Expanding each pool will show the SyncIQ policies that are mapped to the pool.    

    1. The Access zone column shows cluster:zone name.
    2. Pool mapping will show the pool to pool igls-hints that map a pool on source cluster to target and allows viewing the mapping
    3. Target cluster this pool will failover too
    4. Last Successful Readiness Check is the day and time that Failover readiness Assessed this pool readiness
    5. Map policy to pool allows mapping a policy or more than one policy to a pool and allows viewing the mapping for all pools in the access zone.
    6. DR Failover Status shows the highest severity state for all validations OR it will show failed over status if the pool has been failed over.




    Pool Validations

    The pool validations are  the same as Access Zone readiness with the key difference being they only apply to the pool itself and not the whole zone.  This allows a single pool to be viewed and ready for failover independantly.


    Pool Readiness Validation

    The Pool Readiness validation that is unique to IP pool failover is the un-mapped policy smartconnect/ip pool status. and the overall pool readiness that summarizes the pools status.

    Un-mapped policy validation Overview

    1. This verifies that all synciq policies in the zone have been mapped to a pool.
    2. A pool may have more than one SyncIQ policy mapped.
    3. A syncIQ policy may NOT be mapped to more than one pool.
    4. Any SyncIq policy not Mapped using the Dr Dashboard IP pool mapping interface, will raise this error message and WILL block failover for all pools in the access zone until corrected.   




    Overall pool validation status


    Network Visualization

    A new way to view Isilon clusters, DR status, and jump to the DR Dashboard.  The Network Visualization feature allows you to visualize DR and cluster replication. This first release offers the first in several enhancements aimed at visualizing data, data flows, and storage across one or more Isilon clusters. 

    This view indicates which clusters are replicating to each other and direction.  For each cluster, failover readiness status for all failover types is summarized. Any failover readiness error will show as a red arrow from the source to target cluster (failover direction).  Warnings are displayed with an orange arrow.  In the case where there are not errors or warnings the arrow will be green for active replication direction (failover direction) and grey for the failed over (inactive) direction. This simplifies monitoring many clusters replicating.

    To view Network Visualization:

    1. Open the Icon.

    1. Zoom in or out to navigate depth of view.
    2. Click and hold to drag the visual view objects.
    3. Click a cluster to get view of active Sync Data on the cluster viewed by Failover mode and status.
    4. Click on hyperlink to hump to DR Dashboard Directly from the Network Visualization window.

    Copyright Superna LLC