problem with filesystem backup

Hmm, my best guess is that it's concerned about the "file changed as we read it" messages above. Which is to be expected when reading the access log of a web server :-)

The "socket ignored" lines shouldn't be a problem.

However, nothing in the above indicates an incomplete or problematic backup.

I'd verify that your backups look complete on the backup server -- and if so, I think you're in good shape.

To get rid of those messages, you might consider:

1. In the backup details, you might consider having it ignore directories such as /tmp. /var/spool/postfix/private/, and the like.

2. You can rely on the Virtual Server backup (assuming you've set one up ;-) to get /home, as well as the MySQL databases. It's not really possible to get a good backup of mysql through a filesystem backup.

Have a good one!

-Eric

Well, again, I think it's concerned about the "file changed as we read it" messages.

So you'd want to tell it to stop backing up the MySQL databases in /var/lib/mysql (you can use the Virtualmin scheduled backups in "Backup and Restore" to get those).

You might also consider not using that to backup the log files (such as /home/log/auth.log), as log files change frequently.

But, if you want to make sure you have logs around, I'd verify that the Virtual Server backups store those.

-Eric