On 04/20/98 11:37:38 you wrote:

people are familiar with the temporary performance hole in one's toaster when starting a backup via "rsh toaster dump 0fqwerty etc. etc.", right?

am i imagining it, or is it getting worse with later versions of ONTAP? it's got to the point where users are substantially hampered in working over the weekend when the backups kick off becasue CPU goes to 100% used and stays there for tens of minutes (and, for that matter, at various times during the backups). am i doing something wrong?

I know in a previous version, we ran into a problem where the CPU pegged high when scanning a deep directory tree, hundreds or thousands of entries deep, that someone had created. I believe this impact was alleviated in later releases but I can't be certain of that having not tried it myself.

So, unless your filer is just heavily loaded and/or short of memory when doing your backup, I'd suspect something like a deeply nested directory tree. Perhaps you can locate it an remove it.

Then again, it could be something entirely different. :/

Bruce