IBM Tivoli Storage Manager for Space Management, Version 7.1

Enabling a file system to be managed by multiple Tivoli Storage Manager servers

Enable multiple-server support for each Tivoli® Storage Manager for Space Management client in the GPFS™ node, then add Tivoli Storage Manager servers to manage the file system.

In a multiple-server environment, the Tivoli Storage Manager server to which a file is backed up must be the server to which a file is migrated. Before the upgrade, each file system on a GPFS cluster that is managed by a Tivoli Storage Manager for Space Management client must be managed by a single Tivoli Storage Manager server. That means that files on a file system must be backed up and migrated to the same Tivoli Storage Manager server.

A file system that is managed by multiple Tivoli Storage Manager servers must be GPFS version 3.4 or later and must be enabled for Data Management Application Programming Interface (DMAPI).

A single Tivoli Storage Manager for Space Management client can use only HSM daemons (dsmmonitord and dsmscoutd) or GPFS policy to manage automatic migration. A Tivoli Storage Manager for Space Management client cannot use both HSM daemons and GPFS policy to manage automatic migration.

Multiple-server support requires that automatic migration is driven by the GPFS policy engine. Before you upgrade to multiple-server support, you must configure GPFS appropriately.

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.

For information about using the GPFS backup command mmbackup with a file system that is space-managed by multiple Tivoli Storage Manager servers, see the GPFS FAQs topic in the IBM® Cluster Products information center: http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/topic/com.ibm.cluster.gpfs.doc/gpfs_faqs/gpfsclustersfaq.html.

The following steps enable a file system to be managed by multiple servers.

  1. Set option hsmdisableautomigdaemons=YES for each Tivoli Storage Manager for Space Management clientin the GPFS cluster. Setting hsmdisableautomigdaemons=YES disables the automatic migration daemons dsmmonitord and dsmscoutd. The dsmmonitord and dsmscoutd daemons do not drive automatic migration in a multiple-server environment. If you do not disable the dsmmonitord and dsmscoutd daemons, they continue to run and use system resources.
  2. Set option hsmmultiserver=YES for each Tivoli Storage Manager for Space Management clientin the GPFS cluster.
  3. Add to the list of servers the Tivoli Storage Manager server that currently manages the file system by issuing the following command: dsmmigfs addmultiserver -server=server_name file_system_name. You can determine the Tivoli Storage Manager server that currently manages the file system with the following command: dsmmigfs query -detail.
  4. Run the dsmMultiServerUpgrade.pl script.

    The script couples all files on a file system with the Tivoli Storage Manager server that manages the migration copies and backup versions. The script calls the dsmreconcile command to run a special reconciliation that couples the files with the server.

  5. Optional: Add additional servers to manage a file system. For each additional server, issue the following command: dsmmigfs addmultiserver -server=server_name file_system_name.
To query status of the multiple-server environment, issue the following command: dsmmigfs querymultiserver file_system_name. You can add more Tivoli Storage Manager servers to the list of servers that manage a file system.


Feedback