Adding and configuring space management for a file system

When you add space management to a file system, you indicate how and when files are migrated and recalled. You can also deactivate, reactivate, and remove space management from a file system.

When you add space management to a file system, the Tivoli Storage Manager for Space Management client completes the following tasks:

• Creates a hidden directory for the file system named .SpaceMan that stores certain information objects that are required for space management.
• Creates the hsmfsconfig.xml file in the .SpaceMan directory of the file system. This file contains the space management settings that you selected.
  Remember: The .SpaceMan directory is not processed by the Tivoli Storage Manager backup-archive client. Copy the hsmfsconfig.xml file to a directory that is included for automatic backups so that the Tivoli Storage Manager backup-archive client can process the file.
• Updates mount information for the native file system.
• Starts space management for the file system.

  For AIX® GPFS™ and Linux x86_64 GPFS file systems, the dsmwatchd daemon starts at system startup with an entry in the etc/inittab file or with the initctl service. Ensure that DMAPI is enabled on all GPFS file systems that the Tivoli Storage Manager for Space Management client manages. Issue the following command to query this information: /usr/lpp/mmfs/bin/mmlsfs DevicePath -z.

  If Data Management Application Programming Interface (DMAPI) is disabled, enable it with following command: /usr/lpp/mmfs/bin/mmchfs DevicePath -z yes.

  On GPFS, you can change the value for the DMAPI enablement to YES only if the file system is unmounted on all nodes of the cluster. When DMAPI is enabled, the file system can be mounted only if a dsmrecalld daemon is set up on one of the cluster nodes within the GPFS cluster.

  The AIX or Linux x86_64 cluster node to which you add a GPFS file system becomes the preferred node for your file system. If several Tivoli Storage Manager for Space Management client on several AIX or Linux x86_64 cluster nodes are candidates for managing a GPFS file system, the preferred node has precedence. If failover occurs, the Tivoli Storage Manager for Space Management client that manages the file system is not the Tivoli Storage Manager for Space Management client on the preferred node.

  For information about configuring GPFS integration with the Tivoli Storage Manager for Space Management client, see the Tivoli field guide TSM for Space Management for UNIX-GPFS Integration Part I: Policy-driven Threshold Migration at https://www.ibm.com/support/docview.wss?uid=swg27018848.

HSM-created stub files on your space-managed file systems are bound to the space-managed file system. You cannot do the following tasks:

• Move stub files as native stub files (without the migrated data) to other file systems, even if the other file system is space-managed.
• Use the Tivoli Storage Manager raw device backup utility or any other image-based backup utility to restore a space-managed file system to a system other than the original system.
• Use space-managed file systems within cluster replication tools.
• Use any other tools that transfer images between systems.

The following are more considerations:

• You cannot add space management to file systems such as the root file system and the temp file system.
• You can add space management to a nested file system.
• You can add space management to an exported file system.

Do not add space management to the /usr and /var file systems. All of those file systems contain files that your operating system uses regularly.