hat happens in the synthetic merge logic when there are 10 restore points, a job is triggered, and the disk is out of space to accept a further retention point?
does VEB have enough information to approximate the next restore point size before proceeding to move data to the repository?
Can the backup console have an option to perform an ad-hoc synthetic merge of the full with the oldest restore point if the answer to my question above is "VEB will fail the job"?
attempt to keep as many restore points as the backup target has space available?
Will more backup chain logic be implemented similar to B&R, for example reverse incremental, forward incremental with periodic synthetic?
Will VEB be enhanced in the future to make use of the scale-out backup repository in B&R v9?
Users browsing this forum: kva and 12 guests