I have several customers doing this. One, for example, has a machine called CLIENT. It is registered as CLIENT-DAILY to run daily backups, and also as CLIENT-MONTHLY to run monthly backups.
You just have 2 different schedulers, pointing to 2 different dsm.opt files. The first dsm.opt specifies NODENAME CLIENT-DAILY The second dsm.opt specifies NODENAME CLIENT-MONTHLY CLIENT-DAILY is registered in the DAILY domain CLIENT-MONTHLY is registered in the MONTHLY domain. Domains have different schedules, and mgmt. classes have copy groups pointing to different destination disk and tape pools. To simplify I use classic schedulers (running without dsmcad and MANAGEDSERVICES SCHEDULE). Although it should be possible to set up multiple dsmcads too (but it makes my head hurt so I don't). But have never had a problem getting it to work. Can you be more specific about the problems you are having? W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Ehresman,David E. Sent: Wednesday, January 08, 2014 12:48 PM To: [email protected] Subject: Re: [ADSM-L] running two distinct tsm client instances pointing to two different servers on windows box Gary, Maybe a different approach would work. Use the same TSM node but use INCLUDE statements to point different filesystems to different management classes pointing to different disk/tape combinations. David -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Lee, Gary Sent: Wednesday, January 08, 2014 11:11 AM To: [email protected] Subject: [ADSM-L] running two distinct tsm client instances pointing to two different servers on windows box I need to do some testing where a client machine must be two distinct tsm nodes on different servers; or on the same server but a different domain. I've been playing with this, but can't seem to get it working. I want machine client-a backing up to one disk / tape combination, while its alter ego client-b backs up to another disk / tape combination on the same tsm server. Most clients will be windows, with a few linux thrown in. Any ideas would be helpful.
