Skip to main content

Amazon S3 Backup retention

Comments

10 comments

  • cPanelPeter cPanel Staff
    Hello, Your access level isn't listed on this forum. Do you have full root access to the server? If so, please review the log files in: /usr/local/cpanel/logs/cpbackup/
    Specifically look for the word "Pruning" and see if there are errors related to that. If you don't have access to the server via SSH, then you'll need to discuss this with your data center.
    0
  • Benito
    Thanks Peter, im the administrator of this server. Looking on the logs i only find one occurence of Pruning. Its one of the last lines and it says: [backup] pruning backup directory: /backup/2014-06-09 But on Amazon, the folder 2014-06-09 still exist. Im not sure if this is a problem, but i do not have any "backup" folder on amazon. This is the folder structure of my bucket. Daily backups on root and a monthly folder. ]http://i.imgur.com/HfdgKkz.png
    0
  • cPanelMichael
    I believe we could provide a more accurate answer if we were able to review your existing setup and see what's happening. Could you open a support ticket so we can take a closer look? You can provider the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • Benito
    Thanks Michael, the ticket id is: 5106031
    0
  • cPanelMichael
    To update, the user is running some tests to see if the issue is related to settings/processes on their remote Amazon S3 server. Please feel free to update us with the outcome. Thank you.
    0
  • dto123
    Was there any update on this?
    0
  • cPanelMichael
    [quote="dto123, post: 1675782">Was there any update on this?
    The user found an issue with the permissions they were assigning to Amazon users on each server. Thank you.
    0
  • Benito
    [quote="dto123, post: 1675782">Was there any update on this?
    Hi! I was using this policy for the users with access to the bucket. { "Statement":[ { "Effect":"Allow", "Action":[ "s3:ListAllMyBuckets" ], "Resource":"arn:aws:s3:::*" }, { "Effect":"Allow", "Action":[ "s3:ListBucket", "s3:GetBucketLocation" ], "Resource":"arn:aws:s3:::you_bucket_name" }, { "Effect":"Allow", "Action":[ "s3:PutObject", "s3:GetObject", "s3:DeleteObject" ], "Resource":"arn:aws:s3:::you_bucket_name/*" } ] }
    And after some testing i ended using this policy, less restrictive. { "Statement": [ { "Effect": "Allow", "Action": "s3:ListAllMyBuckets", "Resource": "arn:aws:s3:::*" }, { "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::bucket_name", "arn:aws:s3:::bucket_name/*" ] } ] }
    0
  • keencs
    [quote="benito, post: 1676782">Hi! I was using this policy for the users with access to the bucket. ...
    Was this policy effective in allowing your backups to be pruned? I am experiencing the same problem. I have implemented the policy changes you suggested without success. Previous research for me indicated that pruning on S3 was not yet supported by cPanel backups. Has it been confirmed that it is? Ryan
    0
  • Benito
    [quote="keencs, post: 1678032">Was this policy effective in allowing your backups to be pruned? I am experiencing the same problem. I have implemented the policy changes you suggested without success. Previous research for me indicated that pruning on S3 was not yet supported by cPanel backups. Has it been confirmed that it is? Ryan
    Yes, my backups are prunning correctly.
    0

Please sign in to leave a comment.