Hi, if you set both to active and synthetic full to happen on the same day, then only active full will happen. With these settings above, synthetic full will never happen. I would recommend setting up the schedule for monthly (or even more rare) active fulls. Thanks!
Full backup will be built by pulling the entire VM images from the production storage, rather than synthetically using previous full backup and following incremental backups.
in the day of month setting x Active full backup we have a big file
In the backup dir we see for any job 2 big file, 1 think is "the maste" and another made by "active.."
Synthetic and Active full backups will consume the same storage space on your backup repository. The only difference between these options Anton has already described in his post above.
This depends on your retention policy settings, but if you enable "Transform previous full backup chains into rollbacks" you will end up in having only single VBK file at any point of time.
Vitaliy S. wrote:This depends on your retention policy settings, but if you enable "Transform previous full backup chains into rollbacks" you will end up in having only single VBK file at any point of time.
The number of fulls (VBK files) in the job folder also depends on your retention settings (how many restore points do you keep) and with forward incremental backup mode can vary from day to day. Please see this topic for descriptive explanation.
Also please note, that new active full backup resets the chain of increments. So even if you have transform option enabled and perform an active full, a previously used full backup file will remain on disk until it is automatically deleted according to retention settings.
Would Veeam consider adding the Transform option to Active full backup jobs? It would have the advantage of the Full backups being more reliable, but saving space because older full backups could be transformed into RBKs...