I don't think there is a way to get around the schedule already running
issue with a single system name for multiple servers. I'm surprised the
TSM server doesn't balk about multiple backups running with the same
node name at the same time.  
Scheduling a dsmc backup inc through windows scheduler would be one way
to eliminate that. 
But they would all try to run at the same time, then they would run at
the same time.

Doesn't each successive backup expire the data from the other systems ?
Or does it ignore it because it's a different filespace ?

Sounds messy. But could be a very interesting licensing loophole ;-)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bob Booth
Sent: Thursday, August 14, 2008 12:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Different nodes backing up under same name

I have a situation that I can't quite get my head around.  It may not be
do-able, however I thought I would ask..

I have a department that wishes to back all of their Windows lab
machines under the name of their main server.  It already works, as the
NODENAME of each lab machine has been changed to the main server name,
and the passwords are consistent.  The filespace names are unique on the
main server, so that is working as well.

The main problem I am having is trying to schedule mess.  They are
behind a firewall, so they are trying to use polling, however when they
attempt to run the polled schedule, the server tells them that the
schedule has already run (because one of the other clients ran it
first).  Is there even a way to do this with the scheduler, or should I
have each client run a windows schedule instead?

Thanks in advance for any advice.

Bob