IBM Tivoli Storage Manager in a Clustered Environment

Chapter 22. VERITAS Cluster Server and the IBM Tivoli Storage Manager Server 945

22.9 Configuring Tivoli Storage Manager devices

Before starting the tests of the Tivoli Storage Manager Server, we create the

necessary storage devices such as library, drives, and storage groups, using the

Administration Center. We created the devices based on Table 22-3 on

page 907.

22.10 Testing the Tivoli Storage Manager on VCS

In order to check the high availability of Tivoli Storage Manager server on our lab

VCS environment, we must do some testing.

Our objective with these tests is to show how Tivoli Storage Manager, on a

Veritas clustered environment, manages its own resources to achieve high

availability and how it responds after certain kinds of failures that affect the

shared resources.

22.10.1 Testing incremental backup using the GUI client

Our first test uses the Tivoli Storage Manager GUI to start an incremental

backup.

Objective

The objective of this test is to show what happens when a client incremental

backup is started from the Tivoli Storage Manager GUI and suddenly the node

which hosts the Tivoli Storage Manager server in the VCS fails.

Activities

To do this test, we perform these tasks:

1. We open the Veritas Cluster Manager console to check which node hosts the

Tivoli Storage Manager Service Group as shown in Figure 22-65.

946 IBM Tivoli Storage Manager in a Clustered Environment

Figure 22-65 Veritas Cluster Manager console shows TSM resource in SALVADOR

2. We start an incremental backup from RADON (one of the two nodes of the

Windows 2000 MSCS), using the Tivoli Storage Manager backup/archive GUI

client. We select the local drives, the System State, and the System Services

as shown in Figure 22-66.

Figure 22-66 Starting a manual backup using the GUI from RADON

Chapter 22. VERITAS Cluster Server and the IBM Tivoli Storage Manager Server 947

3. The transfer of files starts as we can see in Figure 22-67.

Figure 22-67 RADON starts transferring files to the TSMSRV06 server

4. While the client is transferring files to the server we force a failure on

SALVADOR, the node that hosts the Tivoli Storage Manager server. When

Tivoli Storage Manager restarts on the second node, we can see in the GUI

client that backup is held and a reopening session message is received, as

shown in Figure 22-68.

Figure 22-68 RADON loses its session, tries to reopen new connection to server

5. When the connection is re-established, the client continues sending files to

the server, as shown in Figure 22-69.

948 IBM Tivoli Storage Manager in a Clustered Environment

Figure 22-69 RADON continues transferring the files again to the server

6. RADON ends its backup successfully.

Results summary

The result of the test shows that when you start a backup from a client and there

is a failure that forces Tivoli Storage Manager server to fail in a VCS, backup is

held, and when the server is up again, the client reopens a session with the

server and continues transferring data.

22.10.2 Testing a scheduled incremental backup

The second test consists of a scheduled backup.

Objective

The objective of this test is to show what happens when a scheduled client

backup is running and suddenly the node which hosts the Tivoli Storage

Manager server in the VCS fails.

Note: In the test we have just described, we used disk storage pool as the

destination storage pool. We also tested using a tape storage pool as

destination and we got the same results. The only difference is that when the

Tivoli Storage Manager server is again up, the tape volume it was using on the

first node is unloaded from the drive and loaded again into the second drive,

and the client receives a “media wait” message while this process takes place.

After the tape volume is mounted, the backup continues and ends

successfully.

Chapter 22. VERITAS Cluster Server and the IBM Tivoli Storage Manager Server 949

Activities

We perform these tasks:

1. We open the Veritas Cluster Manager console to check which node hosts the

Tivoli Storage Manager Service Group: SALVADOR.

2. We schedule a client incremental backup operation using the Tivoli Storage

Manager server scheduler and we associate the schedule to the Tivoli

Storage Manager client installed on RADON.

3. A client session starts from RADON as shown in Figure 22-70.

Figure 22-70 Scheduled backup started for RADON in the TSMSRV06 server

4. The client starts sending files to the server as shown in Figure 22-71.