>Here's a good one for a Friday afternoon....
>
>We've had a requirement to temporarily suspend expiration of objects on
>selected client nodes.
>
>We copied the active policy set for the domain containing these nodes
>and set all backup and archive copy group parameters to NOLIMIT, and
>activated this new policy set.  I have verified that I see these new
>values from the client side (q mgmt -detail).
>
>The strange part is that now when we run expiration processing in
>verbose mode, as the processing hits the filespaces for these nodes, it
>is still reporting statistics of  many hundreds of backup objects being
>deleted.  How is this possible?!?

I believe that the documentation of expiration mechanics in the Admin Guide
manual cover this...  When a Backup is performed under a prevailing policy
set, it will push in new Active versions of files, and effectively push out
the oldest Inactive version which exceeds the versions retained value: it
marks it for expiration.  Once a file is marked, I don't know that anything
can unmark it - even extending policy values.  Thus, the next Expire Inventory
will cause the marked files to evaporate.  And the manual describes how files
can otherwise be flagged for expiration, other than date-based.

Whereas your requirement is to suspend expiration, I would not run expiration.

  Richard Sims