I had always been under the impression that changing the retention in a
management class for archives would cause any existing archives to change
also - But I did find that reference in the postings, and the customer here
was insistent that they had not been able to change retention on archive sets.

I was just sanity checking.

Does the process of policy activation cause the exsting archives to be
updated?


On Friday 03 May 2002 02:57 pm, you wrote:
> I'm pretty sure as long as you just CHANGE the archive group it will change
> the retention settings. Dale was talking about creating a NEW archive
> group. If Dale wanted to change the retention value for 3_Month to actually
> 1 month he would be better of changing the retention value for 3_Month to 1
> month rather than create a new group called 1_Month. Creating a new group
> would do nothing for the existing 3_Month group. I know I changed one of my
> archive groups from infinite to 1 year and saw tapes start to reclaim...
>
> Mark
>
>
> -----Original Message-----
> From: bbullock [mailto:bbullock AT MICRON DOT COM]
> Sent: Friday, May 03, 2002 3:25 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Archive retention question
>
>
>         Wait a second.....
>
>         So, lets say I set up a management class with the archive copypool
> set to 5 years and I archive a bunch of files. A couple of years later,
> legal comes to me and says, "laws have changed, we now need to keep those
> files for 10 years." I have been under the false impression that I could
> change the archive copygroup to 10 years, and the currently archived files
> would hang around for an extra 5 years. This is not so?
>
>         Hmm, just when I thought I had it figured out... So that means I
> must retrieve all 3TB of data to somewhere and re-archive it to keep it
> around for the extra 5 years? Not a pleasant thought.
>
>         I've always wished that I could change the management class an
> archive is bound to ~after~ it has been archived. For example, just last
> week, a DBA archived a dump of a 900GB database, to a 90-day management
> class instead of a 2 year management. Sure, I can delete the bad archive
> and have them re-archive it, but tape cycles and bandwidth don't grow on
> trees....
>
> Thanks,
> Ben Bullock
> Micron Technology
> Boise, ID
>
> -----Original Message-----
> From: Jolliff, Dale [mailto:xjolliff AT TI DOT COM]
> Sent: Friday, May 03, 2002 1:13 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Archive retention question
>
>
> I found this gem on the ADSM site:
>
> "Unlike backups, once a file is archived, its
> retention is set in stone (you can delete archive files however)."
>
>
> Scenario:
> Client creates a management class called "3_Month" and sets retention at 90
> days.
> Later they change their mind, and create another management class called
> "1_Month"
> and set it to 30 days.  All current archives go to "1_Month".
>
> They want to ditch as much of the "3_Month" as possible, without getting
> rid of anything newer than 30 days...
>
> Is there any way to accomplish this without deleting individual archives?
>
> Confidentiality Note: The information transmitted is intended only for the
> person or entity to whom or which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of this information by persons or entities other
> than the intended recipient is prohibited. If you receive this in error,
> please delete this material immediately.