Networker

Re: [Networker] Scanner command taking soooooooooooo long

2009-08-10 17:34:07
Subject: Re: [Networker] Scanner command taking soooooooooooo long
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 10 Aug 2009 16:30:06 -0500
Thanks for the reply.

 

Unfortunately I'm just scanning in one saveset, this saveset happens to
be 800gb.  I'll check out the link to see if it can help me out..

 

Thanks.

 

From: Preston de Guise [mailto:enterprise.backup AT gmail DOT com] 
Sent: Monday, August 10, 2009 4:22 PM
To: EMC NetWorker discussion; Chester Martin
Subject: Re: [Networker] Scanner command taking soooooooooooo long

 

 

On 11/08/2009, at 07:08 , Chester Martin wrote:





I'm running the scanner command against 4 800gb compressed volumes to
see if a user's home share was in this particular backup.  The scanner
command has been running for 3 hours and just now called for the 2nd
tape.   

Is there a way to tell the scanner to pull in information on a
particular folder? I've looked at the scanner man page and nothing jumps
out as to being the solution.

 

(FWIW the scanner command will take as long as a full start<->finish
write/read of the media - hence it's usually 2-3 hours per tape for most
tapes).

 

You can't restrict scanner to sub-saveset ranges, but you can, if the
tape has multiple savesets, restrict the scanning operation to only
those savesets that you are interested in -

 

e.g.,

 

scanner -i -N /home /dev/nst0

 

Also if there's multiple clients on the volume(s) you can restrict to
just those clients that will have the saveset - e.g.,

 

scanner -i -c client -N /home /dev/nst0

 

 

Other than that it's just a case of scanning through the "bare minimum"
of what needs to be rescanned; given that NetWorker's media database
doesn't really work with the notion of "partial" savesets (they're
declared unrecoverable), it's understandable in these circumstances why
scanner doesn't allow you to drill down to lower levels.

 

The other option of course if you just want to recover the data no
matter what is to combine scanner and uasm to just pull the data back as
you find it. Obviously this results in not indexing the data, but if
it's a one-off recovery that *may* be acceptable. (My blog covers this
at
http://nsrd.wordpress.com/2009/04/22/recovering-with-scanner-and-uasm/)

 

Not the exact answer you were looking for, but hope it helps.

 

Cheers,

 

Preston.

 

--

Preston de Guise

 

"Enterprise Systems Backup and Recovery: A Corporate Insurance Policy":


http://www.amazon.com/Enterprise-Systems-Backup-Recovery-Corporate/dp/14
20076396

 

http://www.enterprisesystemsbackup.com

 

NetWorker blog: http://nsrd.wordpress.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