Sounds like a client defect. You might be able to circumvent by backing up in
pieces, such as doing one major subdirectory of a file system at a time.
Some other things to check:
- Verify that the account that ran the operation, has sufficient Unix
Limits values to allow the operation;
- Check the Backup log to see where the thing ended: this may be the
case of a circular symlink causing ADSM to go in circles until
virtual memory is exhausted. You might also do a
'find DIRNAME -type l -ls' to inspect symlinks in suspected
directory.
You might also try a client trace to see what's happening, and/or watch the
backup with operating system process monitoring to see if memory usage
grows linearly (and how fast), and if there is a spike. And see if there
is a difference in resource consumption in running it interactively, from
the command line, versus a schedule.
Richard Sims, BU
