Looking for bright ideas:

Config:
        C20 running AIX 4.1.5
        67GB filesystem with 1 directory and 1.5 million files
        2.1.0.6G ADSM client

Behavior:

After 40 hours, the idletimeout kicked in.  The client had not sent ANY
data.  Thursday of last week, performed a trace and watched it going
through the inodes (picks a file, then traverses it's inodes).  This is
what is killing us.  To circumvent this from happening we tried:

1. removing all filespaces from the server for a "clean" backup
2. dsmc incr
3. dsmc incr (slow incremental)
4. dsmc selective

It is set to shared static - would dynamic alleviate the problem?

Has anyone been able to get the client to backup a file system without
first traversing the inodes?

V3 allows no query restore, does it have any new backup features which
alleviates this problem?

I understand the need to go through the inodes since if a file changes
during backup it will know this (hence the thought that dynamic might
help).  At least allow the option of NOT traversing the inodes prior to
backup.  We have 3-4 Sun/AIX boxes with 1 Million+ files (the others
actually have directory structures) and this is killing us.

David Hendrix
dmhendri AT fedex DOT com