Re: Archival with different retentions?
2001-09-27 13:52:00
Subject: |
Re: Archival with different retentions? |
From: |
Jeff Bach <jdbach AT WAL-MART DOT COM> |
Date: |
Thu, 27 Sep 2001 12:48:47 -0500 |
What is a verification process that can be used to make sure archived files
are not going away?
How many times are directories archived?
The information contained in the emails is outstanding. What else is going
to "bite us"?
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.
WAL-MART CONFIDENTIAL
-----Original Message-----
From: Richard Sims [SMTP:rbs AT BU DOT EDU]
Sent: Thursday, September 06, 2001 10:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Archival with different retentions?
>This sounds like a good solution. I was under the belief that when
I did
>something like this that the archival process would start rebinding
>previously archivals and therefore change the retention. But I
guess that
>is not true.
Matt - From my notes at http://people.bu.edu/rbs/ADSM.QuickFacts :
Archived files, rebinding does not From the TSM Admin. manual,
chapter on
occur Implementing Policies for
Client Data,
topic How Files and
Directories Are
Associated with a Management
Class:
"Archive copies are never
rebound
because each archive
operation creates
a different archive copy.
Archive copies
remain bound to the
management class
name specified when the user
archived
them." (Reiterated in the
client B/A
manual, under "Binding and
Rebinding
Management Classes to
Files".)
Beware, however, that
changing the
retention setting of a
management
class's archive copy group
will cause
all archive versions bound
to that
management class to conform
to the new
retention.
Note that you can use an
ARCHmc to
specify an alternate
management class
for the archive operation.
Richard Sims, BU
**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed. If you have received this email
in error destroy it immediately.
**********************************************************************
|
|
|