I have indeed lower the number of regular restore points and now it is running a transforming full backup process.
I will now wait and see how the process will work the next months. But finally see a full backup creation

I hope this isn't hijacking the thread, but I'm trying to get a firm handle on the use of disc space and how much is needed in our "live" environment. By all means, if this thread needs to be moved or modified as a new thread, I hope I haven't done anything in poor action.

Real quick background, we're using GFS for some of our servers currently, hoping to move to the system for everything. We are looking to have weekly backups for the current month, a monthly backup for each month in the last 12, and a yearly backup to be held for seven years. I'm comfortable with our retention points for the backup copy jobs and archive period setting for each period.

My issue is with the space needed. I have four weeks of weekly backup copies, 3 months of monthly backup copies, and seven days of daily backup copies. By my count, that's seven full size backup files of the server, our dailies are incrementals, not rolled up into a full each day, that's why they aren't included.

If I want to keep space for other jobs, as well as running weekly and monthly backup copy job runs, is it possible to remove completed monthly jobs from the storage area to an off-site location that's not connected, without compromising the ongoing yearly roll-up or do I only need the latest monthly job to be converted into an annual and the latest weekly job to be created for the monthly?

Tom, you do not need previous GFS restore points to create subsequent ones, so you can safely offload them to another location. Just keep in mind that corresponding records will still be displayed in Veeam B&R console until wiped out from the database according to retention.

Im working with Veeam Backup and Replication for the first time and Im having trouble unterstanding how to configure the archive job.
We have a Backup Job which runs daily and is set to 14 Restore Points. Active full backup is set to monthly.
This seems to be fine so far.

What Im trying to do for the archive Job:

There should be 4 weekly restore points for the month previous to the current month and 1 monthly restore point for the month before this. After that there are only yearly backups.

Does this work like this:

Restore Points to keep: Does this affect all weekly/monthly etc. restore points? How can i calculate what amount is needed?

I have a backup copy job with 7 day interval, 2 restore points, and weekly GFS setup. Over the past 2 sundays, they day i expected it to generate a weekly full, it has failed to do so. No indication why. I've just changed it to start today, both before and after the current time, and changed the interval to 1 day, yet it still won't start a new GFS transformation. Am i doing something wrong?

I've read the v8 User Guide on this a few times, I just need more help.

Presently my on-site backups use a Simple Retention Policy. I run a Full backup once per month, and an Incremental daily for rest of the month. My retention policy keeps 365 restore points, so theoretically I end up with 12 Full backups per year, along with around 30 daily backups for each month.

I am now adding Cloud Connect into the picture, and it isn't feasible to store this way off-site. I need to configure the GFS Retention Policy for Backup Copy Jobs. I am focused on this screen:

What I would like to have at the end of a year:
30 days of daily restore points, one for each of the previous 30 days.
Weekly restore points for the previous 12 weeks
Monthly restore points for the previous 12 months
1 Yearly

After running this way for a full calendar year, this is what I'd want to see on Jan 1:
December – a restore point for every day, 30 total
Oct, Nov – weekly restore points, 8 total
Jan – Sept – a monthly restore point, 9 total

How do I configure the screen above to achieve this?
And while at it, Does this make sense?

Makes perfect sense, however "what you would like to have at the end of a year" does not 100% correspond to "what you'd want to see on Jan 1" (different number of weekly and monthly backups). Basically, you need to set retention of 30 restore points and the desired number of weeklies, monthlies and yearly backups in the corresponding fields.

Same full backup can be marked as weekly, monthly, quarterly and/or yearly, so you will not have duplications.
Also, please read the topic where your post has been merged and ask additional questions if you have any. Thanks!

OK, so if I follow, "restore points to keep" is dailies. 30 restore points gives me a month of dailies, then on top of that I have the weekly, monthly and yearly. The confusion for me is it seems like I'd have more 30 dailes, plus the additional weekly and monthly and yearly, which might come out to something like a total of 48 restore points.

Thanks much for the feedback folks. And I did read this whole thread before I started mine, FWIW.

I will be bringing a Cloud Connect repository online in the next day or so, and I need to setup the Backup Copy job in v8. I have two questions:

Virtual Machines selection - At the Virtual Machines screen, I’m not clear on the differences between From Infrastructure, From Backup, and From Jobs. Are these just different methods for getting to the VM? If you select the same VM regardless of method, is it the same outcome/result?

Existing Restore Points - When the Backup Copy job runs for the first time, will it sync all the available local restore points to the cloud, while observing the defined GFS parameters? I have a Full backup and a couple weeks of daily Incrementals, all of which I’d like to get uploaded to the cloud repository. It is about 60GB, and I expect it will take about three days to upload.