Configuring the space management client to connect to a failover IBM Storage Protect server
If the primary IBM Storage® Protect server for the space management client is unavailable, you can manually configure the client to connect to a failover server. You can recall files from the failover IBM Storage Protect server but cannot migrate files to the failover server. When node replication is used on the IBM Storage Protect failover server, you can restore files from the failover server. However, restoring stub files from the failover server is not supported. Instead of restoring the stub files, the resident files are restored. In such a case, when you reconfigure HSM to connect to a failover server, the dsmmigundelete and dsmreconcile commands are not supported.
Before you begin
The primary IBM Storage Protect server for the space management client must be one that replicates client node data.
About this task
The backup-archive client can automatically fail over to the failover server when it is configured for failover.
However, the space management client does not automatically fail over to the failover server. You must manually edit the dsm.sys file to connect to the failover server. Any failover server information in the replservername stanza and myreplicationserver option is ignored by the space management client.
Procedure
Results
Functions that require write access to the failover IBM Storage Protect server are not available for a space-managed file system. You cannot back up, archive, or migrate files to the failover server from a space-managed file system. You can restore, retrieve, and recall from the failover server.
With the backup-archive client, you cannot restore migrated files as stub files. Migrated files can be only restored as resident files.
What to do next
To switch back to the primary IBM Storage Protect server, repeat the steps, but change the value of the migrateserver option from the target server to the source server.