Although I am a command line junkie, not everyone else is.  I'm about 50/50 on 
using the gui vs command line for restores.  For ndmp restores I only use the 
command line.

But opening a gui and restoring to a different server than you backed it up 
from into a different folder logically is a lot more efficient for me than it 
would be to craft together a command to do it, plus grabbing the saveset name.  
:)

-----Original Message-----
From: Thierry FAIDHERBE [mailto:Thierry.Faidherbe AT skynet DOT be] 
Sent: Friday, October 22, 2010 11:24 AM
To: 'EMC NetWorker discussion'; Chester Martin
Subject: RE: [Networker] Why is NetWorker User single threaded?

GUI... GUI... Use CLI even on Windows ! :-) Use ssid-based recovery for such 
recover. 
Using GUI is mainly for recovering small amount of files.

When you need to recover an entire drive or a big tree, use recover -S ssid 
(look at manpage, sorry, at pdf doc for other
options) and think to also suppress verbose output (use -q option) to max the 
recover speed, everybody knows displaying filename of recovered files slow down 
the recover process (displaying being slower than IOWrite)

HTH

Th

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Chester Martin
Sent: jeudi 21 octobre 2010 17:04
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Why is NetWorker User single threaded?

Yeah, we were going to use networker user to do an initial restore of data to a 
new server that we were migrating to.  This was a server with thousands of 
files on it.  When I tried to select the top level folder in networker user I 
could see it "selecting" the files in the subfolders.  15 minutes later all the 
files in the 1st subfolder hadn't been selected.  Needless to say we just used 
robocopy for the initial copy of the data. :)

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Len Philpot
Sent: Thursday, October 21, 2010 9:40 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Why is NetWorker User single threaded?

> James Pratt
> 
> Yes, The UI has always locked up on *any* restore here (We run NW 
> server on windows32, 2003 R2). we found if we just leave it be, it 
> will unlock when it's done. (I assumed it was because the legato 
> user/recovery app appears it has not been updated in years, but i'm 
> not sure... :\

Yep - Nothing new. We used to have a test server that periodically got reloaded 
with data from its production counterpart's backup. Try selecting multiple 
directories with a total of several hundred thousand (mostly
small) files... It would hang for more than an hour(s) at times. But it always 
ended up restoring OK.

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

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

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