---- Original message ----
>Date: Thu, 16 Jun 2005 17:46:15 -0500
>From: "Werth, Dave" <dave.werth AT GARMIN DOT COM>  
>Subject: Re: [Networker] Restore questions  
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>
>Stan (or anyone),
>
>Questions, comments interspersed below.
>
>Thanks, Dave
>
>David Werth
>Garmin AT, Inc
>Salem, Oregon
>dave.werth AT garmin DOT com
>
>-----Original Message-----
>From: Stanley Horwitz [mailto:stan AT temple DOT edu] 
>Sent: Thursday, June 16, 2005 2:18 PM
>To: Legato NetWorker discussion; Werth, Dave
>Subject: Re: [Networker] Restore questions
>
>
>>You should do a saveset recover, which is not what you described. A  
>>saveset
>>recover is the fastest option because NetWorker does not need to hit  
>>its database
>>for each file that needs to be restored.
>
>DFW - Any idea how much faster a saveset recover is?  If it's only 5% or so
>it's probably not worth stopping what we've got going to restart it.  If
>it's 25% or more then maybe it is.  Any thoughts?

Dave, each time NetWorker goes to recover a file, it has to query its databases?
So, how long this takes depends on the number of files that need to be 
recovered.
For a large number of files, more than say around 10K, you might see a 
significantly
faster recover time in a DR situation. 

Other factors can influence the recover speed too, such as your network 
bandwidth
and the type of storage you are recovering too, as well as the HBA that is used
to connect the storage to the client.

Frankly though, questions like this are why recover testing is so important.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=