It is my understanding that the "Process Dirs" indicates the time ADSM spends examining the objects in the filespace in an effort to determine those objects that must be backed up. I would guess that your 1 million files are arrayed across approximately 99,543 directories. The only way I know of to solve this "problem" is to break it down into smaller problems, either by creating smaller filespaces on the client, or breaking them up using the VIRTUALMOUNTPOINT option to create virtual filespaces. I believe that with the 3.7 NT client, the new option "RESOURCEUTILIZATION" that allows you to multiplex your client sessions may be useful, however, that may also require a 3.7 server. - Tom Thomas A. La Porte DreamWorks Feature Animation [EMAIL PROTECTED] On Fri, 21 Jul 2000, Dieter Herzog wrote: >Hi > > We have problems to backup (incremental > procedure)a NT-System (100 GB, 1 Million of > files). > ADSM server Version 3.1.2.5 (OS/390 R2.8) > ADSM Client Version 3.7 > > We activated a client detail trace > during an incremental backup and the trace > information is: > > Final Detailed Instrumentation statistics > >Elapsed time: 16884.969 s >Section Total Time(sec) Average Time(msec) Frequency used > >------------------------------------------------------------------ >Client Setup 4.109 4109.0 1 >Process Dirs 16613.330 166.9 99543 >Solve Tree 0.000 0.0 0 >Compute 0.200 0.0 12989 >Transaction 260.754 1.9 138849 >BeginTxn Verb 0.000 0.0 31 >File I/O 30.766 3.8 8147 >Compression 64.004 4.9 12992 >Data Verb 22.931 4.5 5115 >Confirm Verb 0.000 0.0 2 >EndTxn Verb 19.281 622.0 31 >Client Cleanup 1.422 1422.0 1 > > > The ADSM client is spending the bulk of its time > during the "Process Dirs" process. > What is it doing ? > Suggestion to solve this problem ? > > Thanks in advance > Dieter >
