Thanks. I see that this was supposed to be corrected in 7.1.3 which is the
version we are running. I hope IBM fixes this. Can't really say that
setting all our copy volumes offsite for every restore is an acceptable
workaround. Us who administer the servers have no control of who might
initiate a
How does TSM/VE fit into a containerized world? I assume I can write the data
to a container. What about the vmctl metadata; can it be stored in a container
or does it have to stay in a file based storagepool?
If both the data and the metadata are in a container and that data is
replicated
Thanks Michael,
Here is the output from the tsmdlst command. The tape library is listed as
lb2.1.0.3 below.
Computer Name: TSMANL
OS Version: 6.1
OS Build #: 7601
TSM Device Driver: TSMScsi - Not Running
3 HBAs were detected.
ManufacturerModel Driver
Koen,
Why different containers? Why nodupe on vmctl pool. How do you set a the
vmctl pool to nodedup? I thought the container software decided whether to
dedup or not?
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Koen
Willems
