Tivoli Storage Manager for Windows Quick Start


Managing TSM on a Cluster

For most tasks, you can administer a virtual TSM server as you would a nonclustered server. However, you must use the Cluster Administrator to perform some important tasks. The Cluster Administrator is available through the Administrative Tools program group. The Cluster Administrator main window displays a detailed view of a virtual server configuration, including the physical Windows servers that make up the cluster and their resources, network connections, and status.

Use the Cluster Administrator to view the components of a virtual server configuration and to start, stop, or fail back a virtual server that has failed over. If you use the TSM Server Utilities or some other method to stop a virtual TSM server, Clustering Service treats the shutdown as a failure and restarts the server on the cluster's secondary node. A virtual TSM server should be controlled from the Cluster Administrator rather than the Windows NT Service Control Manager.

There are reasons other than a systems failure for manually moving a virtual TSM server from its primary node to its secondary node. For example, if the Windows server acting as the primary node requires hardware or system maintenance, you may use the Cluster Administrator to move control of the virtual TSM server to the secondary node until the maintenance is completed. Clients will experience a failover, just as if the primary server failed and the secondary server had taken over the virtual TSM server. After the TSM server has been moved to the secondary node, TSM Server Utilities are no longer available from the primary node. Run the TSM utilities from the secondary node of the cluster.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]