Tivoli Storage Manager for Windows: Administrator's Guide


Administrator's Tasks

After you have set up your initial cluster or clusters, maintenance needs are minimal. Check your Windows Event log on a regular, if not daily, basis to monitor the activity of the nodes in the cluster. By checking the log, you will be informed that a node has failed and needs maintenance.

The following presents some situations that can occur over time that will affect the configuration or format of your cluster.

Adding a Node to an Existing Cluster

As your business grows or new equipment is added, you may find it advantageous to add an additional node to your cluster configuration. You would still want to do the initial planning to help save you time and ensure a successful implementation. In addition, proceed with the following steps:

  1. Ensure your new configuration is supported by the Windows software application running on your computers. For instance if you have been running Windows Advanced Server (which supports two nodes in cluster), you will need to install Windows Datacenter which supports up to four nodes in a cluster.
  2. Install TSM on the node you are adding if it is not already installed. Ensure the install process uses the same local disk drive letter as the other nodes in the configuration.
  3. Ensure the new node is online and functional and sharing the same shared disk as the other nodes.
  4. Take the TSM Server group offline using the Cluster Administrator.
  5. Modify the TSM server resource in the group and add the new owner node.
  6. Move the TSM server group to the new node.
  7. Bring only the disk resource online for the new node.
  8. Access the TSM Console.
  9. Access the TSM Initial Configuration wizard list and initialize the server for the existing group.
  10. Access the Cluster Configuration wizard and add the new node to the cluster.

Migrating an Existing TSM Server into a Cluster

The reason you might want to migrate an existing server into a cluster is probably the same as why you would a server to a cluster. More than likely you are looking to increase the availability and reliability of data to all your users. By having the server as part of the cluster, you provide an extra level of security by ensuring that no transactions will be missed due to a failed server. The failover pattern you establish prevents future failures.

To migrate an existing TSM server into a cluster, you can either move the clients or perform a backup and restore procedure. The choice depends primarily on the availability and capacity of other TSM server computers in your site and your familiarity with the backup and restore procedure.

Moving the Clients

If you move clients from a nonclustered TSM server computer to a clustered one, you can have the time to gradually migrate your users to the new system and not interrupt services. However, you must have the hardware needed to run two TSM servers simultaneously. You can move clients in either of the following ways:

Backup and Restore

If you have limited hardware resources, you can add an existing TSM server to a cluster by using the backup and restore procedure outline here. For example, suppose you have no hardware other than the two servers to be clustered and you plan to use the computer that is currently running the TSM server as a node. Follow this procedure to remove TSM from the computer and reinstall it in the cluster:

  1. Back up all disk storage pools to a copy storage pool.
  2. Back up the database of the existing TSM server.
  3. Perform the installation and configuration of the cluster.
  4. Restore the database to the clustered TSM server.
  5. Restore the disk storage pool volumes from the copy storage pool.
  6. After you verify that all your data is on the clustered server, delete the old server.


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