-
- Influencer
- Posts: 11
- Liked: 1 time
- Joined: Feb 03, 2021 5:10 pm
- Full Name: Jonathan Wandless
- Contact:
Veeam Backup Copy Job (GFS question)
Morning all (Happy Monday)
I have a backup copy job with a retention policy set to 14 days.
I then configured GFS to Keep 1 weekly full backups (1 weeks)
I have monitored over the weeks, thinking i would see only 1 weekly full but after 3 weeks, i can now see 3 fulls? is this correct and why isn't that weekly getting replaced with another weekly (Since i set GFS to weekly (1)
Any light and understanding would be fantastic!
Jonathan.
I have a backup copy job with a retention policy set to 14 days.
I then configured GFS to Keep 1 weekly full backups (1 weeks)
I have monitored over the weeks, thinking i would see only 1 weekly full but after 3 weeks, i can now see 3 fulls? is this correct and why isn't that weekly getting replaced with another weekly (Since i set GFS to weekly (1)
Any light and understanding would be fantastic!
Jonathan.
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Veeam Backup Copy Job (GFS question)
Hi Jonathan,
I've asked my colleagues from QA department to check this scenario explicitly, I'll update the topic as soon as I have more details.
Thanks!
I've asked my colleagues from QA department to check this scenario explicitly, I'll update the topic as soon as I have more details.
Thanks!
-
- Influencer
- Posts: 11
- Liked: 1 time
- Joined: Feb 03, 2021 5:10 pm
- Full Name: Jonathan Wandless
- Contact:
Re: Veeam Backup Copy Job (GFS question)
Hi,
Thanks, look forward to hearing back.
Thanks, look forward to hearing back.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam Backup Copy Job (GFS question)
Hi Jonathan
You have configured to keep 14 days of restore points.
With the setting to keep 1 weekly full, you configured weekly synthetic fulls on the specific weekday.
If veeam would only keep the last fullbackup and delete all other, you wouldn‘t be able to restore the older incremental restore points which were created before the last fullbackup. An incremental restore point cannot be used for restores without it‘s fullbackup.
With a configuration of 14 days, you will have always backups for the last 14-21 days (2-3 fullbackups, 12-19 incremental). It‘s how a forward incremental chains works.
Thanks
Fabian
You have configured to keep 14 days of restore points.
With the setting to keep 1 weekly full, you configured weekly synthetic fulls on the specific weekday.
If veeam would only keep the last fullbackup and delete all other, you wouldn‘t be able to restore the older incremental restore points which were created before the last fullbackup. An incremental restore point cannot be used for restores without it‘s fullbackup.
With a configuration of 14 days, you will have always backups for the last 14-21 days (2-3 fullbackups, 12-19 incremental). It‘s how a forward incremental chains works.
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Veeam Backup Copy Job (GFS question)
Hello,
Basically, Fabian is right. We've checked this scenario in our lab and I can confirm that the behavior described in the first post is the behavior by design. GFS retention policy functions in combination with short-term retention policy. Weekly GFS full backups are also seeds for further incremental backups that are retained according to the short-term retention settings, therefore the full backups cannot be deleted before the short-term retention period is over. Please refer to this example to see how it works in forward incremental mode.
However, I'm not sure that I understand what is the purpose of such a configuration? If you need to leverage long-term retention, then it should exceed your short-term retention settings, for example you can opt for storing 3 Weekly backups and 14 days for the short-term chain. Alternatively, you can just disable GFS retention, backup chain will be switched to the forever forward incremental mode and backup copy will start to merge increments to the full backup and you will have just one full backup.
Thanks!
Basically, Fabian is right. We've checked this scenario in our lab and I can confirm that the behavior described in the first post is the behavior by design. GFS retention policy functions in combination with short-term retention policy. Weekly GFS full backups are also seeds for further incremental backups that are retained according to the short-term retention settings, therefore the full backups cannot be deleted before the short-term retention period is over. Please refer to this example to see how it works in forward incremental mode.
However, I'm not sure that I understand what is the purpose of such a configuration? If you need to leverage long-term retention, then it should exceed your short-term retention settings, for example you can opt for storing 3 Weekly backups and 14 days for the short-term chain. Alternatively, you can just disable GFS retention, backup chain will be switched to the forever forward incremental mode and backup copy will start to merge increments to the full backup and you will have just one full backup.
Thanks!
Who is online
Users browsing this forum: Bing [Bot], Egor Yakovlev, karazedbryan and 92 guests