Op 22 jan. 2014, om 17:52 heeft Lee, Gary <[email protected]> het volgende geschreven:
> 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. > vm (mainframe) or vmware? And if VMWare, is tape (physical or virtual) supported on VMWare? Last time I checked it wasn't. > 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. > you can just check the copypool tapes out from the old lib and in in the new lib, assuming the device type is compatible/identical. A tape volume is not bound to a device class, only to a pool and a device type (not device class!). (BTDTGTTS) > 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. > nope, you can't set a reclaim stg on a copypool. > Any other ideas out there? -- Met vriendelijke groeten/Kind Regards, Remco Post [email protected] +31 6 248 21 622
