I have a win2k cluster as well. We currently have the local backup/archive client backing up each associated resource on each cluster node. I want to configure TSM for failover services as well. My understanding of the install goes like this: 1. Install the b/a client on both cluster nodes. 2. Create a local dsm.opt file for each cluster node and schedule service. 3. Create an additional dsm.opt file(with clusternode=yes) for each cluster group and place it on a resource drive the opt file is associated with.(make sure the proper resource drives are failed over to each clusternode to ensure access) 4. Create a seperate schedule for each cluster group. I.e. If you have: svrA, svrB, clusternodeA, clusternodeB. There would be 3 schedules on each server: SVRA: svrAsched, clusternodeAsched, clusternodeBsched. SVRB: svrBsched, clusternodeAsched, clusternodeBsched. 5. Create a Generic Service on each Clustergroup to handle failover.
My question is by creating seperate groups for the TSM backups, does that handle failover more gracefully? I ask this because we had issues on first attempt of failover and backed out of the procedure to do more research. I am not terribly familiar with MS Cluster so if this is a stupid question I apologize in advance. Bud Brown Information Services Systems Administrator 303-436-5986 -----Original Message----- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 8:23 AM To: [EMAIL PROTECTED] Subject: Re: TSM win2k cluster install What I have done is installed TSM Client on both nodes on their local drives. I then created 2 dsm.opt files (one called dsm.opt and the other dsmlocal.opt). The dsm.opt file contained clusternode=yes, which you will only see the shared drives. The dsmlocal.opt does not have the clustermode option in it. In Cluster admin I created a separate group called TSM Backups and put in there the TSM Scheduler, Client, and Journal services (make sure you have these services set to manual start - Cluster admin will control the start/stop of these services). This will allow Windows to start/stop the services for TSM depending on what node is active. I then created a 2nd schedule on each node (2nd service) using the DSMLOCAL.OPT file. I called this "TSM Backup for local node" (service name). This service will also be installed on each node in the cluster and will be set to automatically and will NOT be in the cluster admin group of TSM. This will backup the local drives and the System.objects of each node. If you need more detail let me know and I will send screen shots and more info to your email. Joe Cascanette The Cumis Group Limited -----Original Message----- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:38 AM To: [EMAIL PROTECTED] Subject: TSM win2k cluster install We just installed a WIN2k Cluster and I'm a little confused as to what to do with TSM. If I read the book correctly, I'm easily confused by the way, it looks like I'm supposed to install the TSM client more than once. Once on a local disk and again on a disk out on the SAN the cluster is using. Would someone who's familiar with the steps for installing and configuring please drop me a line so I can hopefully get this backed up properly. If you have the steps outlined in a document that would be great. Thanks for the help...... Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
