Re: [ADSM-L] How do I override compression setting?
2009-03-10 14:39:28
> You can verify that overriding is working like:
> dsmc q opt -compression=no | grep -i compress
Fun fact #273: Another way to do this that does not require the grep:
dsmc q opt comp* -compression=no
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/10/2009
02:25:01 PM:
> [image removed]
>
> Re: How do I override compression setting?
>
> Richard Sims
>
> to:
>
> ADSM-L
>
> 03/10/2009 02:28 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> On Mar 10, 2009, at 1:29 PM, Schneider, John wrote:
>
> > It is good to know an option like that exists, thanks. But that
> > is not really my question. What is wrong with what I am doing? I
> > don't
> > see any mistakes in my configuration. When I create a schedule and put
> > "-compression=n" in the options for the schedule, the TSM client
> > should
> > turn compression off for that schedule, right? I shouldn't have to
> > put
> > a special exclude in, should I?
>
> Specifying -COMPRESSIon=No is documented as (temporarily) overriding
> "COMPRESSIon Yes" in the options file, and will do so if
> the Node definition does not force compression, and there are no TSM
> defects or odd release changes in play.
>
> You can verify that overriding is working like:
> dsmc q opt -compression=no | grep -i compress
>
> Richard Sims
|
|
|