Tivoli Header

Administrator's Guide


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 console 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. 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, the TSM console is no longer available from the primary node. Run the TSM Console from the secondary node of the cluster.

Using the Cluster Log on Windows

The TSM Cluster Resource DLL reports events and errors to the cluster log. The cluster log is a very useful troubleshooting tool. When this log is enabled, it records the actions of each component of the Cluster service as the result of each action. The cluster log is a more complete record of cluster activity than the Microsoft Windows Event Log. The cluster log records the Cluster service activity that leads up to the events recorded in the event log. Although the event log can point you to a problem, the cluster log helps you get at the source of the problem.

The cluster log, also known as the diagnostic log, is enabled by default in Windows 2000 and Windows NT. Its output is printed as a .log file in %SystemRoot%\Cluster. For more information, see the Windows 2000 or Windows NT online help documentation.


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