Backing up multiple nodes with client node proxy support

Edit online

Backups of multiple nodes which share storage can be consolidated to a common target node name on the IBM® Storage Protect server. This method is useful when the system that runs the backup can change over time, such as with a cluster. You can also use the asnodename option to restore data from a different system other than the one which ran the backup.

About this task

Use the asnodename option on the dsmInitEx option string to back up, archive, restore, and retrieve, query, or delete data under the target node name on the IBM Storage Protect server. You can also specify the asnodename option in the dsm.opt or dsm.sys file.

Restriction: Do not use target nodes as traditional nodes, especially if you encrypt your files before you back up to the server.

Procedure

To enable this option, complete the following steps:

  1. Install the API client on all nodes in a shared data environment.
  2. If not already registered, register each node with the IBM Storage Protect server. Register the common "target" node name to be shared by each of the agent nodes that are used in your shared data environment.
  3. Register each of the agent nodes in the shared data environment with the server. The agent node name is used for authentication. Data is not stored by using the agent node name when the asnodename option is used.
  4. Ask your administrator to grant proxy authority to all nodes in the shared environment to access the target node name on the IBM Storage Protect server, by using the grant proxynode command.
  5. Use the query proxynode administrative client command to display the client nodes that have the authority to perform client operations on behalf of another node. This authority is granted by the grant proxynode command. Or use the dsmQuery command with the query type qtProxyNodeAuth to see the nodes to which this node can proxy.
  6. If the application is using user encryption of data, not TSMENCRKEY, ensure that all nodes use the same encryption key. You must use the same encryption key for all files that are backed up in the shared node environment.