>>That is very interesting. I thought that TSM only did dedup at the backend storage pool. 6.1 back end only 6.2 client side too
>>Have you tried the source side dedupe? No, don't have a 6.2 to play with yet. And it requires the 6.1 dedup to be implemented first, i.e. data has to reside in a file-type deduplicated pool, which not everybody has space for. >>Any thoughts on this feature? Everything I've seen on it looks good to me... There is a free web class on June 9: http://bit.ly/b3RXLT W ----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Prather, Wanda Sent: Wednesday, May 26, 2010 2:22 PM To: [email protected] Subject: Re: [ADSM-L] Any way to avoid full backup of data relocated on TSM client file system?? Dedup at the source now includes TSM 6.2! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Schaub, Steve Sent: Wednesday, May 26, 2010 2:19 PM To: [email protected] Subject: Re: [ADSM-L] Any way to avoid full backup of data relocated on TSM client file system?? Any backup product would by definition have to backup "changes", even inane ones like these. However, one that dedupes at the source (e.g. Avamar, Syncsort) might have the advantage here, in sending less actual data during the backup. Steve Schaub Systems Engineer, Windows BlueCross BlueShield of Tennessee -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Michael Green Sent: Wednesday, May 26, 2010 1:45 PM To: [email protected] Subject: Re: [ADSM-L] Any way to avoid full backup of data relocated on TSM client file system?? I wondering if there is any other backup software that is designed and actually capable of handling such situations. I bet there is not. -- Warm regards, Michael Green ----------------------------------------------------- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
