But when you say "incremental", it is increment from the last full backup data set ?It seems there are some misunderstandings here. There is no reduced load on the production VM when comparing forward incremental vs reverse incremental. The first full will create exactly the same load, after this Veeam will leverage changed block tracking and extract only changed blocks = equal load from either forward/reverse incremental.
When restoring from the latest restore point, there is no benefit to restore from VBK versus a chain. The reason is Veeam metadata. This means sure the VBK contains all the blocks needed, but if you restore from a forward incremental chain, we don't read the entire chain, only the exact blocks needed to restore the latest restore point, but all of the changed blocks that are not needed will not be read/processed.
So if the retention period is 21 days, it will have full + 21 increments with each of the 21 increments being critical component to recovery of the latest backup ?
Example if today is 10th April, I would have "synthetic" full backup at 15 Feb with 21 increments ? If one of the increments (like 1st April was lost or corrupted), can I still recover 9th April ?
Then if there would be daily "synthetic" full due to the retention period, I really do not see the point of wasting that resources to create a full backup that old ?
Statistics: Posted by zadrian — Apr 07, 2025 3:12 am
