Remote backup trouble
I've got remote backups to Amazon S3 enabled, and I've also disabled retaining backups locally. However, while user accounts seem to be backed up fine, system backups are left on the local drive, and aren't ever uploaded to Amazon. Here's how all my logs in /usr/local/cpanel/logs/cpbackup start:
...it then goes on to back up user accounts, which seem to proceed without errors. It looks like this log should have more information at the top, but going back 2 weeks this is how they all start. In /usr/local/cpanel/logs/cpbackup_transporter.log, I see that a number of upload attempts for user account backups have been failing on their first try ("RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period"), but they seem to always succeed the second time around, and there's no mention of system backups.
/bin/gtar: Removing leading `/' from member names
/bin/gtar: /var/lib/mysql/mysql.sock: socket ignored
/bin/gtar: /var/lib/mysql/ib_logfile0: file changed as we read it
[backup] Failed to perform full MySQL database backup
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from hard link targets
/bin/gtar: /var/cpanel/dnsadmin/sock: socket ignored
/bin/gtar: /var/cpanel: file changed as we read it
[backup] Failed to perform full backup of /var/cpanel/ to /backup/2014-06-12/system/dirs/_var_cpanel.tar.gz
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
[backup] System backups will not be uploaded to any remote destinations
pkgacct started....it then goes on to back up user accounts, which seem to proceed without errors. It looks like this log should have more information at the top, but going back 2 weeks this is how they all start. In /usr/local/cpanel/logs/cpbackup_transporter.log, I see that a number of upload attempts for user account backups have been failing on their first try ("RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period"), but they seem to always succeed the second time around, and there's no mention of system backups.
-
Hello :) System backups are not stored on remote destinations by default. You have to manually enable this functionality, as documented here: System Backups Thank you. 0 -
Thanks! It's annoying that there's not a menu option to enable this, but at least the manual change was simple. Should I be worried about the "failed to perform" errors? The /var/cpanel/ one has shown up the past 2 days, and the MySQL the past 3. 0 -
That warning stems from the following entry in the logs you provided: [QUOTE]/bin/gtar: /var/cpanel: file changed as we read it
The information could not archive successfully because files were changing during the attempt. Check your active processes to see if any configuration files in that directory are updating and then run a backup again to see if it persists. Thank you.0 -
After letting a backup run "naturally" overnight, I notice the [date]/system/* files are all still left locally on the drive, even though I unchecked the "retain backups" option. Is this box ignored for system files? If so, would there be any harm in just adding something along the lines of "rm [backup_directory]/*/system/*" to run right after the cpbackup cron task completes? 0 -
Hello, The only harm would be in that if you need them later, they are gone. They really don't take up a lot of room, but as long as you keep at least one copy somewhere, you should be good. 0
Please sign in to leave a comment.
Comments
5 comments