Fwd Incremental w synth FB is weekly - what if?

[cpfleger]

We all know that with a primary backupjob running on forward incremental mechanics one needs to have at least one weekly full backup to leverage synthetic fulls (useful eg for fast cloning).

Now what if:

. what happens, when one disables the backup job before the new weekly synthetic full backup run can start (let's say this would be scheduled for each Saturday) and re-enables the job again maybe on Monday the next week? Will then the chain simple be continued against the incremental backup from Friday with another VIB on Monday - skipping the creation of the weekly synthetic VBK?

. what happens, when one disables the backup job after the first run (which generates an active full backup, let's say this was a Saturday) and re-enables it four weeks later just before the original schedule would trigger that particular job?
Will there now be a new synthetic full being generated?
Or just a synthetic full backup capturing all the changes in between that 4 weeks passed by?

. Is the behaviour the same when using Backup Copy Jobs with GFS (I would guess so as the mechanics are supposed to be the same)?

Because VBR User Guide (https://helpcenter.veeam.com/docs/backu ... ml?ver=110) tells us:

Veeam Backup & Replication automatically triggers a backup job session to create a synthetic full backup, even if a regular backup job session is not scheduled on this day.

Maybe someone knows so that I do not have to wait that long (playing around with the system date is not always soooo good...)

Background: trying to figure out if there is a way to both leverage fast cloning with Immutability on Hardened Linux Repositories to get a function similar to S3/S3c capacity tier (User Guide: [/url]https://helpcenter.veeam.com/docs/backu ... ml?ver=110 [/url]) regarding GFS with a longer period between the fulls (monthly):

For example: the backup repository immutability period is 10 days; the GFS backup file lifetime is 3 years; the backup file will be immutable for 3 years; the increments from this full backup file will be immutable for 10 days from the moment of the last increment creation.

Or will v12 add a feature to add (or extend) Immutability with Linux Hardened Repo only for selected backups - GFS ones?
As there is a Powershell CMDLET to set the Immutability expiration date (Set-VBRImmutabilityLockExpirationDate - https://helpcenter.veeam.com/docs/backu ... ml?ver=110) I believe that could also be introduced into the GUI to have a longer protection only for GFS instead for the whole chain.

Regards!

[Andreas Neufert]

With SF you can mark specific week days for SF processing.
The first job of this day will process a SF.
If you disabled the job or you missed it, then on next day or later there will be only a SF created when this day is marked as a SF day in the scheduler.

The idea is to avoid that a SF is created on a working day that could affect roduction or so.

If you want to fix the situation you temporarly change the SF days to the current day and start the job (reversing the setting right after the job started).

In the end you can end up with an old SF and a lot of Incrementals that depend on each other.

Retention processing will only delet old data if the last backup restore point of a chain is out of the retention.
The product works that way for over 10 years.

Immutability processing will extend the Immutability as needed for dependant backup files.

[Andreas Neufert]

BTW. you can test the SF chain processing in a lab by just changeing the computer time clock manually, scheduler will pick it up within 2 min. Manual runs instantly (without Veeam service restart).

[cpfleger]

Thx Andreas!