The fact that both pools use the same device class is the problem. While you can change the library a device class points to, you can't change the device class a stgpool points to. You are changing from a DRM/vault flow to 2 online libraries. This will require a new backup stg if you want all of your copy pool data in the new location.
What I would do is: - rename both pools to something like tape_c1.old and tape_c2.old - Create new pools using the desired new device classes so that all new backup data moving forward works how you want it, - Maintain the old pools as you have in the past (using a vault, DRM and reclamation) You can slowly migrate data from tape_c1.old -> tape_c1 over time and slowly reclaim all the tapes in the old pools. You will have trouble reclaiming tapes from the tape_c2.old pool until all the data is moved (or work some collocation trickery and manually delete volumes that you know is in the new pools) Regards, Shawn ________________________________ Shawn Drew > -----Original Message----- > From: ADSM-L@VM.MARIST.EDU [mailto:ADSM-L@VM.MARIST.EDU] > Sent: Wednesday, January 22, 2014 11:53 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] moving to new copy storage pool > > We are upgrading our server from v5.5.4 to 6.2.5. At the same time, we > are changing platforms to redhat on x86 from suse under vm. > > I have tested the upgrade process, and it seems to work well. > In the current 5.5 server, the primary tape pool uses the same devclass as > the offsite copy pool. > I now will have access to an offsite library from the new upgraded server. > > Since a new library requires a new devclass, I assume this will also > require a new offsite pool. Is there a way to avoid a complete new "ba > stgpool" from having to be done? > At approximately 60 tB, I don't have time or tape cartridges to do this. > > I thought of reclaiming the old pool to the new pool for the first two or > three weeks, then starting to backup to the new pool, hoping to get tapes > back from the old to reuse. > > Any other ideas out there? 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.
