If the primary Tivoli® Storage Manager server for the Tivoli Storage Manager for Space Management client is unavailable, you can manually configure the Tivoli Storage Manager for Space Management client to connect to a secondary server. You can recall files from the secondary Tivoli Storage Manager server but cannot migrate files to the secondary server.
The primary Tivoli Storage Manager server for the Tivoli Storage Manager for Space Management client must be one that replicates client node data.
In a multiple-server environment, each Tivoli Storage Manager server includes storage pools for backup and migration. All pools used for backup and migration must be replicated to the same secondary server.
The backup-archive client can automatically fail over to the secondary server when it is configured for failover.
The Tivoli Storage Manager for Space Management client, however, does not automatically fail over to the secondary server. You must manually edit the dsm.sys file to connect to the secondary server. Any secondary server information in the replservername stanza and myreplicationserver option is ignored by the Tivoli Storage Manager for Space Management client.
Functions that require write access to the secondary Tivoli Storage Manager server are not available for a space managed file system. You cannot back up, archive, or migrate files to the secondary server from a space managed file system. You can restore, retrieve, and recall from the secondary server.
With the backup-archive client, you cannot restore migrated files as stub files. Migrated files can only be restored as resident files.
To switch back to the primary Tivoli Storage Manager server, repeat the steps, but change the value of the servername option from the target server to the source server.