I (Bruce Elrick) wrote:
>
> Unlike backups, once a file is archived, its
> retention is set in stone (you can delete archive files however).
> Performing subsequent archives using a different -archmc or with
> a different include/excluding list which binds files to mgmtclasses
> differently will not rebind the previous archive copies, unlike
> backups where changing the mgmtclass for a file in the incl/excl
> list will cause a rebinding on the next backup of that file,
> possibly causing versions to be marked for expiration if the retextra
> or verexists parameters differ.
Perhaps set in stone is too strong.  As Jerry Lawson pointed out,
changing the retention on the archive copy group does change the
expiration of previously archive files. However, as I said, the binding
of a file to a mgmtclass when archiving occurs when the archive is
made, and can be different each time.

Cheers...
Bruce