Ok, so the implication here is that there should be multiple Archive management
classes named for say each application, rather than a single set on Archmcs for all
applications.
I currently have set up arch_1y, arch_9m, arch_6m, arch_3m etc
if anyone archives something to say arch_1Y and then wants the retention extended then
they can only retrieve and re-archive (or have the archmc names not match their
retention periods, ugh!)
whereas if I had appA_longterm and appB_longterm both set at 1 year I could change
these independently as the application archive requirements changed.
Does anyone use such a scheme?
Steve Harris
AIX and ADSM Admin
Queensland Health, Brisbane Australia
>>> Richard Sims <[EMAIL PROTECTED]> 25/04/2001 6:44:00 >>>
>Archived copies of files have their expiration date set upon the file being
>archived based on current date plus the duration of the archive management
>class...
Dwight - The Archives table contains an Archive_Date column: there is no
Expiration_Date column, as the files conform to whatever the
prevailing management class retention rules are at the time. So if you
extend your retention policy, it pertains to all archive files, old
and new.
Richard Sims, BU
