EXCLUDE.COMPRESSION excludes files from compression when COMPRESSION YES is in effect. Your client option set forced COMPRESSION YES to be in effect, but otherwise does not impact EXCLUDE.COMPRESSION.
In a way, I'm not sure there is much point in forcing compression because you could always override it with "EXCLUDE.COMPRESSION *". :-) Glad it's figured out. 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/i...@ibmus Internet e-mail: [email protected] 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" <[email protected]> wrote on 03/10/2009 02:28:57 PM: > [image removed] > > Re: How do I override compression setting? > > Schneider, John > > to: > > ADSM-L > > 03/10/2009 02:31 PM > > Sent by: > > "ADSM: Dist Stor Manager" <[email protected]> > > Please respond to "ADSM: Dist Stor Manager" > > Andy, > There is a client options set in effect, and it did have > compression=yes, with the "force" option, which probably overrides > everything. > But even with that in effect, when I used the > "exclude.compression /mnt/mksysb/.../*" line, it skipped compressing the > files in that filesystem, which is what I wanted. > Ok, so now I know why the client was behaving that way; the > client options set was overriding the schedule options. > > > Best Regards, > > John D. Schneider > Phone: 314-364-3150 > Cell: 314-750-8721 > Email: [email protected] > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Andrew Raibeck > Sent: Tuesday, March 10, 2009 1:19 PM > To: [email protected] > Subject: Re: [ADSM-L] How do I override compression setting? > > Make sure you don't have a client option set forcing compression. > > I checked the 5.4.2.0 client on Linux x86, your scenario (compression > yes > in dsm.sys, compression no in sched definition) works fine without a > client > option set. > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus > Internet e-mail: [email protected] > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan > ager.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" <[email protected]> wrote on 03/10/2009 > 01:51:25 PM: > > > [image removed] > > > > Re: How do I override compression setting? > > > > Schneider, John > > > > to: > > > > ADSM-L > > > > 03/10/2009 01:54 PM > > > > Sent by: > > > > "ADSM: Dist Stor Manager" <[email protected]> > > > > Please respond to "ADSM: Dist Stor Manager" > > > > Well, I guess I am being tripped up my engineer's mind. I want the > > product to work consistently, not arbitrarily. And to work according > to > > the manual. In the Unix client manual in the section on processing > > options it says: > > > > * Most options that you enter on the command line override the value > set > > in the preferences file. However, when you use the domain option with > > the incremental command, it adds to the domain specified in your > client > > options file rather than overriding the current value. > > > > This implies that "-compression=no" should override "compression yes" > in > > the dsm.sys file. In fact, isn't that kind of the point of allowing > > line-mode options, to override what is in the dsm.sys file? > > > > Best Regards, > > > > John D. Schneider > > Phone: 314-364-3150 > > Cell: 314-750-8721 > > Email: [email protected] > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of > > Kelly Lipp > > Sent: Tuesday, March 10, 2009 12:33 PM > > To: [email protected] > > Subject: Re: [ADSM-L] How do I override compression setting? > > > > That is the question: does the compress=no on the command line > override > > the compress yes in the dsm.sys? Apparently not. The docs state, > > though, that the exclude.compression will override the dsm.sys. Might > > be you only option. > > > > Kelly Lipp > > CTO > > STORServer, Inc. > > 485-B Elkton Drive > > Colorado Springs, CO 80907 > > 719-266-8777 x7105 > > www.storserver.com > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of > > Schneider, John > > Sent: Tuesday, March 10, 2009 11:29 AM > > To: [email protected] > > Subject: Re: [ADSM-L] How do I override compression setting? > > > > Kelly, > > 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? > > > > > > Best Regards, > > > > John D. Schneider > > Phone: 314-364-3150 > > Cell: 314-750-8721 > > Email: [email protected] > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of > > Kelly Lipp > > Sent: Tuesday, March 10, 2009 12:07 PM > > To: [email protected] > > Subject: Re: [ADSM-L] How do I override compression setting? > > > > How about exclude.compression on that filespace? > > > > exclude.compression > > Excludes files from compression processing if the compression option > is > > set to yes. This option applies to backups and archives. > > > > Kelly Lipp > > CTO > > STORServer, Inc. > > 485-B Elkton Drive > > Colorado Springs, CO 80907 > > 719-266-8777 x7105 > > www.storserver.com > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of > > Schneider, John > > Sent: Tuesday, March 10, 2009 10:11 AM > > To: [email protected] > > Subject: [ADSM-L] How do I override compression setting? > > > > Greetings, > > I have a specific NFS filesystem on a TSM AIX client that I need > to > > backup without compression because the files are very large and > already > > compressed, so it is pointless to compress them. But compression is > > "yes" in the dsm.sys file because I want to compress the other > > filesystems. > > The TSM client definition for compression is set to "client", so > > presumably the client can choose to either compress or not. Here is > the > > dsmsched.log of the schedule. Note that I turn off compression in the > > schedule: > > > > 03/10/09 10:00:38 > > ------------------------------------------------------------ > > 03/10/09 10:00:38 Schedule Name: @1002 > > 03/10/09 10:00:38 Action: Incremental > > 03/10/09 10:00:38 Objects: /mnt/mksysb > > 03/10/09 10:00:38 Options: -subdir=y -compression=n > > 03/10/09 10:00:38 Server Window Start: 09:57:56 on 03/10/09 > > 03/10/09 10:00:38 > > ------------------------------------------------------------ > > 03/10/09 10:00:38 > > Executing scheduled command now. > > 03/10/09 10:00:38 --- SCHEDULEREC OBJECT BEGIN @1002 03/10/09 > > 09:57:56 > > 03/10/09 10:00:38 Incremental backup of volume '/mnt/mksysb' > > 03/10/09 10:00:45 ANS1898I ***** Processed 500 files ***** > > 03/10/09 10:00:50 ANS1898I ***** Processed 1,000 files ***** > > > > .... Buncha lines skipped... > > > > 03/10/09 10:02:12 ANS1898I ***** Processed 5,500 files ***** > > 03/10/09 10:07:02 Normal File--> 2,489,241,600 /mnt/mksysb/osba > > ckup/eeyore/eeyore-03082009 ANS1360I Compressed Data Grew > > 03/10/09 10:13:05 Normal File--> 2,489,241,600 /mnt/mksysb/osba > > ckup/eeyore/eeyore-03082009 [Sent] > > 03/10/09 10:13:05 Successful incremental backup of '/mnt/mksysb' > > > > 03/10/09 10:13:05 --- SCHEDULEREC STATUS BEGIN > > 03/10/09 10:13:05 Total number of objects inspected: 5,624 > > 03/10/09 10:13:05 Total number of objects backed up: 1 > > 03/10/09 10:13:05 Total number of objects updated: 0 > > 03/10/09 10:13:05 Total number of objects rebound: 0 > > 03/10/09 10:13:05 Total number of objects deleted: 0 > > 03/10/09 10:13:05 Total number of objects expired: 0 > > 03/10/09 10:13:05 Total number of objects failed: 0 > > 03/10/09 10:13:05 Total number of bytes transferred: 3.93 GB > > 03/10/09 10:13:05 Data transfer time: 8.86 sec > > > > Why am I still getting "ANS1360I Compressed Data Grew" when the > options > > for the schedule are "-compression=n"? It shouldn't be trying to > > compress, should it? > > > > We are running TSM client 5.4.2.0, and TSM server 5.4.3.0 on AIX, in > > case that matters. > > > > Best Regards, > > > > John D. Schneider > > Lead Systems Administrator - Storage > > Sisters of Mercy Health Systems > > 3637 South Geyer Road > > St. Louis, MO 63127 > > Phone: 314-364-3150 > > Cell: 314-750-8721 > > Email: [email protected] > > > > > > This e-mail contains information which (a) may be PROPRIETARY IN > NATURE > > OR > > OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only > for > > the > > use of the addressee(s) named above. If you are not the addressee, or > > the > > person responsible for delivering this to the addressee(s), you are > > notified > > that reading, copying or distributing this e-mail is prohibited. If > you > > have > > received this e-mail in error, please contact the sender immediately. > > This e-mail contains information which (a) may be PROPRIETARY IN > NATURE > > OR > > OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only > for > > the > > use of the addressee(s) named above. If you are not the addressee, or > > the > > person responsible for delivering this to the addressee(s), you are > > notified > > that reading, copying or distributing this e-mail is prohibited. If > you > > have > > received this e-mail in error, please contact the sender immediately. > > This e-mail contains information which (a) may be PROPRIETARY IN > NATURE > OR > > OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only > for > the > > use of the addressee(s) named above. If you are not the addressee, or > the > > person responsible for delivering this to the addressee(s), you are > notified > > that reading, copying or distributing this e-mail is prohibited. If > you > have > > received this e-mail in error, please contact the sender immediately. > This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR > OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the > use of the addressee(s) named above. If you are not the addressee, or the > person responsible for delivering this to the addressee(s), you are notified > that reading, copying or distributing this e-mail is prohibited. If you have > received this e-mail in error, please contact the sender immediately.
