Jump to content

Recommended Posts

Posted

We've got VEEAM at my new school, and my predecessor set up a backup policy which for the sake of politeness, we'll refer to as "comprehensive".

 

The 'backup copy' jobs to the offsite store are set with grandfather-father-son, and that is doing what I would expect, by which I mean I have backupname_W.vbk and backupname_M.vbk files going back a few months, and only .vib files for the last week. On the VEEAM box itself, I have daily incremental and monthly active full backups being created, but - and here is the bit I want your thoughts on - it is leaving the daily incrementals on the disk as well, meaning I have 3 .vbk files and around 50 .vib files for each server.

 

Is this normal/correct or is something amiss?

Posted
Yeh the daily incrimentals get left on there until it runs up against your retention policy settings eg. "only keep 30 copies" or "keep infinite copies but start deleting when you get to 100Gb of drive space"
Posted
Yeh the daily incrimentals get left on there until it runs up against your retention policy settings eg. "only keep 30 copies" or "keep infinite copies but start deleting when you get to 100Gb of drive space"

 

Thanks, that makes sense. Except I have 52 items in the folder for most servers - that's one .vbm file, three .vbk files and 48 .vib files - despite having the backup set to keep 30 restore points. Is there another retention policy somewhere telling it to keep 30+ anyway since there is the disk space available?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...