Replicating nodes in a multiple-server environment
If the primary IBM Spectrum Protect server for the space management client is unavailable, you can manually configure the client to connect to a secondary server. You can recall files from the secondary IBM Spectrum Protect server but cannot migrate files to the secondary server. When node replication is used on the IBM Spectrum Protect secondary server, it is not permitted to restore stub files or call the dsmmigundelete command, see APAR IC94316 for details.
Before you begin
The primary IBM Spectrum Protect server for the space management client must be one that replicates client node data.
In a multiple-server environment, each IBM Spectrum Protect server includes storage pools for backup and migration. All pools used for backup and migration must be replicated to the same secondary server.
About this task
The backup-archive client can automatically fail over to the secondary server when it is configured for failover.
However, the space management client 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 space management client.
Procedure
Results
Functions that require write access to the secondary IBM Spectrum Protect 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.
What to do next
To switch back to the primary IBM Spectrum Protect server, repeat the steps, but change the value of the servername option from the target server to the source server.