I think you will save space in the both primary and copy pools because of compression, but de-duplication rate in primary pools will be reduced because of compression. In my opinion, in most of the case compression+deduplication is better than just deduplication, if you are ready to ignore increase in backup time and more heavy load on clients during backups because of compression.
Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@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 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 disk, and running dedup as well. Jeffrey S. Brunt Corporate IT Operations Chief Information Office 902-424-0885 Pplease consider the environment before printing this e-mail. Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
