WOW! Thanks Andy -- That new feature slipped by me, I"m turning it on now!
-----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 22, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: I forgot to mention: Starting with the 4.2 client, you can now use include.compression and exclude.compression client options. For example: exclude.compression *:\...\*.zip will prevent any *.zip file from being compressed, even if COMPRESSION YES and COMPRESSALWAYS are in effect. However, the 4.2 client is not supported with the 3.1 server. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. ----- Forwarded by Andrew Raibeck/Tucson/IBM on 01/22/2002 07:10 ----- Andrew Raibeck 01/22/2002 07:04 To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> cc: From: Andrew Raibeck/Tucson/IBM@IBMUS Subject: Re: ADSM and TSM do not "know" that a file is compressed, per se. However, it does detect if the file is growing during compression (which is most likely because the file is already compressed). If the file grows during compression and COMPRESSALWAYS YES (the default) is in effect, then it will keep compressing the file anyway. This is causing the negative compression that you are seeing. If COMPRESSALWAYS NO is in effect and the file grows during compression, then all files in the current transaction will be resent to the server, but the file that grew wll be sent uncompressed. The trade-off is that in resending all the other files in the current transaction, you may see a performance degradation in over-all elapsed time, especially if there are lots of files that grow during compression. Regard, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Wolfgang Rest <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/22/2002 06:04 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: 01/21/2002 21:41:55 ANE4952I (Session: 196, Node: APOLLO) Total number of objects inspected: 129,216 01/21/2002 21:41:55 ANE4954I (Session: 196, Node: APOLLO) Total number of objects backed up: 43,830 01/21/2002 21:41:55 ANE4958I (Session: 196, Node: APOLLO) Total number of objects updated: 0 01/21/2002 21:41:55 ANE4960I (Session: 196, Node: APOLLO) Total number of objects rebound: 0 01/21/2002 21:41:55 ANE4957I (Session: 196, Node: APOLLO) Total number of objects deleted: 0 01/21/2002 21:41:55 ANE4959I (Session: 196, Node: APOLLO) Total number of objects failed: 4 01/21/2002 21:41:55 ANE4961I (Session: 196, Node: APOLLO) Total number of bytes transferred: 5.11 GB 01/21/2002 21:41:55 ANE4963I (Session: 196, Node: APOLLO) Data transfer time: 911.71 sec 01/21/2002 21:41:55 ANE4966I (Session: 196, Node: APOLLO) Network data transfer rate: 5,886.47 KB/sec 01/21/2002 21:41:55 ANE4967I (Session: 196, Node: APOLLO) Aggregate data transfer rate: 992.76 KB/sec 01/21/2002 21:41:55 ANE4968I (Session: 196, Node: APOLLO) Objects compressed by: -16% 01/21/2002 21:41:55 ANE4964I (Session: 196, Node: APOLLO) Elapsed processing time: 01:30:05 Objects compressed by: -16% ?!?!?! How can this be? There are many .zip Files on this Server.. but i thought ADSM will check if a File is already compressed and dont compress it again. I am running on Client side 3.1.0.8 and Server 3.1.2.90 best regards
