We are running a similar setup with our cluster nodes. Cluster1 - nodea, nodeb, nodec - all active. 3-5 cluster groups with disk resources. Which are serving as 3-5 file and print servers. I use the cluster name and "file and print alias name" as my TSM definitions. If you want to add the C drives, those should have a separate schedule service configured the same as a standalone box.
TSM definitions. Clustername_aliasname1 Clustername_aliasname2 Clustername_aliasname3 Clustername_aliasname4 Clustername_aliasname5 On each node of the cluster we create an options file for each tsm definition with the same name in the Tivoli\TSM\baclient directory. Clustername_aliasname1.opt Clustername_aliasname2.opt Clustername_aliasname3.opt Clustername_aliasname4.opt Clustername_aliasname5.opt Create five schedulers and 5 Webclients (if needed) on each cluster node each preceeded by the alias name. Aliasname1 - TSM backup scheduler Aliasname1 - TSM Client acceptor Aliasname1 - TSM Remote Client Agent Create ten cluster resources, 2 per group to allow failover of the scheduler service and the TSM Client Acceptor also preceeded by the alias name. It can be complicated, and even more so when some groups require archives or a different set of rules to back up specific data. I have a three node cluster with 12 different scheduler services and 6 of the definitions require a Web client. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wanda Prather Sent: Monday, July 21, 2008 2:40 PM To: [email protected] Subject: Re: Newbie Question As I understand this, you are not currently backing up any of the cluster drives now with the regular BA client? The usual way to do this is to create a "virtual" TSM client node. Most of my customers register the backup clients for the local filesystems as the node/hostname, and register the "virtual" TSm client name as the cluster name to back up cluster drives. You install a second scheduler service that runs as the "virtual" TSM client to back up the cluster drive(s). (It has it's own dsm.opt file, and it's own scheduler log - they should live on a cluster drive.) That scheduler service has to be made cluster resource, and you typically install that 2nd service on all the cluster nodes so that the backups of the cluster drive(s) can continue, even if the primary owner noder goes down. That 2nd service will typically be running on 1 node, and shut down on the others. The Windows clustering software is repsonsible for starting the service on the other node, if the 1st node dies. If you've never messed with the Windows cluster manager, have one of the Winders admins give you a tour. I'm hesitate to go any further because I'm a little confused by the statement "we have different cluster drives active on different nodes". You have to think a bit about what you are trying to accomplish, and what needs to fail over. If you never intend to run backups in a failover situation, you only have to install the scheduler service for the cluster drive on one node. (OTOH, I had one customer with 4 nodes active-active-active-passive with different Exchange stores active on each node, and it resulted in 5 scheduler services being installed on each node.) Anyway, look in the TSM for Windows client manual, there is an appendix that explains exactly how to set up a TSM backup for a cluster drive. If you only have the 1 cluster drive you care about, it won't be difficult. BTW: are you aware that TSm 5.2, it's been out of support for a long time? suggest you get upgraded soon. On 7/21/08, Matthews, Gary (GSD UK Production Services business) < [EMAIL PROTECTED]> wrote: > > Hi , > > I've inherited a TSM setup recently and it's been ticking over fine > but now I need to make some changes, and thought I'd ask the experts > for some help :-) . It's TSM 5.2 and a W2K/3 environment. One server > we're backing up is a sharepoint cluster, with different cluster > drives active on each node. Currenlty we backup the local drives on > each node, and also a SQL agent backup. The DBA's also backup SQL to a cluster drive. > They now want this drive backed up as well . How do I do this? Bear in > mind, all I've done with TSM so far is checked that the existing > backups worked, so in simple terms please!! :-) > > TIA > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be > copied, disclosed to, retained or used by, any other party. If you are > not an intended recipient then please promptly delete this e-mail and > any attachment and all copies and inform the sender. Thank you. >
