What you can do is just creating multiple instance of the same client
and play with saveset list, schedule and directives.

For sample : assuming your super big E:\ drive,

create one client with
        saveset E:\DIR1
               E:\DIR2
        schedule F 1 1 1 1 1 1

create one client with
        saveset E:\DIR3
               E:\DIR4
        schedule 1 1 1 1 1 1 F

create one client with
        saveset E:\
       directive : +Skip E:\DIR1, E:\DIR2, E:\DIR3, E:\DIR4
        schedule 1 1 1 F 1 1 

Play with your group membership for starting time.

All dirs not backuped by the 2 first client settings
will be backuped by the third one (No unprotected files)
Time to time, you may have to adapt the saveset lists and
directive.

You can also load balance your fulls (and differential) for
faster recover without relying on old-full.

Do also not use incrementals as it will recover from all tapes
since full till recover time. (longer recover)

Adapt also by adding/removing/grouping entries in saveset lists 
and adapting client parallelism to be more aggressive on the 
storage volume and take backup at the same time for data that
may require to stay in sync.

I am not sure disk backup to be the solution in this case, 
because the entire tree structure will have to be walked thru.
Splitting volume by directories may be the solution.

Another one is to perl-script a job that looks at a volume (argument)
and the split on each dir from volume root folder  and call save cmds
but it will be more difficult to play with levels (save cmd requires
nsavetime
of last full to rely to when processing leveled backups).

HTH

TH

Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
                                   
 *********       *********   HEWLETT - PACKARD
 *******    h      *******   1 Rue de l'aeronef/Luchtschipstraat
 ******    h        ******   1140 Bruxelles/Brussel/Brussels
 *****    hhhh  pppp *****   
 *****   h  h  p  p  *****   100/102 Blv de la Woluwe/Woluwedal
 *****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
 ******      p      ******   BELGIUM
 *******    p      *******                              
 *********       *********   Phone :    +32 (0)2  / 729.85.42   
                             Mobile :   +32 (0)498/  94.60.85 
                             Fax :      +32 (0)2  / 729.88.30   
     I  N  V  E  N  T        Email/MSN : thierry.faidherbe(at)hp.com
                             Internet  : http://www.hp.com/ 
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Ty Young
Sent: Wednesday, June 07, 2006 4:07 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Slow Win2k backup with lots of files

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.

Just so you don't feel alone, I have run into exactly the same problem.
In my environment there are a number (> 5) of Windows machines with
millions of files within about 75 directories, all under "E:\" which are
supposedly business-critical.    I used to be able to make the excuse
that
the symptoms you're describing are simply inherent with Windows, i.e.
tons
of tiny binary files, but this isn't always the case any longer.

In one particular case, I've had to resort to fulls about 1x/quarter and
just run incrementals all other days so that I get daily coverage.   I
also
pray a lot, and occasionally I remember to be thankful for the
relatively
good health of the client machine and the SAN on which its data is
located.
:-)

But truthfully you're not alone and I think the disk-based backup (to
which
you could stage off to tape) is probably what a lot of shops use to get
past this issue.


Phillip T. ("Ty") Young, DMA
Manager, Data Center and Backup/Recovery Services
Information Services
i2 Technologies, Inc.


 

             "Dewhirst, Rob"

             <dewey AT KU DOT EDU>

             Sent by: Legato
To 
             NetWorker                 NETWORKER AT LISTSERV.TEMPLE DOT EDU

             discussion
cc 
             <NETWORKER@LISTSE

             RV.TEMPLE.EDU>
Subject 
                                       Re: [Networker] Slow Win2k backup

                                       with lots of files

             06/07/2006 08:56

             AM

 

 

             Please respond to

             Legato NetWorker

                discussion

             <NETWORKER@LISTSE

              RV.TEMPLE.EDU>;

             Please respond to

              "Dewhirst, Rob"

              <dewey AT KU DOT EDU>

 

 





> Rob,
> Could you write a script that updates the client record of
> this machine (say once an hour), with the main folders. This
> would allow you to create your saveset streams, without user
> intervention ?

I really thought I had a firm grasp of most networker functions, but I
don't understand which client record you mean.

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