I have the same problem on a HP-UX system, but I know that's due to a big
directory which contains more than 150.000 files.  I think that ADSM
collects all the info from the server to check what should be backed-up,
using -INCRBYDATE reduces the amount of memory requested on the client
(less info per single file!).

The problem on my box is related to the maxdsiz parameter!

Hope this helps

Mauro

> At present we are having problems completing a successful scheduled
> backup on a DEC UNIX server with an ADVFS file system that has 680,000
> files on one drive and 75,000 files on two others.  We repeatedly get
> 'out of memory' errors that cancel the backup.  Huge amounts of memory
> on the UNIX server and the ADSM server are  both available at the time.
> I can only concluded that the application is encountering some
> pre-determined internal limit or there is some type of memory leak in
> the application.  For a time, we were able to run the backup from the
> command line successfully, but now it too aborts the backup with the
> 'out of memory' error.  The ADSM server is at version 3.1.0.3 and the
> client the UNIX box is running is 3.1.0.6.  Any ideas?
> --
> ******************************************
> Renee Davis
> Central Computing/Telecommunication Services
> Program Analysis Specialist
> RDavis AT UH DOT EDU
> ******************************************