IBM Tivoli Storage Manager for Space Management, Version 7.1

Removing a Tivoli Storage Manager server from a multiple-server environment

You can remove a Tivoli® Storage Manager server from an environment that supports multiple servers.

Before you remove a server from managing a file system, recall all files from the Tivoli Storage Manager server to the local file system. Then, remove the server with the following steps:
  1. Remove the Tivoli Storage Manager server from the multiple server list by issuing the following command: dsmmigfs removemultiserver -server=server_name file_system_name. Run the command for all file systems that were managed by the server. After you run the command, files are not backed up or migrated to the server that was removed. You can still recall migrated copies and restore backup copies from the server that was removed.
  2. Run the dsmMultiServerRemove.pl script.
    The dsmMultiServerRemove.pl script does the following three tasks:
    1. Recalls all migrated files that are coupled with the Tivoli Storage Manager server that was removed to the specified file system.

      The Tivoli Storage Manager for Space Management client determines how much space is required to recall all files to the file system. If there is not enough space, the Tivoli Storage Manager for Space Management client notifies you. To remove the server, make space available and run the script again.

    2. Reconciles the specified file system with the Tivoli Storage Manager server that was removed. The following reconciliation tasks are completed:
      • The Tivoli Storage Manager for Space Management client verifies that valid objects for each local stub file exist in the space management pool of the specified Tivoli Storage Manager server.
      • When orphans are identified, their names are recorded in the .SpaceMan/orphan.stubs file.
      • The Tivoli Storage Manager for Space Management client expires all files in the space management storage pool on the Tivoli Storage Manager server.
      Note: The script does not expire backup copies. If you want to also expire backup copies, you can modify the script by adding the backup-archive client command dsmc expire.

      The dsmMultiServerRemove.pl script calls the dsmreconcileGPFS.pl script for the reconciliation.

    3. Uncouples all files that are coupled with the Tivoli Storage Manager server that was removed.
    More than one recall and reconciliation process can run simultaneously.
    For example, you can simultaneously remove server TSM_server from several file systems with commands like the following commands:
    dsmMultiServerRemove -server=TSM_server file_system_A
    dsmMultiServerRemove -server=TSM_server file_system_B
    dsmMultiServerRemove -server=TSM_server file_system_C
To query status of the multiple-server environment, issue a command like the following command: dsmmigfs querymultiserver file_system_name.

After files are decoupled from the Tivoli Storage Manager server that was removed, they can be migrated and backed up to another server.

If at least one other Tivoli Storage Manager server manages the file system, the file system is still space-managed.



Feedback