Shawn, I was the presenter for that STE but I did not cover this as part of the presentation. Let me find the answer for you and I will reply back to the listserv.
Dave Canan IBM TSM Advanced Technical Skills Ddcanan at us.ibm.com -----Original Message----- From: Bill Boyer <bjdbo...@verizon.net> Date: Fri, 28 May 2010 23:39:37 To: <ADSM-L@VM.MARIST.EDU> Subject: Re: [ADSM-L] TSM 6.2 Deduplication Question Might want to take a look at this webcast from yesterday: http://www-01.ibm.com/software/sysmgmt/products/support/TE/techex_G856816E23 063W02.html Implementation and Use of TSM Client/Server Data Deduplication with TSM 6.2 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Shawn Drew Sent: Friday, May 28, 2010 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM 6.2 Deduplication Question I'm reviewing the features of 6.2 and trying to decide if its worth the new-version-risk for one of our smaller branches. We are a 5.5 shop, so I'm a little behind on the details of the new features. The manual says that deduplication is available only on storage pools using a File device class. (many times!) However, I noticed this other entry under Virtual Volumes: When you copy or move data from a deduplicated storage pool to a non-deduplicated storage pool that uses virtual volumes, the data is reconstructed. When you copy or move data to a "deduplicated storage pool that uses virtual volumes" the data is deduplicated. http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=/com.i bm.itsm.srv.doc/t_network_virtualvol.html From that, I am inferring you can use a device class of "server" as well. This would be a huge for us if this were true. Can anyone confirm or deny this? Is this just a documentation hiccup? Regards, Shawn ________________________________________________ Shawn Drew This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.