Critical bug in VBR Console causing VMware backup jobs to become unscheduled

[Seb.pythoud]

Hi everyone.

We’ve identified a bug in the Veeam Backup & Replication Console that can lead to VMware backup jobs becoming unscheduled — effectively leaving VMs unprotected for several days (as it happened in our environment). Is anyone reproducing this issue ? (VBR 12.3.2.x)

Our setup includes VMware backup jobs configured with a daily automatic schedule and a secondary target (Backup Copy job).

The issue is reproducible with the following steps:

1) Edit an existing VMware backup job.
2) Go to the Secondary Target tab, select the Backup Copy job, and click Edit.
3) In the Backup Copy job window, click Cancel without making any changes.
4) Go to the Schedule tab — notice that the Daily option is now unselected.
5) Go to the Summary tab and click Cancel to close the job editor.

The job is now unscheduled, even though no change was made and no warning or confirmation was displayed.

Impact:
This behavior silently disables the backup schedule, leading to unprotected VMs without any user notification.

Case open : 07852935

[david.domask]

Hi Seb.pythoud,

Thank you for the report and for sharing the case number.

I was not able to reproduce on 12.3.2.3617 with the above steps, however I see Veeam Support is requesting logs and will review the behavior.

Are you able to reproduce this behavior on-demand in your environment? If so please note it in the case as it will likely help Support to narrow down the issue.

[Seb.pythoud]

Yes, I was able to reproduce it on 2 different VBR.
I've sent a quick video to support to show it.

[DaStivi]

hi,
what secondary job do you have?
I can't reproduce it on 12.3.2.3617 (nor V13)

in v12 i've a "backup copy" to my serviceprovider environment (cloud connect target) and 2x NetappOntap Storage Snapshot options...

in v13 i've a "backup copy" to S3.

I've tested a couple of times, "clicking" differently, like gooing directly to sheduled tab, instead of using, next/next... but doesn't matter its still sheduled all the time...

might be something specific

[Gostev]

@Seb.pythoud this is exactly why in the forum rules (which were displayed when you click New Topic) we ask not to bring any issues to the forum until you have a confirmation from support that this is a product bug as opposed to a corner case related to the specific environment or specific settings. Such discussions like above just waste the PM team time for nothing.

Please please please don't just ignore the forum rules with your future contributions to this community. Let out small team focus on what really matters.