Hi Gary, There's a couple ways to go about this:
1. Have a single SERVERNAME stanza in your dsm.sys file, talking to a single node on your TSM server. Setup two more nodes on your TSM server, and use GRANT PROXYNODE to allow the first node to talk to them. You will then use -ASNODE on the client side to select which node you wish to talk to. This has the drawback that you can only have one schedule running at any given time, so if a schedule runs long it could overlap with the start window of the next node. 2. Have two SERVERNAME stanzas in your dsm.sys file, with different NODENAME attributes. Configure one node per NODENAME attribute. Associate your schedules with these nodes, and run one "dsmc sched"/dsmcad process per stanza on the client side. This would allow you to have schedules for each node running concurrently. On Wed, Jan 08, 2014 at 04:11:25PM +0000, Lee, Gary wrote: > 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. -- -- Skylar Thompson ([email protected]) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
