Re: Changing Migration Destination target pool
Rats, just when I thought I got a question right.... :-)
How about this?
When you change the setting of where the data goes to, it will
only impact the backup of any ~new~ data. The old data that was already
backed up to that storagepool will remain in that old pool, only new
data will go to the newly defined storage pool. Do a "q occ" on the node
and see if you have ~any~ data from that client in the new pool.
If I'm on the right track.... Then if you want to move
previously backed up data on a host to the new storage pool, you can use
the " move nodedata" command to get it to transfer over...
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Thursday, April 29, 2004 2:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Changing Migration Destination target pool
I am new to TSM and did not phrase my post quite right... The Copy
Destination was changed in the Copy Group, then the policy set was
Validated and then Activated.
received message: Policy set STANDARD activated in policy domain
It now looks like this:
Backup Copy Groups : STANDARD ACTIVE ARCHIVE14-MC STANDARD Policy
Domain NameSTANDARDPolicy Set NameACTIVEMgmt Class NameARCHIVE14-MCCopy
Group NameSTANDARDVersions Data Exists2Versions Data Deleted1Retain
Extra Versions14Retain Only Version60Copy ModeMODIFIEDCopy
SerializationSHRSTATICCopy Frequency0Copy DestinationCLEANUPPOOLLast
Update Date/Time2004-04-29 10:38:45.000000Last Update by
But the backups still go to BACKUPPOOL which was the former setting, and
not to CLEANUPPOOL.
Migration destination is only for HSM managed files.
If you are hoping to change the location of where the backup or the
archive data goes, you need to change the destination on the copygroup.
If you are using the web GUI, drill down into the management class to
the backup and archive copygroups and then make the changes there.
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs