The incremental backups destination pool is defined in the copygroup. In 
the management class you specify where HSM files will go. If you want to 
change destionation of backups you should modify backup copygroup (archive 
copygroup does not change automatically on backup copygroup change). HSM 
migration destination will change. The HSM files stored before the 
management class change is kept in old storage pool. Files migrated after 
the change will go to new storage pool.
If you want to decommision old pool you can set the new pool as next to the 
old and lower HIGHMIGration threshold to 0. Migration will start and data 
from all volumes will be moved to the new storage pool. 
If the pools are defined using same device class you have to watch about 
volume reuse delay. Emptied volumes will go in status of "Pending" and new 
volumes will be grabbed from scratch tapes. You may easily run out of 
scratch tapes.
If reuse delay is set to 0 they will be immediately reused. But your 
database backups will point to old volume contents (old storage pool data). 
If something happens with the TSM server during that time you can lose 
data!

Zlatko Krastev
IT Consultant





Pétur Eyþórsson <Peddi AT ITN DOT IS> on 25.10.2001 11:40:47
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc: 

Subject:        Re: Update Management Class

Hi Kelvin

TSM does not automaticly move data between STGPools.
The Incremental backups will conntinue as nothing has happend, and if you 
do
a restore you must restore from both the storage pools.

If you are planing to only use one of the storage pools you must manualy
move the data between the storage pools.



   Kvedja/Regards
   Petur Eythorsson
   Taeknimadur/Technician
   IBM Certified Specialist - AIX
   Tivoli Storage Manager Certified Professional
   Microsoft Certified System Engineer

     Nyherji Hf            Simi TEL: +354-569-7700
     Borgartun 37       105 Iceland
     URL:                    http://www.nyherji.is