ADSM-L

Re: [ADSM-L] disabling compression and/or deduplication for a client backing up against deduped/compressed directory-based storage pool

2018-04-05 11:48:23
Subject: Re: [ADSM-L] disabling compression and/or deduplication for a client backing up against deduped/compressed directory-based storage pool
From: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 5 Apr 2018 17:47:38 +0200
Hi,

With the directory containerpool you cannot, for as far as I know, disable
an attempt to deduplicate the data and if the data is able to deduplicate
it will be deduplicated.
You can, however, disable compression on the storagepool-level. If you
disable it on the containerpool client-side settings for deduplication will
have no effect on compression within the pool.

Are you using an IBM blueprint configuration for the Spectrum Protect
environment?

Regards,
   Stefan


On Tue, Apr 3, 2018 at 6:06 PM, PAC Brion Arnaud <Arnaud.Brion AT panalpina DOT 
com
> wrote:

> Hi All,
>
> Following to global client backup performance issues on some new TSM
> server, which I suspect to be related to the workload induced on TSM
> instance by deduplication/compression operations, I would like to do some
> testing with a client, selectively disabling compression or deduplication,
> possibly both of them on it.
>
> However, the TSM server has been configured to only make use of
> directory-based storage pools, which have been defined having deduplication
> and compression enabled.
>
> Thus my question : is there any mean to configure a client, so that its
> data  will not be compressed or deduplicated ?
>
> From my understanding, setting up "compression no" in the client option
> file will be of no use, as the server will still be compressing the data at
> storage pool level.
> Likewise, setting up "deduplication no" in the client option file will
> refrain the client to proceed to deduplication, but the server still will.
> The last remaining possibility  that I can think of, to disable
> deduplication, would be to make use of some "exclude.dedup" statement on
> client side, that would exclude anything subject to backup.
>
> What are your thoughts ? Am I condemned to define new storage pools not
> enabled for deduplication and or compression to do such testing, or is
> there some other mean ?
>
> Thanks a lot for appreciated feedback !
>
> Cheers.
>
> Arnaud
>
> ************************************************************
> ********************************************************************
> Backup and Recovery Systems Administrator
> Panalpina Management Ltd., Basle, Switzerland,
> CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
> Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
> Direct: +41 (61) 226 19 78
> e-mail: arnaud.brion AT panalpina DOT com<mailto:arnaud.brion AT panalpina 
> DOT com>
> This electronic message transmission contains information from Panalpina
> and is confidential or privileged.
> This information is intended only for the person (s) named above. If you
> are not the intended recipient, any disclosure, copying, distribution or
> use or any other action based on the contents of this
> information is strictly prohibited.
>
> If you receive this electronic transmission in error, please notify the
> sender by e-mail, telephone or fax at the numbers listed above. Thank you.
> ************************************************************
> ********************************************************************
>

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

ADSM.ORG Privacy and Data Security by KimLaw, PLLC