Bob, We have some situations where we want to do something similar. What I have found to be the simplest is to set up each machine as if they were going to be backed up individually, with dsm.opt files that reference their unique machine names. This opt file is used for the dsmcad and scheduler services. Then I create a 2nd opt file on each machine that uses the common nodename I want all the data stored under. Then rather than scheduling an incremental backup, I create a schedule(s) that are defined as command action, with the object pointing to a simple batch file that I have copied to each machine. This script runs the dsmc i command using the -optfile=<2nd optfile> parameter. This way each machine is easily scheduled but the data all gets backed up under the common nodename. I have examples if you want to email me offline.
Steve Schaub Systems Engineer, Windows Blue Cross Blue Shield of Tennessee -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth Sent: Thursday, August 14, 2008 1:36 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] 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 Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm