Escolar Documentos
Profissional Documentos
Cultura Documentos
A Microsoft Cluster consists of a number of physical servers that are capable of hosting a series of resources. If any
node in the cluster fails, all the resources hosted on that node fail over to another node in the cluster. For ease of
management, resources are combined together into groups, and failover acts at the group level. Resources can be
things like server names and IP addresses, but the ones that apply to TSM are disks, file shares and TSM schedule
resources.
Open up the Windows Cluster Administrator, and on the left hand menu you will see Groups, Resources, Cluster
Configuration, then a list of nodes, or physical servers that are hosting the cluster. Let us assume we have a 2 node
cluster, CLS001 and CLS002, and 5 SAN attached disks, DSK01-5. We also have 2 groups, group-a and group-b. In
this example, group-a contains DSK01-3 and group-b contains DSK04-5. Make a node of the Cluster Name as you
need it to define the schedule services, ours is CL001.
CLABC01
tcpport
TCPServeraddress
1500
TSM001
ERRORLOGNAME
SCHEDLOGNAME
ERRORLOGRETENTION
SCHEDLOGRETENTION
F:\tsm\dsmerror.log
F:\tsm\dsmsched.log
7 D
7 D
PASSWORDACCESS
SCHEDMODE
QUERYSCHEDPERIOD
GENERATE
POLLING
1
CLUSTERNODE
YES
DOMAIN
F: G: H:
Note that the clusternode option is set to YES, and the DOMAIN option picks out the 3 drives on that cluster group.
The TSM schedule and error logs are allocated on the cluster disk, so they move between physical nodes too. Define
another dsm.opt file for the other resource group, with appropriate nodename, log file locations and domains, and
place that file on the 'i' drive.
Next, you need to install schedule services for the cluster nodes, and it is best to do this with a dsmcutil command.
You must do this on both the physical nodes, for each cluster node, so here you would install 4 clustered schedule
services. Start with the server that is hosting the cluster disks, and navigate to the directory where you installed your
client code, usually C:\Program Files\tivoli\tsm\baclient then run these commands.
dsmcutil install SCHED /name:"TSM Scheduler Service - CLABC01"
/clientdir:"c:\Program Files\tivoli\tsm\baclient" /optfile:f:\tsm\dsm.opt /node:CLABC01
/password:nodepassword /validate:yes /autostart:no /startnow:no /clusternode:yes /clustername:CL001
dsmcutil install SCHED /name:"TSM Scheduler Service - CLABC02"
/clientdir:"c:\Program Files\tivoli\tsm\baclient" /optfile:i:\tsm\dsm.opt /node:CLABC02
/password:nodepassword /validate:yes /autostart:no /startnow:no /clusternode:yes /clustername:CL001
Next, fail the groups over the other physical server using Cluster Administrator, then run the same 2 commands
again. If the cluster groups are not both hosted on the same server, then fail over or adjust the way you run these
commands as appropriate.
dsm -optfile=f:\tsm\dsm.opt
this should load up a TSM GUI that points to the correct filespaces and data, and now its just a standard restore