ADSM-L

Re: [ADSM-L] TSM/VE and Containers

2016-03-16 11:23:53
Subject: Re: [ADSM-L] TSM/VE and Containers
From: David Ehresman <david.ehresman AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 16 Mar 2016 15:19:30 +0000
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 AT VM.MARIST DOT EDU] On Behalf Of 
Koen Willems
Sent: Wednesday, March 16, 2016 10:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM/VE and Containers

Hi David,
I store vmctl and backup data in separate container storage pools with no 
dedupe on my vmctl pool this works like a charm.
Regards,
Koen

-----Oorspronkelijk bericht-----
Van: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Namens David 
Ehresman
Verzonden: Wednesday, March 16, 2016 1:38 PM
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: [ADSM-L] TSM/VE and Containers

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 to a remote location, can TSM/VE be run in the remote location 
accessing the replicated data/metadata?

David

<Prev in Thread] Current Thread [Next in Thread>