Amazon S3 bucket empty after backup
Hi
I have setup Amazon S3 as an additional destination at 'Backup > Backup Configuration'. Clicking on 'Validate All Destinations' reports: 'Success: "Amazon S3 backup" validated'. But after running a backup the S3 bucket is still empty.
These are the backup logs:
From /usr/local/cpanel/logs/cpbackup/
/usr/local/cpanel/logs/cpbackup_transporter.log
Interesting that it says 'retaining 1 items' when there's nothing there. When I login to Amazon Web Services it says the bucket is empty. Any ideas what went wrong?
/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 member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: /var/cpanel/dnsadmin/sock: socket ignored
/bin/gtar: Removing leading `/' from hard link targets
/bin/gtar: /var/cpanel: file changed as we read it
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/bin/gtar: Removing leading `/' from member names
/usr/local/cpanel/logs/cpbackup_transporter.log
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Initializing log file
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon started.
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] cpbackup_transporter - started
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Initializing log file
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Can't locate object method "die" via package "Cpanel::LoggerAdapter" at /usr/local/cpanel/Cpanel/Daemonizer.pm line 62.
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] cpbackup_transporter - Processing next task
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Instantiating Object
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Starting a "prune" operation on the "Amazon S3 backup" destination ID "idgoeshere".
[2015-01-15 01:36:51 +1100] info [cpbackup_transporter] Performing prune operation, retaining 1 items on: Amazon S3 backup
[2015-01-15 01:36:52 +1100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2015-01-15 01:36:52 +1100] info [cpbackup_transporter] cpbackup_transporter - Processing next task
[2015-01-15 01:36:52 +1100] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
[2015-01-15 01:36:52 +1100] info [cpbackup_transporter] cpbackup_transporter - Exiting - the queue has been emptied; no more work to do
[2015-01-15 01:36:52 +1100] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon is being stopped.
Interesting that it says 'retaining 1 items' when there's nothing there. When I login to Amazon Web Services it says the bucket is empty. Any ideas what went wrong?
-
Don't worry, I figured it out. In 'Backup > Backup User Selection' all the accounts were switched on for 'Legacy' and off for 'Backups'. Reversed this and problem solved. (I recently migrated to a new server and switched to the newer backup system, but didn't realise I had to manually switch every account across too.) 0 -
Hello :) I am happy to see you were able to address the issue. Thank you for updating us with the outcome. 0 -
No worries Michael. But while I've got your attention, that line in the log, 'Can't locate object method "die" via package "Cpanel::LoggerAdapter"'" I'm still getting that. Does this indicate a problem, or can I safely ignore it? 0 -
What version of cPanel is installed on your system? If you are using a recent version (11.46 or higher), then please open a support ticket so we can take a closer look at that warning message. You can post the ticket number here so we can update this thread with the outcome. Thank you. 0
Please sign in to leave a comment.
Comments
4 comments