DR Configuration Guides
Post SyncIQ Policy Failover Manual Steps
Home

Post SyncIQ Policy Failover Manual Steps

Update Networking for Client Access

Make the necessary networking changes required to redirect your clients to the Failover Target Cluster.  This may involve:

  • PowerScale SmartConnect Zone or Zone Alias updates
  • DNS Updates

Update SPNs

For the case where SMB shares and Active Directory are being used for client access, any add or delete of SmartConnect Zone or Zone Alias will require an SPN update.

Refreshing SMB connection after Failover completed and DNS updated

This section describes steps to refresh an SMB connection post failover and DNS update.

  1. If client was connected to the share during the failover, unmount the share (disconnect).
  2. Remount the share (connect). Check Kerberos and SPN on the target cluster machine account.
  3. Test read/write against newly mounted shares.
  4. If step 3 fails, the original connection information is likely cached on the client machine.  The data in this case would continue to be available, however it would be Read-Only.  Writes would fail. To remove the cached connection information, open a Window cmd window and type the command:

ipconfig /flushdns

  1.  Test read/write against newly mounted share again.
  2.  If step 5 fails, it is likely a DNS cache issue and needs to be looked at upstream DNS servers.

Refreshing NFS connection after Failover completed and DNS updated

Please refer to document section steps to refresh an NFS connection post failover and DNS update.

Post SyncIQ Policy Failover Checklist

The following sections outline what can be checked post SyncIQ Policy failover to verify execution of all of the steps.

IMPORTANT: If the failover was done with the Controlled failover option unchecked, then some steps on the failover SOURCE cluster will not have been executed.  This is outlined in Appendix 1 in this document.

File System Updates

On the failover SOURCE cluster (the cluster you failed over FROM), the directories and sub-directories corresponding to the SyncIQ Policies that were failed over are read-only.

On the failover TARGET cluster (the cluster you failed over TO), the directories and sub-directories corresponding to the SyncIQ Policies that were failed over are writeable.

SyncIQ Policy Updates

On the failover SOURCE cluster (the cluster you failed over FROM), for the SyncIQ Policies that were failed over:

  • SyncIQ Policies are Disabled in OneFS
  • Eyeglass configuration replication jobs related to these SyncIQ Policies are in Policy Disabled state
  • SyncIQ Policies in OneFS have their schedule set to manual

On the failover TARGET cluster (the cluster you failed over TO), for the SyncIQ Policies that were failed over:

  • SyncIQ Policies are Enabled in OneFS
  • The corresponding Eyeglass Configuration Replication Jobs are also in Enabled state
  • SyncIQ Policies have same schedule that was originally set for the policy on the failover SOURCE cluster

NOTE: If you have Eyeglass “INITIALSTATE” property set to disabled for AUTO jobs (check this using the “igls adv initialstate show” command in the Eyeglass Admin Guide here), the Eyeglass Configuration Replication job for the mirror SyncIQ Policy created during the first failover will be in User Disabled state.  This job should be enabled following the instructions in the Eyeglass Admin Guide here.

Quota Updates

After the upgrade, there should be no quotas on the failover SOURCE cluster for the SyncIQ Policies that were failed over.  On the failover TARGET cluster you should find all quotas for the SyncIQ Policies that were failed over.

© Superna LLC