- Posts: 5
- Liked: never
- Joined: Jul 01, 2021 3:39 am
- Full Name: Teerakiat K
Customers have scenario where they would like to keep yearly backup year 1, year2 to be on premise performance tier. After reached the time move policy to object storage (S3).
From my understanding if we configure backup job GFS for performance tier if the yearly data had performed backup then after the SOBR capacity tier policy the data would move to object storage (S3) ?
For example if capacity tier policy is data older than 14 days after the backup job yearly year 1 had backup then at day 15 the yearly data would move to object storage straight away?
- Veeam Legend
- Posts: 1664
- Liked: 671 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: St. Gallen, Switzerland
Your yearly flagged restore point (vbk) will be moved to capacity tier, after your configured 14 days.
If you want to have the yearly RPs only onpremise, you need to configure the move policy to 365 days. But that will keep all RPs onPremise until a year is over. Not very good.
Why does he want to have the yearly only onpremise? It should‘t take to much more storage if you keep it in the capacity tier too. Only changes will be offloaded an not the entire „vbk-size“.
Working with Veeam since 2017 for a VCSP in Switzerland
- Veeam Legend
- Posts: 500
- Liked: 246 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey Carel
No, this is wrong.
14 days means 14 days. If your GFS point is older than 14 days, it will be moved. The move period has no concern as far as I'm aware about the GFS periodicity; a backup is a backup is a backup.
I would be very curious why anyone would want such staggered offloading on a per-backup-file basis and I'm not sure it gives a ton of benefits.
- Product Manager
- Posts: 18837
- Liked: 1904 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
Users browsing this forum: No registered users and 19 guests