Check pp. 69-75, Chapt. 8 (Setting Common Options) in the "TSM for Unix: Using The Backup-Archive Clients" book; dsm.sys belongs in the installation directory, dsm.opt (or other "xxx.opt") file can reside anywhere, and can be pointed to via DSM_CONFIG. You could create multiple stanzas in dsm.sys, where one stanza uses nodename=node1, other specifies node3, then control which stanza is used based on whether you're doing the non-shared disks or the shared disks. Also, it's nice to use the centrally-defined client option sets, where feasible (it doesn't solve your need for multiple node names, but...) When we had HACMP, we actually used the fail-over server as the "normal" TSM server for the cluster and connected the library to it; our challenge (nominally) was to ensure continued backup server operation after a fail-over... since the IP "identity" moved from primary to secondary, it was a bit of a trick to keep outside references coming to the NIC defined for backups as well as continue production operation, as well as backup the shared disk resources using the same node name regardless of who currently owns it. Hope this helps. Don France Technical Architect - Unix Engineering/P.A.C.E. San Jose, CA mailto:[EMAIL PROTECTED] PACE - http://www.pacepros.com Bus-Ph: (408) 257-3037 -----Original Message----- From: Herb Girard/CanWest/IBM [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 07, 2000 11:27 AM To: [EMAIL PROTECTED] Subject: Configuring dsm.sys and dsm.opt for multiple clients on one host Our environment includes an AIX/HACMP cluster. Some disks are shared, non-concurrently, by the active and standby hosts. We have configured three TSM client nodes, one permanently on each host to back up its non-shared disks, and a third that runs on whichever host is accessing the shared disks. In order to do this, we need separate include/exclude lists for the nodes, which requires separate dsm.sys files. The TSM 3.7 "Installing the clients" manual (p.34) says "Do not put any user created files into /usr/tivoli/tsm/clients/ba/bin, the directory into which the TSM product is installed.... Include-exclude files, dsm.opt and dsm.sys files should not reside in this directory". Later on (p.48) the same manual says that the DSM_DIR environmnet variable must "point to the executable file dsmtca, the resource files, and the dsm.sys file. ... If DSM_DIR is not set, the executables are expected in the default installation directory." Sounded to me like you can;t get there from here. Our solution was to make a copy of /usr/tivoli/tsm/clients/ba/bin, put the second client's dsm.sys and dsm.opt files in there and point to it with DSM_DIR and DSM_CONFIG. This works but seems kind of clumsy. Has anyone else encountered this problem and found a more elegant solution? Thanks, Herb ITSD (250) 952-6649 IBM: (250) 380-5483 FAX: (250) 380-5427 Mail: [EMAIL PROTECTED] IBM Canada Global Services 1803 Douglas Street 02/346 Victoria, B.C. V8T 5C3
