How does VEB handle incomplete incrementals in the repo?
In case of disconnect or under any other circumstances where repository becomes inaccessible backup job starts a retry cycle (restarts every 10 minutes during the next 23 hours) and will clean up the incomplete restore point once repository is connected. Same behavior for merge process
f so, are there any tips/tricks/hints to get this to succeed on that first big backup (e.g., pre-seeding)?
Mike is right, for local and shared targets you should be able to create a local copy (i.e. on internal drive or USB stick) and then move it to shared folder. Reconfigured job with the changed destination should be able to pick this restore point. Note that this not going to work with Veeam repository
no performance impact to anything else I'm doing on my machine. It looks like you guys nailed the throttling algorithm
Happy to hear it again and again. Thank you
Do you know if a feature request has already been submitted for "restart interrupted backups from where they left off"? If not, do I just start a new thread in this forum to submit a feature request?
Added you to the list