[dnanian]

This has nothing to do with memory, jmooers: it's because files are being actively updated on the source volume when we try to copy them. If you look at the name of the file that seems to be filling the drive, that's what's causing issues.

If this is a server, it's possible that it's a log or similar -- and you can adjust the copy scripts to ignore the log folder(s).

If you have a lot of active services during copy, it's possible those are the problem -- and you should use the before/after copy shell script call-outs to disable and re-enable those services during the backup.

As far as email notification goes, Growl works quite well, so I'd suggest giving that a shot.

Hope that helps.