IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

118 IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

7.1 Client node proxy support and GPFS

Figure 7-2 Client node proxy support and GPFS

Backups of multiple nodes which share storage can be consolidated to a common target node

name on the Tivoli Storage Manager server. This is useful when the machine is responsible

for performing the backup may change over time, such as with a cluster. The asnodename

option also allows data to be restored from a different system than the one which performed

the backup.

򐂰 An

agent node is a client node which has been granted authority to perform client

operations on behalf of a target node.

򐂰 A

target node is a client node which grants authority to one or more agent nodes to

perform client operations on its behalf.

ibm.com/redbooks

International Technical Support Organization

95© 2005 IBM Corporation

IBM ITSO – International Technical Support Organization

Use cases

•Client node proxy support and General Parallel File

System (GPFS)

–An illustration of a GPFS cluster is shown in the next slide

–The GPFS team has written a routine which performs the

following functions on a GPFS file system:

• Scan the entire file system for inode changes

• Create a list of files that have changed

• Parcel out the list of files to an IBM Tivoli Storage Manager

Backup-Archive client node to move the data

Chapter 7. Use cases 119

Figure 7-3 Backing up a GPFS cluster

Scheduling example for backing up a GPFS file system

Each client node authenticates with the server as the same node name, for example,

node_gpfs. This is done by having a dsm.sys file on each machine with an entry:

nodename node_gpfs

The problem with this solution is that the password expiration cannot be managed

automatically. If there are three nodes in the GPFS cluster, each node knows the password to

node_gpfs. If the server expires the password, then one node resets the password and the

other two can no longer authenticate. The only solution is to either turn off node

authentication at the Tivoli Storage Manager server or to manually reset the password and

update all three nodes with the new password.

The Tivoli Storage Manager scheduler is not currently used in this solution. However you can

set up a schedule for node_gpfs, via a macro, to execute the file system scan or workload

created from one client machine. Then this schedule is associated with one of the three

nodes such as node_1.

ibm.com/redbooks

International Technical Support Organization

53

© 2005 IBM Corporation

IBM ITSO – International Technical Support Organization

Use cases

Backing up a GPFS cluster

120 IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

A better solution is available through multinode support. Using the example of three nodes in

the GPFS cluster, which would participate in the backup, follow these steps:

1. Define four nodes on the Tivoli Storage Manager server: node_1, node_2, node_3, and

node_gpfs. node_1, node_2, and node_3 are used only for authentication. All filespaces

are stored with node_gpfs.

REGISTER NODE node_1 mysecretpw

REGISTER NODE node_2 mysecretpw

REGISTER NODE node_3 mysecretpw

REGISTER NODE node_gpfs mysecretpw

2. Define a proxynode relationship between the nodes:

GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1, node_2, node_3

3. Define the node name and asnode name for each of the machines in their respective

dsm.sys files:

nodename node_1

asnodename node_gpfs

4. Optionally define a schedule for only node_1 to do the work:

DEFINE SCHEDULE STANDARD GPFS_SCHEDULE ACTION=MACRO OBJECTS="gpfs_script"

DEFINE ASSOCIATION STANDARD GPFS node_gpfs

5. On the node_gpfs node, run the schedule:

DSMC SCHED

Note: The multiple node design, as described previously, can be exploited only in a UNIX

environment and not on Windows and NetWare Systems. The

asnodename option is

available on Windows systems. However, there is not as much benefit in using this option

because of the filespace naming limitations that are inherent in Windows systems.