I would have to agree as well.  Having a dedupe solution replicated to the DR 
site so we can begin recovery faster is currently more valuable than the few 
servers we have issues with recovery to dissimilar hardware.  A conversation I 
had today on this topic suggests more people are looking at tools that allow 
P2V as well as V2V and V2P.  Do you agree?


enchanter wrote:
> In regard to: Re: [Networker] Backup next step: dedup or BMR, or both?,...:
> 
> 
> > 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.
> > 
> 
> Agreed 100% for us too.
> 
> 
> > ... our requirements tilt toward protecting
> > application data far more than they do protecting the components of BMR.
> > 
> 
> That perfectly summarizes our needs too.  We can have an OS installed
> and configured in a relatively short amount of time.  The time it takes
> to get back the application data is generally orders of magnitude longer
> than the time it takes to get the OS ready.
> 
> Tim
> -- 
> Tim Mooney                                             Tim.Mooney < at > 
> ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, IACC Building                             701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
> 
> 
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


+----------------------------------------------------------------------
|This was sent by stevefenner AT gamestop 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