ADSM-L

Re: Management class Revamp

2005-03-08 09:53:29
Subject: Re: Management class Revamp
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 8 Mar 2005 09:53:02 -0500
On Mar 7, 2005, at 10:44 AM, Meadows, Andrew wrote:

...The old domain will not be deleted just not actively used, I am
beginning to think that if I keep the old domain around the data will
keep the management class association that it was backed up with.

Andrew - Thanks for the further details on the steps you took.

Backup data will retain its original management class unless it is
backed up again, in which case it can be "rebound" to a new mgmt class.
The Admin Guide topic "Rebinding Files to Management Classes" describes
the other limited cases where the rebinding of Backup files can occur.

In pursuing your issue, be mindful of the great difference between
Backup and Archive data: Backup instances of files are treated as
multiple versions of the same file, where the newest version is deemed
the most viable, the older ones being regarded as disposable with age.
Archive instances of files are each deemed unique unto themselves, not
as different versions of the same file. The nature of Backup files
allows them to be rebound; but Archive files are not rebound - they
remain associated with their original management class. Only if the
archive copygroup definition disappears for the Archive files does TSM
get desperate and find another copygroup/managment class to assign them
to. As part of your Archive file tests, you have been doing a backup;
but don't let that influence your thinking, as what happens in a backup
has nothing to do with your Archive data.

Your test may be more illuminating if you had different archive
copygroup retention values for the same management class name, in the
multiple domains. (But, whereas the management class name is
15YRARCHIVE, one thinks it should remains as-is.)  Also, consider
performing your archive queries from the client, which should report an
expiration in addition to the archive date.

Multiple Domains can indeed be a confusing area...to the extent that
many customers avoid using more than one policy Domain.

   Richard Sims

<Prev in Thread] Current Thread [Next in Thread>