:
Subject:Move from Primary Pool Doesn't Remove from Copy Pool
All,
My colleague issued a move data command from a primary stg pool to a new
primary stg pool. He then backed up the new stg pool. After this was
done, there were actually 3 copies of the data (1 in the new primary stg
pool
All,
My colleague issued a move data command from a primary stg pool to a new
primary stg pool. He then backed up the new stg pool. After this was
done, there were actually 3 copies of the data (1 in the new primary stg
pool, 1 in the new copy stg pool, and 1 in the original copy stg pool).
My
After giving it some thought, I figure you have two choices.
1. If your OLD Copypool is sequential then you could sort by the oldest written date and move the data from each cartridge to the NEW Copypool. That way, data that should be expired, would be once it was with the rest of the copypool
Once you are sure the data has all been copied to a new copy storage
pool, why not just delete the volumes in the copy storage pool you want
to get rid of? This shouldn't do anything to your primary pool, or your
new copy pool.
Curtis Stewart
Shannon Bach wrote:
After giving it some thought, I
from Primary Pool Doesn't Remove from Copy Pool
Once you are sure the data has all been copied to a new copy storage
pool, why not just delete the volumes in the copy storage pool you want
to get rid of? This shouldn't do anything to your primary pool, or your
new copy pool.
Curtis Stewart
