I do not believe that the DOMAIN option is valid for the ARCHIVE function. The description for DOMAIN is the drives to be included for incremental backup processing. For ARCHIVE you have to specify what you want processed in the OBJECTS= parameter for the schedule. ARCHIVE also does not process your systemobject, system services or system state objects. If you want to use a schedule and ARCHIVE for everything, you'll need to specify each drive in a separate schedule for each node. OBJECT='C:\* D:\*'for example. It is not dynamic in that if the admin adds a drive, you will need to adjust the schedule to include the new drive.
Bill Boyer "Nothing is foolproof to a sufficiently talented fool." - Murphy -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Clark Sent: Monday, October 22, 2007 11:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Scheduling a full archive of data once/month Something like: 1). def sched <domain> monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain="all-local"' expiration=10/30/2014 2). associate your clients with the schedule ----- Original Message ----- From: "Joni Moyer" <[EMAIL PROTECTED]> To: <ADSM-L@VM.MARIST.EDU> Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month > Hello everyone, > > I have just received the task of scheduling an archive of all data > from several windows servers the first Saturday of every month for 7 years. > What is the best method of accomplishing this? I would like to do > this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any > suggestions are greatly appreciated! > > ******************************** > Joni Moyer > Highmark > Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 > Fax: (717) 302-9826 > [EMAIL PROTECTED] > ********************************
