Re: Deduplication/replication options

2013-07-26 Thread Paul Zarnowski
> > Bill Colwell >> > Draper Lab >> > >> > -----Original Message- >> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >> > Gee, Norman >> > Sent: Wednesday, July 24, 2013 11:29 AM >> > To: ADS

Re: Deduplication/replication options

2013-07-26 Thread Stefan Folkerts
wg21500482 > > > > > > Thanks, > > > > > > Bill Colwell > > > Draper Lab > > > > > > -Original Message----- > > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of > > > Gee, Norman >

Re: Deduplication/replication options

2013-07-26 Thread Nick Laflamme
On Jul 26, 2013, at 5:21 AM, Steven Langdale wrote: > Hello Stefan > > Have you got cases of this? I ask because I have been specifically told by > our rep that any dedupe saving for capacity licensing is TSM dedupe only, > regarless of the backend storage. During our last TSM license renewal

Re: Deduplication/replication options

2013-07-26 Thread Steven Langdale
; Bill Colwell > > Draper Lab > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > > Gee, Norman > > Sent: Wednesday, July 24, 2013 11:29 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: Deduplicat

Re: Deduplication/replication options

2013-07-26 Thread Stefan Folkerts
ginal Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Gee, Norman > Sent: Wednesday, July 24, 2013 11:29 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Deduplication/replication options > > This why IBM is pushing their VTL solution. I

Re: Deduplication/replication options

2013-07-24 Thread Colwell, William F.
Bill Colwell Draper Lab -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Gee, Norman Sent: Wednesday, July 24, 2013 11:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Deduplication/replication options This why IBM is pushing their VTL solution. IBM will

Re: Deduplication/replication options

2013-07-24 Thread Gee, Norman
, 2013 11:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Deduplication/replication options Hi Sergio! Another thing to take into consideration: if you have switched from PVU licensing to sub-capacity licensing in the past: TSM sub-capacity licensing is based on the amount of data stored in your primary

Re: Deduplication/replication options

2013-07-24 Thread Allen S. Rout
On 07/23/2013 06:30 PM, Nick Laflamme wrote: > I'm surprised by Allen's comments, given the context of the list. > > TSM doesn't support BOOST. It doesn't support at the server level, and it > doesn't support for a client writing directly to a DataDomain DDR. Duh, yes, good point. Context: We mo

Re: Deduplication/replication options

2013-07-24 Thread Loon, EJ van - SPLXM
@VM.MARIST.EDU] On Behalf Of Sergio O. Fuentes Sent: dinsdag 23 juli 2013 19:20 To: ADSM-L@VM.MARIST.EDU Subject: Deduplication/replication options Hello all, We're currently faced with a decision go with a dedupe storage array or with TSM dedupe for our backup storage targets. There are some very cri

Re: Deduplication/replication options

2013-07-23 Thread Sergio O. Fuentes
Thanks, guys, for your input. Nick, your comment is relevant to us. We're not used to by-passing TSM for any storage management task regarding backups. We use very little storage-based replication in our environment as it is, and introducing array-based replication adds a wrinkle to managing our

Re: Deduplication/replication options

2013-07-23 Thread Nick Laflamme
I'm surprised by Allen's comments, given the context of the list. TSM doesn't support BOOST. It doesn't support at the server level, and it doesn't support for a client writing directly to a DataDomain DDR. This may be obvious to everyone, but I fear for the people who are TSM-centric and haven't

Re: Deduplication/replication options

2013-07-23 Thread Huebner, Andy
with serial number changes. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sergio O. Fuentes Sent: Tuesday, July 23, 2013 12:20 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Deduplication/replication options Hello all, We're

Re: Deduplication/replication options

2013-07-23 Thread Vandeventer, Harold [BS]
anager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sergio O. Fuentes Sent: Tuesday, July 23, 2013 12:20 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Deduplication/replication options Hello all, We're currently faced with a decision go with a dedupe storage array or with TSM dedupe for our

Re: Deduplication/replication options

2013-07-23 Thread Allen S. Rout
On 07/23/2013 01:19 PM, Sergio O. Fuentes wrote: > > We're currently faced with a decision go with a dedupe storage array > or with TSM dedupe for our backup storage targets. There are some > very critical pros and cons going with one or the other. For > example, TSM dedupe will reduce overall ne

Re: Deduplication/replication options

2013-07-23 Thread Arbogast, Warren K
Hi Sergio, There are many people more knowledgeable than I am on this topic, and I hope they contribute to this interesting question. My two cents would be to remember that the TSM database doesn't know about an array replication, so you'll have to deal with that issue if you have a massive reco

Deduplication/replication options

2013-07-23 Thread Sergio O. Fuentes
Hello all, We're currently faced with a decision go with a dedupe storage array or with TSM dedupe for our backup storage targets. There are some very critical pros and cons going with one or the other. For example, TSM dedupe will reduce overall network throughput both for backups and replic