> Updated the device class to refer to the second library? The pools would
> remain associated with the device class, the (new|moved) drives would be
> defined to the new library, and the tapes would be checked out of the old
> library and checked into the new one (with the device class change in
On 01/22/2014 05:36 PM, Remco Post wrote:
indeed, the trick is to change the primary pool, new device class, new
pool etc. The copy pool can remain unchanged. Now, you do make me doubt
about what we did 10 years ago when we got our second library. We moved
tapes, I'm sure of that.
Updated the
Op 22 jan. 2014, om 23:23 heeft Shawn DREW het
volgende geschreven:
> The fact that both pools use the same device class is the problem.
you're right.
> 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
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 al
Op 22 jan. 2014, om 17:52 heeft Lee, Gary 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 VMW
