1. On first backup after include/exclude list change the new bindings will
take effect.
- *All* old versions of the files will be rebound to new class.
- New class copygroup settings will mandate the expiration
2. Rebind to another class does not force backed up data move.
- All newly backed up data will respect the destination set in new
class backup copygroup
- All *existing* data will stay where it is. If you want this to be
changed explore usage of "move nodedata" and "move data" commands"
New destination primary pools may have different copypools (or no
copypools). TSM server will backup the data in each primary pool as you
have configured it. Therefore newly backed up data might go to different
copypool than old backups.
Zlatko Krastev
IT Consultant
Joni Moyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
22.05.2003 14:27
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: new management class
Hello everyone!
Quick question: I have created a new disk storage pool, sequential and
offsite storage pool for oracle logs, which were previously going to
another disk storage pool that is associated with the same domain. I was
wondering if when they go to use this new management class which goes to a
different disk pool, etc. will all current files be rebound to the new
management class? If so, how does that work when the tape pools (onsite
and offsite) are different? Or will it just bind all future archives to
this new managment class and storage hierarchy?
Thanks in advance!!!
Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338
