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
You can do this in 2 steps, export the filespace and reimport under the
different nodename. You will have to do some renames.
rename n nodeb nodeb-temp
rename n nodeA nodeB
export n nodeb
rename n nodeB nodeA
remame n nodeb-temp nodeb
import n nodeb
Regards,
Shawn
___
Op 22 jan. 2014, om 20:12 heeft Zoltan Forray het volgende
geschreven:
> Is this possible with the newer TSM server levels? I Google'd and it is a
> old question/desire (move the filespaces from NODEA to NODEB so NODEB
> doesn't have to re-backup everything on things like shared/movable
> NAS/C
Is this possible with the newer TSM server levels? I Google'd and it is a
old question/desire (move the filespaces from NODEA to NODEB so NODEB
doesn't have to re-backup everything on things like shared/movable
NAS/CIFS/NFS/SAN mountpoints)
I know you can rename a filespace but it has always been
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
I'm sticking with 6.3.4.3 for the server. I haven't applied the .300
fixpack yet, but will do so soon. I'm waiting for 7.1.1 because of this
APAR:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC97618
It says in there that that APAR is not fixed in 7.1.0 (only at 7.1.1).
I have worked a bi
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 no
Hi,
keep in mind that with a no-query restore, you can also run a multi-session
restore.
You would need to increase your "resourceutilization" client option from
the default
value of 2. You would then need to adjust the "Maximum Mount Points
Allowed"
value of the node with the "update node maxnumm
With the "no query restore" you are pushing the workload onto the TSM
server.
The client will still have to transmit the details on all the 7.5M files
up to the TSM server.
And I believe a simple "restore -replace=no -subdir=yes X:\*" will trigger
a ~no query restore~ by default.
OK, interesting, I
Just brew a pot of coffee...
I tell folks, just because you "can" do something doesn't mean its a good
idea "to" do something and that much data, that many files in a single
mount point is a "poor choice" (but I deal with it almost daily so you're
not alone).
I haven't been dealing with the Win20
12 matches
Mail list logo
