Josh,

Are you the fellow formely with Dickens?

At any rate I have had this same problem.
To solve it we developed a plan using 2 (can be more than 2) clients. The
process was set up utilizing an exclusion listing based upon the alpha
location.
Client-A backed up all directories starting with [a-j]* and excluded all
directories begining with
[k-z]*. Client-B reversed the roles. The major problem is to determine the
data
load. It may require some digging to balance
where the load is. In our case it was noted that [a-j]* held little data
while
[k-z]* had copious quantities. Tha answer was to adjust this number of
clients
to reflect a reasonable level of data and to provide the maximum threads
possible for backup.

This means also, that the administrators must be aware of the root
directories
for files requested for restore. This means they must come to work with
there
brains engaged.

Respectfully,


Gene Klaus
eklaus AT flagstar DOT com
248-709-2100




"Joshua S. Bassi" <jbassi AT IHWY DOT COM> on 11/16/2000 02:56:45 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Eugene A Klaus/Flagstar_notes)
Subject:  Re: Windows NT Restore Performance



Unfortunately my customer has created one huge data partition with only
one main directory on it.  There are 2000 small directories under that
directory. So there is really no way to run multiple streams against
that.  And to top it off it is not only a compressed NTFS volume, but
a 3-4 disk RAID-5 set, so when I use the GUI for the restore, it only
fires off 2 streams (1 for send & 1 for receive).

Thank you,

Josh