You could try using incremental by date option in the backup.  There
is much less ADSM client-server interaction.  And there is much less
work for the NT client to do for each file.

As another suggestion, you could also turn on "memory efficent
backup".  Bewarned that you will put considerable load onto your ADSM
*server* and network.  There will now be an interaction with the
server for each directory, cf a large download at the start before.

Normally the NT client downloads a map of all the files held at the
last backup.  If that file list is very large it can not be contained
in physical memory will be paged out to disk.  As the NT client then
traverses the file system it incurs extra disk hits paging back in the
file list.

You will be able verify this with Performance Monitor.

I would try each of these in turn and see which one does the most
good.


Russell


> The ADSM for NT version is 3.1.2.40, the NT client is 3.7.
>
> I make an incremental backup for the client.
>
> In the dsmsched.log appears for example:
>
> 12/08/1999 02:53:14 ANS1898I ***** Processed   164,000 files *****
> 12/08/1999 02:53:47 ANS1898I ***** Processed   164,500 files *****
> ...
> 12/08/1999 03:29:05 ANS1898I ***** Processed   211,000 files *****
> 12/08/1999 03:29:12 ANS1898I ***** Processed   211,500 files *****
>
> ADSM checks 700,000 files on this client and backup 4 GB and needs more
> then 8 hours!
>
> The 100 Mbit/s Network is not the bottleneck. The selective backup with
> ADSM is much faster.
>
> The Cache Hit Pct. from the database is over 99.
>
> Does anybody else have a fileserver with so many files and is this backup
> time normal for ADSM/NT or what can I try?
>
> Michael