I think we've been here before, but because I still have a problem and
it has gotten worse of late, I'll try again in hopes someone can
propose a workaround or IBM will
* correct the bug
* fix the performance problem
* correct the BAD design
* all of the above
I have an AIX client that has relatively little data to backup, yet its
backup session takes *many* hours. Today we canceled the backup after
10 hours. The last two hours were viewed by the ADSM (V1, VM) server
as being wait time. Yesterday the ADSM server "saw" almost a 5 hour
"wait time" before the backup completed (in 11 hours).
In every case, the ADSM client is spending all this time spinning his
way through a couple of million files in subdirectories of directories
that have everything EXCLUDEd.
That's right, if the ADSM client does not get to a directory and see
from the include/exclude info that *nothing* could possibly be backed
up in this or lower directories, but just plods through, file by file,
looking for something to do. Meanwhile, a filesystem backup that
should be done in a few minutes lasts many hours, lasting well into
times we'ed rather be doing useful work.
Have others seen this problem? Ditching ADSM backup of (other
important parts of) this filesystem is not something we'd like to see.
Thanks for listening,
Wayne T. Smith mailto:wts AT maine.maine DOT edu
Systems Group -- CAPS University of Maine System
|