Correct me if I'm wrong, please.

On Microsoft OS;

If you schedule an automatic Archive.  The Archive will archive every file 
every time that it runs.

I think that archiving would be more functional if it acted similar to the 
backup client.  The backup client is a set it and forget
it every client can use the same server schedule.  Each client will determine 
what is included in the backup.

With the archive scheduling, each server schedule is specific to the client.  
Logically, it seems to defeat the client server
architecture.

IMHO, the backup client features that would benefit the archive client:
 1) use the dsm.opt file for determining what will be included in the archive.
 2) Archive only items that have not been archived.  For example, new or 
changed items.  Ignore items that have been archived and
not changed.  Of course, I would expect the archive of a changed item would 
completely replace the old archive of that item,
otherwise it would be an incremental backup.

If I'm wrong about how archive works I would appreciate some feedback.

Yes, I know that the archive can delete the file so it is not archived again, 
but that defeats the purpose if just want the file to
also be archived off-site.  And, yes I can use backup and a different 
management class to accomplish what I'm looking for.  But,
why?

ITSM is a terrific product and I may be the only person that thinks archive 
should work differently.

I'm off my soapbox,

sal

Vital Data Systems, LLC
salm AT vitalds DOT com


> In poking around some more, I found that the TSM Backup-Archive Clients
> Install/Users Guide has the "include.archive XXXXXXXXXXXX" statement in
> the normal include/exclude file.
>
> I will try this and see if it works.
>
> I can do manual client archives via the GUI so I know archives work.
>
> Thanks for your trouble.
>
>
>
> Ken Sedlacek
> AIX/TSM/UNIX Administrator
> ksedlacek AT kyrus DOT com
>
> IBM Certified Specialist: RS/6000 AIX v4.3 Support
> IBM Certified Specialist: RS/6000 SP & PSSP 3
> Tivoli Certified Consultant - Tivoli Storage Manager v4.1
>
>
> __________________
>
> Enviro:
>
> W2K TSM 5.1.6.3
> W2K client 5.1.5.15
>
> Client has been backing up normally with schedmode=polling.
>
> I have never used archives before, so I need some help here.
>
> I setup the archive copygroup to keep archives for 2555 days (7 years).
>
> I created an archive schedule and thought that would be it as far as
> archiving configuration goes, but I received the following error in the
> client dsmsched.log:
>
> 08/15/2003 15:02:19 ANS1079E No file specification entered
> 08/15/2003 15:07:19 ANS1079E No file specification entered
> 08/15/2003 15:12:19 ANS1079E No file specification entered
> 08/15/2003 15:17:20 ANS1079E No file specification entered
> 08/15/2003 15:22:20 ANS1079E No file specification entered
>
> The Message manual indicates that "You did not enter a file specification
> as prompted".
>
> Where does one enter the "file specification" for archive if the archive
> is being done in a polling schedmode?
>
> Doesn't archive just read the client dsm.opt file for the
> includes/excludes and use this for the archive??
>
> I am not using CLOPTSETs.
>
> TIA
>
>
> Ken Sedlacek
> AIX/TSM/UNIX Administrator
> ksedlacek AT kyrus DOT com
>
> IBM Certified Specialist: RS/6000 AIX v4.3 Support
> IBM Certified Specialist: RS/6000 SP & PSSP 3
> Tivoli Certified Consultant - Tivoli Storage Manager v4.1
>
>