IvanWarren
Newcomer
- Joined
- Jun 19, 2009
- Messages
- 3
- Reaction score
- 0
- Points
- 0
Gentlemen,
First, this is more of theoretical question as I am pretty much toying around with TSM at this point (self education), so this is no emergency !
Ok, here is what I am trying to do.
I have a copy storage pool defined over a certain device class. Let's now assume I wish to change to a new device class (say like changing to a new library or going from server-server virt volumes to tape...)
My question is : Assuming I have now created my new copy storage pool, backed up my primary storage pools to it and eventually set my COPYSTG attributes for my primary storage pools to the new copy stg pool (if I'm using simultaneous write), is there a simple way of getting rid of the redundant/obsolete copy storage pool ?
The only way I've found to do that was to manually delete each and every single volume that were in the old copy storage pool with discarddata=yes. If I have a bunch (and I mean - when doing server-server vtapes, winding up with hundreds of volumes even on small installations can happen very quickly !), it sure could become quite tedious to do that !
I mean.. Migrating a primary storage pool from 1 lib to another is trivial.. but copy storage pools seem to be a bit more complicated to handle when say migrating to new hardware or changing to a new setup.
Thanks,
--Ivan
First, this is more of theoretical question as I am pretty much toying around with TSM at this point (self education), so this is no emergency !
Ok, here is what I am trying to do.
I have a copy storage pool defined over a certain device class. Let's now assume I wish to change to a new device class (say like changing to a new library or going from server-server virt volumes to tape...)
My question is : Assuming I have now created my new copy storage pool, backed up my primary storage pools to it and eventually set my COPYSTG attributes for my primary storage pools to the new copy stg pool (if I'm using simultaneous write), is there a simple way of getting rid of the redundant/obsolete copy storage pool ?
The only way I've found to do that was to manually delete each and every single volume that were in the old copy storage pool with discarddata=yes. If I have a bunch (and I mean - when doing server-server vtapes, winding up with hundreds of volumes even on small installations can happen very quickly !), it sure could become quite tedious to do that !
I mean.. Migrating a primary storage pool from 1 lib to another is trivial.. but copy storage pools seem to be a bit more complicated to handle when say migrating to new hardware or changing to a new setup.
Thanks,
--Ivan