Configuring HSM on IBM Storage Scale clusters

Edit online

IBM® Storage Scale is a high-performance cluster file system, providing concurrent access to one or more file systems from multiple nodes. You can configure a space-managed file system to become a part of a resource group in an IBM Storage Scale cluster. If there is a system failure, you can access your data from another system.

About this task

The space management client on IBM Storage Scale file systems also supports cascading and rotating takeover relationships in the same manner as the backup-archive client. The dsm.opt file and the dsm.sys file are in the standard /opt/tivoli directory for IBM Storage Scale Linux®, or the /usr/tivoli directory for IBM Storage Scale AIX®. You can also use the DSM_CONFIG environment variable that you set in the start script. However, the behavior must be identical on all nodes. Across different nodes, the server stanza must have the following characteristics:

  • The server stanza name must be the same on each system.
  • The server stanza must use ASNODENAME, and the ASNODENAME must be the same for the server stanza on each system.
  • The server stanza must point to the same IBM Storage® Protect server on each system.

You can increase file transfer performance, by using other IBM Storage Scale nodes within the cluster environment for migration and recall. Use the asnodename option to share the IBM Storage Scale file space on the server.

You can control distributed recall by setting the option hsmdistributedrecall to NO on all source nodes that you do not want to recall files.

To enable distributed migration and recall capabilities follow these steps:

Procedure

  1. Install the space management client on more than one (for example, three) IBM Storage Scale nodes in the cluster environment.
  2. Register each space management client node with the IBM Storage Protect server. These nodes are used for managing HSM file systems and are used for distributed HSM. Nodes that are used only to access data of space-managed file systems do not require HSM, and are not required to be registered on the IBM Storage Protect server.
  3. The IBM Storage Protect server administrator must use the grant proxynode server command. Use the command to grant proxy authority to the source nodes to access the node name where the IBM Storage Scale file systems are stored.
  4. Update the options file on each source node. Specify the asnodename option to access the common file space for the space-managed file systems on the IBM Storage Protect server.

Example

Configuration examples are available in the IBM Storage Protect for Space Management-IBM Storage Scale integration field guide.

For information about configuring IBM Storage Scale integration with the space management client, see Technote 7018848.