I let the new backup script run automaticly after configuring things thusly:
Type: compressed
Frequency: daily (every day) and monthly (1st)
Destinations: local directory (/backup), local directory (/root/Dropbox/server - for redundancy)
Backing up account and system files. Backing up MySQL per account and the entire directory. Retaining local backups, as well as depositing them into Dropbox. Examining the backup log, everything pretty much falls apart from step 1. Exerpt pasted below:
/bin/gtar: Removing leading `/' from member names
/bin/gtar: /var/lib/mysql/rsgames_ZGP/ChatLog.MYD: file changed as we read it
/bin/gtar: /var/lib/mysql/mysql.sock: socket ignored
/bin/gtar: /var/lib/mysql/quanin_rss: file changed as we read it
[backup] Failed to perform full MySQL database backup
The fun continues for system files:
/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: 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: Removing leading `/' from member names
It doesn't look like it even attempts to back up accounts, even though accounts are selected. 2013-07-18 is a very impressive 634M at the moment, with an empty accounts folder and missing several items that probably should be included. The dropbox directory contains only a system_files.tar and nothing else. This is reproduceable on the server always; I've run the backup manually with the exact same result.
I've removed both folders and rerun the backup with again the same result, and again the folder in /backup is 634M. I was hoping to be able to use this system on account of it makes less work for me re: putting the backups from the old system in Dropbox for safe keeping. But now I'm thinking maybe not so much. Any feedback on this would be most helpful.
Type: compressed
Frequency: daily (every day) and monthly (1st)
Destinations: local directory (/backup), local directory (/root/Dropbox/server - for redundancy)
Backing up account and system files. Backing up MySQL per account and the entire directory. Retaining local backups, as well as depositing them into Dropbox. Examining the backup log, everything pretty much falls apart from step 1. Exerpt pasted below:
/bin/gtar: Removing leading `/' from member names
/bin/gtar: /var/lib/mysql/rsgames_ZGP/ChatLog.MYD: file changed as we read it
/bin/gtar: /var/lib/mysql/mysql.sock: socket ignored
/bin/gtar: /var/lib/mysql/quanin_rss: file changed as we read it
[backup] Failed to perform full MySQL database backup
The fun continues for system files:
/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: 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: Removing leading `/' from member names
It doesn't look like it even attempts to back up accounts, even though accounts are selected. 2013-07-18 is a very impressive 634M at the moment, with an empty accounts folder and missing several items that probably should be included. The dropbox directory contains only a system_files.tar and nothing else. This is reproduceable on the server always; I've run the backup manually with the exact same result.
I've removed both folders and rerun the backup with again the same result, and again the folder in /backup is 634M. I was hoping to be able to use this system on account of it makes less work for me re: putting the backups from the old system in Dropbox for safe keeping. But now I'm thinking maybe not so much. Any feedback on this would be most helpful.