stan wrote:
> On 03 19, 2010, at 9:52 AM, tbirkenbach wrote:
> 
> I do not think there is a one size fits all answer to your question. It 
> depends on your employer's requirements and budget. For us, de-dup is far 
> more important than BMR, although BMR would be nice. 
> 
> <snippage>
> 
> 


Completely agree with Stan.  Another factor you might consider along with any 
RTO commitments is that dedupe gives you capacity planning flexibility  to an 
extent.  It's certainly not an end-all, be-all solution, but since we've 
deployed Avamar, my blood pressure doesn't spike quite like it used to when my 
boss casually mentions that there are going to be another 27 virtual machines 
deployed next week.

In our case, server virtualization has alleviated some of the BMR needs.  There 
are lots of options for BMR protection for VMs that aren't terribly expensive 
or hard to do, so I've been preaching the "if want to be able to recover the 
system quickly, make it a VM or cluster" message a lot.

--brerrabbit

+----------------------------------------------------------------------
|This was sent by drhulme AT tarrantcounty DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER