Windows operating systems

Archiving data with client node proxy

Edit online

Archives of multiple nodes that share storage can be consolidated to a common target node name on the IBM® Storage Protect server.

About this task

This is useful when the workstation responsible for performing the archive can change over time, such as with a cluster. The asnodename option also allows data to be restored from a different system than the one that performed the backup. Use the asnodename option with the appropriate command to back up, archive, restore, and retrieve data under the target node name on the IBM Storage Protect server.

Tivoli Storage Manager FastBack clients are also backed up using client node proxy.

To enable this option, follow these steps:
  1. Install the backup-archive client on all nodes in a shared data environment.
  2. Register each node with the IBM Storage Protect server, if it does not exist. Register the common target node name to be shared by each of the agent nodes used in your shared data environment.
  3. Register each of the nodes in the shared data environment with the IBM Storage Protect server. This is the agent node name that is used for authentication purposes. Data is not stored using the node name when the asnodename option is used.
  4. The IBM Storage Protect administrator must grant proxy authority to all nodes in the shared environment to access the target node name on the IBM Storage Protect server, using the GRANT PROXYNODE server command.
  5. Use the QUERY PROXYNODE administrative client command to display the client nodes of the authorized user, granted by the GRANT PROXYNODE command.

Follow these steps to set up encryption with the encryptkey=save option:

Procedure

  1. Specify encryptkey=save in the options file.
  2. Back up at least one file with asnode=ProxyNodeName to create a local encryption key on each agent node in the multiple node environment.

Results

Follow these steps to set up encryption with the encryptkey=prompt option:

  1. Specify encryptkey=prompt in the options file.
  2. Ensure that users of the agent nodes in the multiple node environment are using the same encryption key.
  • If you change the encryption key, you must repeat the previous steps.
  • Use the same encryption key for all files backed up in the shared node environment.

Follow these steps to enable multinode operation from the GUI:

  1. Verify that the client node has proxy authority to a target node (or authorized to act as the target node) using the QUERY PROXYNODE administrative client command.
  2. Select Edit > Preferences to open the preferences window.
  3. Select the General tab and fill in the As Node Name field with the name of the proxy authorized target node.
  4. Click Apply and then OK to close the preferences window.

Follow these steps to verify that your client node is now accessing the server as the target node:

  1. Open the tree window and check that the target node name specified by the As Node Name field appears, or
  2. Verify the target node name in the Accessing As Node field in the Connection Information window.

To return to single node operation, delete the As Node Name from the Accessing As Node field in the General > Preferences tab.

Considerations for a proxied session:
  • A proxy operation uses the settings for the target node (such as maxnummp and deduplication) and schedules that are defined on the IBM Storage Protect server. The IBM Storage Protect server node settings and schedules for the agent node are ignored.
  • All agent nodes in the multiple node environment must be of the same platform type.
  • Do not use target nodes as traditional nodes. Use them only for multiple node processing.
  • You cannot perform a system object or system state backup or restore.
  • You cannot access another node (either from GUI drop down or use of the fromnode option).
  • You cannot use the clusternode option.
  • You cannot perform NAS backup or restore.