Warren,

However, I agree it is the best solution.

Siobhan

From: Steve Warren <swarren AT CRESEND DOT COM>

Reply-To: Legato NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>, Steve Warren <swarren AT CRESEND DOT COM>

To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Slow Win2k backup with lots of files
Date: Wed, 7 Jun 2006 16:15:31 -0400

If you try the suggestions recommended here and it doesn't solve your problem, I suggest you seriously consider SnapImage. It has it's limitations but restore performance from tape is not the issue it's been represented to be here. And on a big slow disk with millions of files, there's no faster way to get file-granular backups to tape.

SnapImage sorts all the file extents in the restore list before it starts so the restore is done in a single pass. Pieces get restored in tape order and assembled on the fly. It's certainly no slower than restoring from a normal multiplexed tape.

There are things about it that are a little more cumbersome though so you should make sure you really have a need for it before you go that direction.

> > > I think that other person meant that maybe there'd be a way
> > > to use the "update" function within nsradmin to update the
> > > client's list of savesets to be backed up, in an automated fashion.
> >

> > I have no problem scripting nsradmin, but what does updating the client

> > record more frequently accomplish?
>
> I read the message not that it needs to be terribly frequent, but that
> it needs to be automated so that human intervention isn't needed to pick
> up new folders.
>
> The frequency just gives the maximum time that can elapse between the
> creation (and population) of a folder and having it hit the backups.
> Daily would probably be sufficient in most environments.
>
> --
> Darren Dunham                                           ddunham AT taos DOT 
com
> Senior Technical Consultant         TAOS            http://www.taos.com/
> Got some Dr Pepper?                           San Francisco, CA bay area
>          < This line left intentionally blank to confuse you. >
>

> 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 > wit 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 wit 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
wit 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