-
- Influencer
- Posts: 10
- Liked: never
- Joined: Dec 09, 2022 1:01 am
- Full Name: Thanakhrit
- Contact:
GFS backup retention policy and SOBR with Archive tier aws glacier
I have a a question about GFS backup retention policy and SOBR with Archive tier using Veeam 11
- Local backups: One Full Backup Monthly Keep data 1 Month;
- SOBR Capacity tier: Copy local backups as soon as they are created; copy backup files older than 30 days; (AWS S3 Standard-IA)
- SOBR Archive tier: Archive GFS full backups older than 30 days as standalone fulls (AWS S3 Glacier)
How to keep data SOBR Archive tier policy 1 year ? configure on AWS AS3 Glacier ?
- Local backups: One Full Backup Monthly Keep data 1 Month;
- SOBR Capacity tier: Copy local backups as soon as they are created; copy backup files older than 30 days; (AWS S3 Standard-IA)
- SOBR Archive tier: Archive GFS full backups older than 30 days as standalone fulls (AWS S3 Glacier)
How to keep data SOBR Archive tier policy 1 year ? configure on AWS AS3 Glacier ?
-
- Product Manager
- Posts: 10273
- Liked: 2745 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
Hello
The retention for backups is configured in the job settings. To have monthly fulls in archive tier, you must configure monthly GFS retention to 12 months.
To move those gfs backups from your performance tier, use the move policy on your capacity tier. Move will remove the backups after the specified operational restore window from your performance tier.
S3 Standard-IA sounds wrong to me, if you want to immediately move the entire restore point away. Minimum storage policy for it is 30 days. Every object removed before those 30 days will cost you extra.
With S3 Standard-IA you should configure your job keep at least 30 daily restore points with 12 monthly GFS restore points.
Best,
Fabian
The retention for backups is configured in the job settings. To have monthly fulls in archive tier, you must configure monthly GFS retention to 12 months.
To move those gfs backups from your performance tier, use the move policy on your capacity tier. Move will remove the backups after the specified operational restore window from your performance tier.
S3 Standard-IA sounds wrong to me, if you want to immediately move the entire restore point away. Minimum storage policy for it is 30 days. Every object removed before those 30 days will cost you extra.
With S3 Standard-IA you should configure your job keep at least 30 daily restore points with 12 monthly GFS restore points.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Dec 09, 2022 1:01 am
- Full Name: Thanakhrit
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
"To have monthly fulls in archive tier, you must configure monthly GFS retention to 12 months." configure on job backup policy data keep on perfomance tier ?
-
- Product Manager
- Posts: 10273
- Liked: 2745 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
A Scale Out Backup Repository does not have retention policies. The retention Policy is configured on Job Level.
On the Scale Out Backup Repository you specify when and how to move stored restore points to the next tier.
Please also note, on capacity and archive tier, a full backup won't take the entire space. You will have a forever forward incremental backup chain on those tiers. We only offload unique blocks of a backup files as objects. Unchanged source data between two full backups will leverage the same objects in AWS S3.
To use immutability and faster RTO (recovery time objective) times from Object Storage, I strongly recommend to keep more backups on capacity tier.
Job Settings:
30 days restore points, weekly synthetic fulls
Keep 4 weekly, Keep 12 monthly restore points

Capacity Tier Move Policy:
- Example with Azure Blob, works same for AWS S3
- Copy: Copy all restore points immediately from performance tier (your local storage) to the capacity tier
- Move with 0 days: Remove inactive backup chains from the performance tier (your local storage) instantly after a new backup chain has started on performance tier

Archive Tier Policy:
- Example with Azure Archive, works same for AWS S3 Glacier
- Archive Policy: Move GFS backups older than 30 days. You don't want to remove backups on S3 Standard-IA earlier than 30 days minimum storage policy, because you have to pay Amazon a early deletion fee for it.

On the Scale Out Backup Repository you specify when and how to move stored restore points to the next tier.
Please also note, on capacity and archive tier, a full backup won't take the entire space. You will have a forever forward incremental backup chain on those tiers. We only offload unique blocks of a backup files as objects. Unchanged source data between two full backups will leverage the same objects in AWS S3.
To use immutability and faster RTO (recovery time objective) times from Object Storage, I strongly recommend to keep more backups on capacity tier.
Job Settings:
30 days restore points, weekly synthetic fulls
Keep 4 weekly, Keep 12 monthly restore points

Capacity Tier Move Policy:
- Example with Azure Blob, works same for AWS S3
- Copy: Copy all restore points immediately from performance tier (your local storage) to the capacity tier
- Move with 0 days: Remove inactive backup chains from the performance tier (your local storage) instantly after a new backup chain has started on performance tier

Archive Tier Policy:
- Example with Azure Archive, works same for AWS S3 Glacier
- Archive Policy: Move GFS backups older than 30 days. You don't want to remove backups on S3 Standard-IA earlier than 30 days minimum storage policy, because you have to pay Amazon a early deletion fee for it.

Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Dec 09, 2022 1:01 am
- Full Name: Thanakhrit
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
thank you for information, AWS S3 Glacier can keep data long term because have to pay?
-
- Product Manager
- Posts: 10273
- Liked: 2745 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
You can keep data on any Tier as long as you want. But you have to pay AWS for that storage as long as you have stored data on it. Does that answer your question?
Best,
Fabian
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 30, 2023 4:04 am
- Full Name: Komkrit Chalermsri
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
Hi Mildur
This config means backup to local storage (Performance tier) 30 day and copy mirror with AWS S3 (Capacity tier) then keep full GFS to AWS S3 Glacier (Archive tier) 12 month. Is it right?s
I have scenario.
1. keep data backup local storage (Performance tier) 30 day.
2. copy mirror with AWS S3 (Capacity tier).
3. if data backup older 30 day give moving data to AWS S3 Glacier (Archive tier).
4. keep data backup on AWS S3 Glacier (Archive tier) 1 year.
Please tell me about the config for both Backup Job and SOBR.
Thank you.
This config means backup to local storage (Performance tier) 30 day and copy mirror with AWS S3 (Capacity tier) then keep full GFS to AWS S3 Glacier (Archive tier) 12 month. Is it right?s
I have scenario.
1. keep data backup local storage (Performance tier) 30 day.
2. copy mirror with AWS S3 (Capacity tier).
3. if data backup older 30 day give moving data to AWS S3 Glacier (Archive tier).
4. keep data backup on AWS S3 Glacier (Archive tier) 1 year.
Please tell me about the config for both Backup Job and SOBR.
Thank you.
-
- Product Manager
- Posts: 15125
- Liked: 3230 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 30, 2023 4:04 am
- Full Name: Komkrit Chalermsri
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
Do you have pictures to show config?
Because I have config Archive GFS backups older than 90 day lower but data not transfer to AWS S3 Glacier.
Because I have config Archive GFS backups older than 90 day lower but data not transfer to AWS S3 Glacier.
-
- Product Manager
- Posts: 15125
- Liked: 3230 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: GFS backup retention policy and SOBR with Archive tier aws glacier
I guess the "Archive backups only if the remaining retention time is above minimal storage period" is still checked.
There is a picture of that option on bottom of https://helpcenter.veeam.com/docs/backu ... ml?ver=120
There is a picture of that option on bottom of https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Who is online
Users browsing this forum: No registered users and 7 guests