Quote:
Originally Posted by dnanian
Well, I definitely was able to copy my own 10.3.9 server every day for a few years without a problem, so I know it's possible.
So. I think it's likely that a file (logfile, database, something) is being written to aggressively when we try to copy it, and that fills the destination. Why that would prevent unmounting I don't know, but it's likely that's why the disk is filling. What file does it say was copied when the drive fills?
|
Hello,
The error happened again. Please find the cloning log file attached. Looks like it has something to do with a Apache server log. Don't know the specifics though. Oh yes, again I was unable to unmount the volume until I restarted the entire server. does that mean that I have to schedule the back up at a different time? Maybe Apache is doing log file rolling at that time and That's what is causing it? I have no clue. Anyway, please have a look. If there is anything that I could do, like a script that would stop certain processes and then starts them again after cloning.. that would be great. But I wouldn't even know where to start.