Submitted by webwzrd on Fri, 10/02/2009 - 15:11 Pro Licensee
I backup twice a month to Amazon S3 and get an error when Virtualmin backup attempts to delete the old backups. Here is the most recent error message:
Deleting S3 bucket vmbackup-09-01-09, which is 30 days old .. .. deletion failed : Failed to delete S3 bucket : The bucket you tried to delete is not empty
And here is the message from two weeks before:
Deleting S3 bucket vmbackup-08-15-09, which is 30 days old .. .. deletion failed : Failed to delete S3 file : We encountered an internal error. Please try again.
There's no problem deleting the entire (full) bucket with S3Fox. Please advise.
Brian
Status:
Active
Comments
Submitted by JamieCameron on Sat, 10/03/2009 - 00:36 Comment #1
If you list the contents of that vmbackup-09-01-09 bucket using S3Fox , what files does it contain? And can they be deleting individually using S3Fox ?
Submitted by webwzrd on Sat, 10/03/2009 - 07:33 Pro Licensee Comment #2
Each baked-up virtual server has the tar.gz file, plus another file with the same name, but with .info appended to it.. Such as:
File Name File Size domain.com.tar.gz 78755 domain.com.tar.gz.info 1
Yes, I can delete individual files when using S3Fox.
Submitted by JamieCameron on Sat, 10/03/2009 - 14:34 Comment #3
If you manually run the monthly backup again (by starting the monthly cron job that runs /etc/webmin/virtual-server/backup.pl , at Webmin -> System -> Scheduled Cron Jobs), does it fail again to delete that bucket?
Submitted by webwzrd on Tue, 10/06/2009 - 10:38 Pro Licensee Comment #4
Jamie,
Yes, the older backup WAS deleted when manually running the scheduled cron.
Brian
Submitted by JamieCameron on Tue, 10/06/2009 - 11:49 Comment #5
It's possible then that the deletion of files from those buckets failed , causing the bucket itself to be left around. You can see this in the error from your original post - "Failed to delete S3 file : We encountered an internal error. Please try again.".
Assuming backups happen relatively regularly, even if a bucket is missed like this it will be cleaned up in the next run..
Submitted by webwzrd on Tue, 10/06/2009 - 13:31 Pro Licensee Comment #6
So far out of half a dozen bi-weekly backups, the one I re-ran from the cron is the only successful removal. Amazon storage is dirt cheap, but I normally manually delete to avoid the extra 11 GB of storage fee, so I never gave it a chance to catch it on the next time around.
This certainly isn't a big deal, but I'll keep you posted on whether I experience a successful backup and removal.
Thanks, Brian
Submitted by JamieCameron on Tue, 10/06/2009 - 13:39 Comment #7
Thanks, let me know. Unfortunately if a file deletion S3 call fails, there isn't much Virtualmin can do apart from trying to clean up next time..