Suggestion - Confirmation before Active Full Backup

[friopel]

Hi,

I have a suggestion : We have had an issue where, in B&R, we wanted to click "Retry" on a failed job, and instead, we clicked my mistake on the button next to it, which is "Active Full". The job, which is close to 5TB is size, started right away. We tried to stop it, but that broke the incremental chain, and we ended up having to do the active full backup, which took about a week to do, because some of the larger VMs failed a couple of times.

A simple "Are you sure you want to perform an Active Full Backup" prompt would've prevented that!

Thanks!

[davecla]

+1

This would be really handy feature. A month or so ago I accidentally kicked off a full Full Backup Copy job, that took 12 days.

[veremin]

Thank you, guys, for submitting your request; appreciated.

If you find yourself in similar situation, you can try to stop running job, remove the latest inconsistent backup from disk (GUI option) and re-run the job.

Thanks.

[friopel]

Hi

I cannot seem to find that option in the GUI, can you guide me?

Thanks!

[foggy]

Vladimir is most likely meaning one of these options.

[dimaslan]

I have had this issue only once so far but it is not hard to have it happen again.
The Active Full button is right next to the Retry button. Since we are 99.9 % of the times remoting to the BDR servers, it is not uncommon for the connection speed to cause the mouse to jump when moving it; Luckily, I misclicked having selected a very small job otherwise I would have had an issue on my hands.
Can you please add a question popup when the Active Full button is pressed?
Thank you.

[foggy]

Dimitris, thanks for the feedback. Though the request makes perfect sense, triggering active full is actually not a big issue, you can stop the job immediately, delete incomplete restore point from disk and "forget" it in Veeam B&R UI.

[odge]

Thank you, guys, for submitting your request; appreciated.

If you find yourself in similar situation, you can try to stop running job, remove the latest inconsistent backup from disk (GUI option) and re-run the job.

Thanks.

We'll I have tired that, deleted the partial VBK file.
Removed it from the backups properties list.
And when it starts again, its trying to create a VBK.

Its worth noting I have my repository set to individual files per VM.

Sigh... it was on 10% of a week long, and I though tthis would be faster, but I seem to be back at scratch.

[dimaslan]

I'd like to add to that, it may be that this is not noticed at all and right after the click one disconnects or loses connection to the backup server. Having a full backup run could cause real issues, depending on the time, repository free space but also the time it will take to notice.