Archives of multiple nodes that share storage can be consolidated
to a common target node name on the IBM
Spectrum Protect server.
Before you begin
All agent nodes in the multiple node environment should be of the same platform type. Do not use
target nodes as traditional nodes. Use them only for multiple node processing.
Consider the following features of 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
Spectrum Protect server. The
IBM
Spectrum Protect server node settings and schedules
for the agent node are ignored.
- You cannot perform a system state or system services backup or restore.
- You cannot access another node (either from the GUI drop down or use of the
fromnode option).
- You cannot perform a NAS backup or restore.
About this task
Consolidating archived files to a common target node name on the server is useful when the
workstation responsible for performing the archive can change over time, such as with a Xsan or
cluster. The asnodename option also allows data to be restored from a different
system than the one which 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
Spectrum Protect server. This support is only
available with IBM
Spectrum Protect V5.3 and higher.
Tivoli® Storage Manager FastBack clients are also
backed up using client node proxy.
Configuring your environment for proxied operations is a multiple step procedure that involves
setting options and commands on the backup-archive client and on the server.
Procedure
Perform steps 1 through 5 to install the client and grant proxy authority
to the nodes that can perform archive procedures on behalf of another node.
-
Install the backup-archive client on all nodes in a shared data environment.
-
Register each node with the IBM
Spectrum 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.
-
Register each of the nodes in the shared data environment with the IBM
Spectrum 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.
-
Grant proxy authority to all nodes in the shared environment to access the target node name on
the IBM
Spectrum Protect server, using the GRANT PROXYNODE
command (IBM
Spectrum Protect administrator).
-
Use the QUERY PROXYNODE administrative client command to display the client nodes of the
authorized user, granted by the GRANT PROXYNODE command.
Step 6 sets ensures that
archived files are encrypted on the server.
-
Set the encryptkey option in the options file.
Specify encryptkey=save in the options file to save the encryption key in the
IBM
Spectrum Protect password file. Back up at least one
file with asnode=ProxyNodeName to create a local encryption key on each agent node
in the multiple node environment.
Specify encryptkey=prompt in the options file if you want the node users to
manage the encryption key. Ensure that users of the agent nodes in the multiple node environment are
using the same encryption key.
Repeat this step if you change the encryption key. Use the same encryption key for all files that
are backed up, in the shared environment.
Perform steps 7 to
step 10 to enable multinode
operation, from the GUI.
-
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.
-
Select to open the preferences window.
-
Select the General tab and fill in the As Node
Name field with the name of the proxy authorized target node.
-
Click Apply and then OK to close the preferences
window.
Perform step 11 to verify
that your client node is now accessing the server as the target node.
-
Open the tree window and verify that the target node name specified by the As Node
Name field is displayed.
Alternatively, you can verify that the target node name shows in the Accessing As
Node field in the Connection Information window.
- Optional:
To return to single node operation, delete the As Node Name from the
Accessing As Node field in the tab.
