S3 & Multiple Buckets
nhustak2
Posts: 14 Bronze 2
SQL Backup Pro can only use a single linked S3 bucket. This means all backups that are stored must use the same lifecyle settings (at least for BackBlaze)
My client wants a monthly backup that is permanent. We also do a daily full backup with differentials throughout the day. We want these to expire after 7 days (so a rolling expiration)
Is there anyway around this? I thought maybe we could do it per backup job, which would make sense but setting it there sets a global bucket.
My client wants a monthly backup that is permanent. We also do a daily full backup with differentials throughout the day. We want these to expire after 7 days (so a rolling expiration)
Is there anyway around this? I thought maybe we could do it per backup job, which would make sense but setting it there sets a global bucket.
Tagged:
Answers
Hi @nhustak2
Thank you for reaching out on the Redgate forums regarding your SQL Backup question
You're right that SQL Backup Pro only allows you to link a single S3 bucket, which makes it tricky to set different lifecycle policies for different types of backups.
One workaround could be to use S3 folder paths or prefixes within the same bucket to differentiate the backups.
For instance, you could store the monthly backups in one folder (e.g.,
<i>s3://bucket-name/monthly-backups/</i>
) and the daily backups in another (e.g.,<i>s3://bucket-name/daily-backups/</i>
).Then, you could apply different lifecycle policies at the folder/prefix level in your S3 bucket settings:
monthly-backups/
folder that retains these files permanently (or as long as you need).daily-backups/
folder to expire objects after 7 days.While this approach doesn’t solve the issue directly within SQL Backup Pro, it could provide a way to maintain different expiration policies within the same bucket.