When you use the term "archive", do you mean the ADSM Archive operation? If so,
then your customer can safely specify a different management class without
affecting prior archives. The rebinding to the new management class only
applies to the ADSM Backup operation.

The "gotcha" you may be thinking of with ADSM archived files is this: If you
change the retention setting of a management class's archive copy group, then
all previously existing archive versions that are bound to that management
class will get the new retention.

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com


 ADSM-L AT VM.MARIST DOT EDU
 03/19/98 01:58 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet

To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: How to store certain file backup versions for a longer perio

Hi ADSM-ers!
I have a customer with the following requirements: He wants an incremental
backup taken every day. The databases on the client are archived (through the
database utilities) to ADSM daily. One time each month he wants to have the
archive version kept for a longer period than the standard archive retention.
Since this archive is from the same databases I cannot use different archive
management classes (the next archive would rebind the files to the standard
retention). How should I implement this?
Thank you very much for your reply in advance!
Kindest regards,
Eric van Loon