You can identify which volumes contain that node's data on old copypool.
Then delete those volumes which would remove the data for the node in
question along with other nodes' data. On the end re-backup all affected
primary storage pools to recover the data for collateral damage nodes.
Works on any version but may consume a lot of time on non-collocated
copypools.
Zlatko Krastev
IT Consultant
Joshua Bassi <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.06.2003 02:00
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
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, 1 in the new copy stg pool, and 1 in the original copy stg pool).
My questions is, how is it possible to remove the copy in the original
copy stg pool since we now have it in a new copy stg pool. The move
data command will not work because you can only move data within a copy
stg pool and not into a new pool.
The only thing I was able to think of was to blow the data away and
re-back it up to the new primary stg pool. Any help would be
appreciated.
--
Joshua S. Bassi
Tivoli Certified Consultant -ADSM/TSM
eServer Systems Expert -pSeries HACMP
IBM Certified - AIX 4/5L, SAN, Shark
Cell (831) 595-3962
