TSM 7.1 migration

[chimod]

Hi all,
I'm using disk storage pool, there are a copy pool and migration proccess defined for that pool.
Migration occurs prior to copy, but the copy pool contains all the migrated data.
Is that a proper behaviour of backup storage pool?

 

[Trident]

Hi,
The purpose of the copy pool is to hold a copy of all the data. Send output of q stg, and we can tell you more.

 

[marclant]

Is that a proper behaviour of backup storage pool?

Yes

I'm using disk storage pool, there are a copy pool and migration proccess defined for that pool.
Migration occurs prior to copy, but the copy pool contains all the migrated data.

If data is migrated from disk pool to a physical tape pool (not VTL), it would be more effiient to do the following order:
- backup stgpool from disk to copy
- backup stgpool from tape to copy
- database backup
- migration
- exipration
- relamation

Some even wait at the last minute to perform the migration in the event a client needs to do a restore from previous day the next morning, the data will be on disk and be a quicker restore.

If you do your backup stgpool from disk to copy (tape), it's quicker because it's reading from disk instead of tape. You can also use more processes because you only need one tape drive to write, none to read.

The 2nd backup stgpool from tape to copy is to catch anything that may have been migrated during the client backups if the HiMig was exceeded.