Restore points: No. of *days* worth instead of no. of

kewnev · Post by **kewnev** » Jul 07, 2012 12:46 am this post

Is it possible to set up a number of *days" worth of restore points to keep?

The problem with having the ability to set just an actual number of restore points is that you may have days where you need to make many incremental backups, and this can reduce the number of days you can go back to restore from.

Thanks.

(Note, we use the Hyper-V version).

Post by **Vitaliy S.** » Jul 07, 2012 10:40 pm this post

Hello Nev, currently it is not possible, as retention policy is "measured" in actual restore points available, not days. Thank you.

cparker4486 · Post by **cparker4486** » Dec 03, 2012 11:59 pm this post

Hello,

Something I find strange and (a little frustrating) about B&R is that its retention policy is based on backup instances and not elapsed time. Why is that? Also, is this ever going to change?

I would, personally, much rather define a maximum age for backups than have to calculate the number of instances I expect to generate over that same time period.

Post by **Vitaliy S.** » Dec 04, 2012 8:02 am this post

Currently this is by design, but thanks for the feedback! Btw, can you please describe your backup schedule, so we could keep that in mind while enhancing our existing scheduling options.

sgravel · Post by **sgravel** » Dec 04, 2012 7:53 pm this post

It might be where we are coming from with our old software, but number of days makes sense to me too. Rarely do the business folks dictate that we need to keep 1,200 restore points. They talk in terms of needing to easily recover data going back 30 days, etc.

mongie · Post by **mongie** » Dec 04, 2012 8:35 pm this post

Not sure how it could be done, but AppAssure has a system where you can specifiy...

Keep 1 Point Every Day for X Days
then Keep 1 Point Every Weeky for X Weeks
then Keep 1 Point Every Month for X Months
then Keep 1 Point Every Year for X Years.

That sounds awesome to me, but again - not sure how you would go about that due to the way Veeam works. I'd expect it would require some sort of re-processing.

Bunce · Post by **Bunce** » Dec 05, 2012 4:19 am this post

Refer existing threads - requested continually in the past.

jim3cantos · Post by **jim3cantos** » Feb 04, 2013 6:24 pm this post

mongie wrote:Not sure how it could be done, but AppAssure has a system where you can specifiy...

Keep 1 Point Every Day for X Days
then Keep 1 Point Every Weeky for X Weeks
then Keep 1 Point Every Month for X Months
then Keep 1 Point Every Year for X Years.

That sounds awesome to me, but again - not sure how you would go about that due to the way Veeam works. I'd expect it would require some sort of re-processing.

+1

VDR (where we come from) had a similar approach that permits a much more flexible retention policy. You can have weekly, montly and yearly backups without having to store hundreds of restore points or defining several backups jobs for every policy needed (duplicating space requeriments for every aditional job, if I am correct)

jim3cantos · Post by **jim3cantos** » Feb 04, 2013 8:14 pm this post

...just found the correct thread

millerjohnson · Post by **millerjohnson** » Apr 01, 2013 1:22 pm this post

We have a stated requirement to keep offsite backups on a weekly basis for 6 month (26 weeks).

We have set the retention period to 26 in Veeam.

This works well until we have a need to do an additional back. Major system or data change and need to have pre and post change kept offsite. Now I have 26 restore points but two additional backups on the same day in addition to the weekly I will have 3 backup jobs for that week.

Once it reaches the 26th backup job it will start to lop off the oldest and I am no longer fulfilling my 6 month requirement.

How do you enforce retention time in days?

Post by **Vitaliy S.** » Apr 01, 2013 1:35 pm this post

As a workaround you may want to use additional, separate backup job prior making any changes to your production system. In this case your main backup job will not be affected by having extra restore points.

markwo · Post by **markwo** » Jun 12, 2013 1:17 pm this post

I would love to see this as well.

I love Veeam, but not being able to set a retention period in number of days was something that really stuck out at me when configuring the product.

chrisdearden · Post by **chrisdearden** » Jun 12, 2013 3:05 pm this post

V7 copy jobs (with gfs retention) should solve this for you.

Post by **dellock6** » Jun 13, 2013 11:21 am this post

But only on the secondary backup, not the primary...

Luca.

chrisdearden · Post by **chrisdearden** » Jun 13, 2013 12:12 pm this post

True - nothing to stop primary and secondary being on the same storage though

Post by **dellock6** » Jun 14, 2013 6:58 am this post

I thought about this trick too, but anyway it requires two I/O operations to create a "day-based" retention.

chrisdearden · Post by **chrisdearden** » Jun 14, 2013 7:35 am this post

but only 1 against the VM

lee.wilmott · Post by **lee.wilmott** » Sep 25, 2015 9:34 am this post

We are using Veeam Backup & Replication 8.0.0.2030.

Currently the retention policy allows you to keep 'x' number of restore points.

I would like to see the retention policy extended so that you could keep the restore points for 'x' number of days. (Perhaps this could be extended further to 'x' number of days/weeks/months/years - whatever).

The reason I ask this is because our company policy dictates that we will keep restore points for 32 days. However, there are scenarios where we do not adhere to our own policies. For example, if we are performing a software update, data migration or significant configuration change then we take additional backups. In fact, we could take a backup before our software update and take another one immediately afterwards. Because we've taken additional backups we no longer have 32 days of restore points as the older restore points have been replaced by the additional backups that we have performed.

Please, please, please you could consider adding such functionality?

By having his functionality it allows for a 'set and forget' philosophy and ensures that we're not breaking our own policies.

Kind regards,

Lee

Sep 25, 2015 12:26 pm

You need to give Quick Backup functionality (http://helpcenter.veeam.com/backup/80/v ... ackup.html) a try, it let's you do exactly that - additional backups outside of set retention policy.

lee.wilmott · Post by **lee.wilmott** » Sep 25, 2015 1:54 pm this post

ssimakov,

Many thanks for your reply.

Without sounding stupid, what are the steps I need to perform to initiate a "Quick Backup"?

I cannot find the term "Quick Backup" anywhere within the console itself.

Kind regards,

Lee

Post by **foggy** » Sep 25, 2015 2:15 pm this post

Lee, you just right-click the VM under the Virtual Machines node and click Quick Backup.

lee.wilmott · Post by **lee.wilmott** » Sep 25, 2015 3:41 pm this post

Hi foggy,

That's great thank you. I couldn't for the life of me find it. Thank you.

Lee

kewnev · Post by **kewnev** » Feb 19, 2020 1:28 pm this post

Going by the release notes, would I be right in saying that this feature is now available in the latest version?

Feb 19, 2020 1:38 pm

Hi,

Correct.

Here's the complete list of new features > What's New in v10 (16 pages)
And here's all v10 documentation including the User Guide.

Also, note that GFS Retention Policy is now available for primary backup jobs as well.

Thanks,
Oleg

kewnev · Post by **kewnev** » Feb 20, 2020 3:55 am this post

Thanks Oleg,
It was 8 years ago that I asked about it ... glad it eventually came

R&D Forums

Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

[MERGED] Why is the retention policy not based on time?

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

[MERGED] Restore points based on retention time in days?

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

[MERGED] Feature Request: Retention Policies by Date Range

Re: Feature Request: Retention Policies by Date Range

Re: Feature Request: Retention Policies by Date Range

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Re: Restore points: No. of days worth instead of no. of

Who is online