...@bkme.com
Please consider the environment before printing this Email
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jeff
Brunt
Sent: Tuesday, February 09, 2010 9:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM 6.1 dedup
I was reading some posts
I have heard that TSM dedup can deal with TSM client-compressed data, but I
have no first-hand experience, nor do I know if there are any tradeoffs. We
are in the same boat as you, and are thus looking forward to exploring this
further.
At 01:53 PM 2/9/2010, Jeff Brunt wrote:
>I was reading so
I was reading some posts earlier this month about using the data domain
appliance and read that they recommend not using client compression. I am
using TSM dedup and was wondering if that recommendation would still be true as
I have forced client compression on since all data is now going to di
Date: 04/06/2009 10:24 AM
Subject:[ADSM-L] TSM 6.1 dedup on SERVER devclass
Hi all,
I am already aware that TSM 6.1 dedup feature works when the data is stored
in a FILE devclass, and is "re-built" when the data goes to tape. But I
have a question: If the data is mig
Hi all,
I am already aware that TSM 6.1 dedup feature works when the data is stored in
a FILE devclass, and is "re-built" when the data goes to tape. But I have a
question: If the data is migrated from a FILE pool to a pool with a SERVER type
devclass, would dedup still be in effect