A customer recently asked me how often they needed to do a “full” backup with Veeam so they would have a full backup in the event there was corruption of one of their differentials. With Veeam Backup’s synthetic backup, this scenario doesn’t exist!!
Veeam uses a synthetic backup which means EVERY backup gives you a full backup, at incremental speed, in a file called jobname.vbk. This .vbk file does NOT depend on any past differentials ( which have the extension .vrb).
The fantastic thing about synthetic backup is never taking the time and space penalty after your 1st backup for a full backup, with all the comfort of a traditional full backup.
The veeammeup blog has a good technical description of this wizardry of how synthetic backup works, which I duplicate here.
The way Veeam’s Synthetic Backup works is that after the first full backup, all subsequent backups are incremental, meaning just the changes from the last backup run, forever. Veeam Backup “injects” the changes into the full recovery file (.VBK) and then also saves any data replaced during this process into the reversed incremental changes file (.VRB). The .VBK file is always a full recovery file and the largest file in the directory. The .VBK file also has the most current modified date as it gets updated after each backup cycle.
The .VRB files do not change, as they contain the .VBK data blocks which were replaced by incremental data for that particular incremental backup run. To restore or roll-back to a particular date/time, all related .VRB files are applied to the .VBK file in the required order to get you back to that point-in-time.
The retention policy specifies how many of the .VRB files you want to keep, this also then corresponds to how “far” you can roll-back. If the retention policy is set to 14, then the 15th time the backup job runs it will delete the oldest .VRB file.
If you archive the .VBK and associated .VRB files as a set to tape, you can recover them back to disk if needed and import them into Veeam Backup to roll-back or recover to any point in time in that set.
So to be clear, if you accidently delete the .VRB file(s) you can get back to your full, as the .VBK is the “full” file. (This should never happen, but I had a customer who had an admin delete these files on their filer to free up some space before they knew the implications).
