Job Set for 14 Mount Points - 46 exist

[ejenner]

Ok, not certain this is the same question.

Some more possibly relevant info:

1. It's a Windows Agent job... so the options for configuring forward and reverse incremental aren't there.
2. The configuration of this job was copied from all the other Windows Agent jobs which all have 23 files stored (19 increments, 3 full, 1 meta data)
3. Not sure whether this makes any difference but it's the same on all our jobs, we have a weekly synthetic full. For the problematic backup we have 44 increments, 1 full, 1 meta data.

I can't see why with the same settings, different results would show at the repository?

[foggy]

Then what are the schedule settings for this job?

[MaxDes]

Worried about space. I have retention set to 7 days. There are 2 fulls and almost 2 weeks of incrementals listed in the folder containing the backup files... Why is it keeping two weeks worth? How can I remedy this?

[foggy]

Hi Marc, this is expected in case you're using a forward incremental backup method with periodic fulls. Please see above for details.

[MaxDes]

Any way to change the retention settings, then run a "cleanup" or something that automatically prunes (deletes properly) the extra backup files I dont want? 2 weeks is too much for a lot of these VMs and I only want one week, or 1 full + the rest of the week.

[foggy]

You can switch to a forever incremental mode - basically, disable the periodic full. In this case, Veeam B&R will maintain the number of restore points specified in the job settings by merging the oldest increment into the full daily.

[MaxDes]

Yeah I did that, but it doesnt just delete/merge, the stuff I need. it's like it requires a new full backup to actually do anything?

[veremin]

Have you tried to execute the job after you disabled periodic full backups (allowing job to function in forward forever incremental mode)?

[MaxDes]

Yes.
Trying again just to be see what happens, but it still had more than the retention the first time.

[foggy]

It will remove unneeded restore points once the latest part of the chain reaches the specified retention (i.e. you will have full + 6 increments in it).

[MaxDes]

I think the issue is that it needs the whole chain so it will have more than 7 because going back 7 doesn't get to the full backup before that. That sound right? Anything I can do there?

[foggy]

Yes, that's correct. Nothing you can do but wait a couple of days for when it reaches 7 with the latest full and 6 subsequent increments. Or you can just delete the older part manually if that is applicable.

[MaxDes]

Deleting the older part doesn't cause any issues? And by manually, do you mean on the file system level or within veeam?

[foggy]

If you keep the latest full and all the increments relying on it, you will be good - the older part of the chain can be safely deleted. You can do it on the file system and then clean up the UI with the help of remove missing restore points functionality.

[MaxDes]

Cheers, thanks