You can change the library a particular devclass is pointing to, but this would only work if your primary and offsite pool use different device classes. If they are using the same device class, you have to recreate a new copypool with a different device/class and pool.
The volume is tied to the pool and can not be moved out of that pool. The pool is stuck to a device class and can't be changed to a different devclass. What I would do in this situation is to rename your primary and copy pools to something like tape_c1.old and tape_c2.old , sync and "freeze" them. I.E. have no new data sent to them. Then direct new data to new pools "tape_c1 -> tape_c2" using the new device classes. Then slowly, over time, migrate tape_c1.old -> tape_c1. Eventually, all the tapes in the old pools will expire and you'll be on the new system with tapes backed up to the new offsite pool. This way, you won't be exposed for the time it takes to create the new copypool at the new site. Hopefully that ramble made sense. Regards, Shawn ________________________________________________ Shawn Drew Internet [email protected] Sent by: [email protected] 12/08/2011 09:57 AM Please respond to [email protected] To ADSM-L cc Subject [ADSM-L] Thoughts on changing an offsite storage pool We are finally able to move into electronic vaulting. I will now have another 3494 to put into our offsite location. My problem is how to get the current offsite data into the new library most expediciously. If I understand correctly, a device class is associated with a particular library; therefore, a new class must be created for the new offsite library. Can I check the existing offsite volumes into the new library thus effectively moving them from their original devclass to the new one, or must I create an entirely new offsite pool and then move data from the old offsite pool into the new? All cartridges are 3592j and drives are all ts1120. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
