Protocols cluster disaster recovery limitations and prerequisites

For protocols cluster disaster recovery (DR) in an IBM Storage Scale cluster, the prerequisites and limitations are as follows.

Ensure that the following prerequisites are met for the secondary cluster for disaster recovery in an IBM Storage Scale with protocols.

  • IBM Storage Scale is installed and configured.
  • IBM Storage Scale code levels are the same on the primary and secondary clusters.
  • IBM Storage Scale code levels are the same on every protocol node within a cluster.
  • Cluster Export Services (CES) are installed and configured, and the shared root file system is defined.
  • All protocols that are configured on the primary cluster are also configured on the secondary cluster.
  • The authentication on the secondary cluster is identical to the authentication on the primary cluster.
  • All exports that need to be protected by using AFM DR must have the same device and fileset name, and the same fileset link point on the secondary cluster as defined on the primary cluster.
  • IBM® NFSv3 stack must be configured on home cluster for the AFM DR transport of data.
  • No data must be written to exports on secondary cluster while cluster is acting only as a secondary cluster before a failover.

The following limitations apply for disaster recovery in an IBM Storage Scale cluster with protocols.

  • Only data that is contained within independent filesets can be configured for AFM-based Async Disaster Recovery (AFM DR). Therefore, all protocol exports that you want to be protected by DR must have the export path equal to the independent fileset link point.
  • Backup and restore of the authentication configuration is not supported.
  • After failover and failback or restore, all clients need to disconnect and then reconnect.
  • If --file-config --restore is specified, perform the follow steps:
    • On failover: file authentication must be removed and then reconfigured on the secondary cluster.
    • On restore: file authentication must be removed and then reconfigured on the primary cluster.
    • On failback: file authentication must be removed and then reconfigured on both primary and secondary clusters.

  • IBM Storage Protect for Space Management and IBM Spectrum Archive migrated data within protocol exports is not supported within protocols cluster DR.

  • IBM Storage Protect configuration file information is not automatically protected through protocols cluster DR.