-
- Expert
- Posts: 239
- Liked: 13 times
- Joined: Feb 14, 2012 8:56 pm
- Full Name: Collin P
- Contact:
S3-Single Zone Infrequent Access Compatibility
I'm looking at the guide for Veeam Backup for AWS 4.0 https://helpcenter.veeam.com/docs/vbaws ... tml?ver=40. I didn't see it mentioned here, but would a lifecycle policy on the S3 bucket to Infrequent Access Single Zone storage be supported?
-
- Product Manager
- Posts: 5796
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: S3-Single Zone Infrequent Access Compatibility
Hi Collin,
Could you clarify what your goal is? In general, we do not recommend using lifecycle policies on our repositories as it may affect our standard operations so clarification on your goal will help with giving advice.
We have a note on the repositories page stating to adjust your existing lifecycle policy.
Could you clarify what your goal is? In general, we do not recommend using lifecycle policies on our repositories as it may affect our standard operations so clarification on your goal will help with giving advice.
We have a note on the repositories page stating to adjust your existing lifecycle policy.
If you have any S3 Lifecycle configuration associated with the selected Amazon S3 bucket, limit the scope of lifecycle rules applied to Amazon S3 objects in the bucket so that no rules are applied to backup files created by Veeam Backup for AWS. Otherwise, the files may be unexpectedly deleted or transitioned to another storage class, and Veeam Backup for AWS may not be able to access the files.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Expert
- Posts: 239
- Liked: 13 times
- Joined: Feb 14, 2012 8:56 pm
- Full Name: Collin P
- Contact:
Re: S3-Single Zone Infrequent Access Compatibility
Goal is to store backup files for long term retention in S3. S3 "Standard" is overkill since we are already storing 7 snapshots in 2 different regions. S3-IA Single Zone is half the cost of S3 standard and stores data in a single availability zone versus multiple. We don't need the data in multiple availability zones since we already have multiple copies stored. Anyway, my question was more around if a lifecycle policy to S3-IA would cause any issues from a technical standpoint. I don't see why it would since files are still available and accessible from S3-IA, same as S3 standard. It's not like Glacier where files require a special request to make available.
-
- Product Manager
- Posts: 5796
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: S3-Single Zone Infrequent Access Compatibility
Understood, we currently don't support IA but your request is noted to support it in a later version.
Keep in mind that for IA, you need to store data at least for 30 days in there. With our current schedule policy, it is possible to keep 1-2 weeks of backups on S3 standard and then opt to move them to Glacier as in general most restores happen between now and 14 days ago which is what we recommend in this case.
Keep in mind that for IA, you need to store data at least for 30 days in there. With our current schedule policy, it is possible to keep 1-2 weeks of backups on S3 standard and then opt to move them to Glacier as in general most restores happen between now and 14 days ago which is what we recommend in this case.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: No registered users and 2 guests