DST supports using DST shadow volumes with OES Cluster Services for Linux for clusters of up to 16 nodes. Clustering is supported for NSS volumes on shared Fibre Channel and iSCSI devices. Users can access files via NCP and via either OES CIFS or SMB/CIFS.
The following caveats apply:
The primary cluster resource must be joined to the Active Directory domain in order for the Active Directory users to access the DST shadow volume pair.
All nodes where you plan to fail over the shadow volume must be running OES 2015 or later and be configured for DST. The nodes must have the same configuration of file systems, access protocols, and so on.
DST and the NCP Server services are not cluster aware. They must be installed and configured separately on each node in the cluster.
Global policies for DST must have the same settings on each node in the server. To manage a global DST policy for a given node, open OES Remote Manager for Linux by using the IP address of the node, not the cluster resource. For information about configuring DST global policies, the Section 4.0, Installing Dynamic Storage Technology.
To manage shadow volume policies in a cluster, open OES Remote Manager for Linux by using the IP address of the cluster resource. You can also open OES Remote Manager by using the IP address of the physical node where the cluster resource is currently mounted if you know which node it is on.
The individual shadow volume’s policies fail over along with the shadow volume.
The primary volume and the secondary volume are managed in the primary cluster resource load and unload scripts. This allows the configuration to be failed over or cluster migrated to a different node as a single resource.
For planning information about installing and configuring shadow volumes in a cluster, see. Section 17.0, Configuring DST Shadow Volume Pairs with OES Cluster Services