Backup Copy doesn't function after VM MoRefID change

[gatorheelz]

Having an issue whereby BCJ does not function after vSphere re-install and MoRefID was manually updated in the VBR MSSQL database (there was a need to keep the existing backup chain). The Backup Job works without issue after MoRefID change. We were hopeful to keep the same BCJ chain as well (no longer a requirement), but even a new BCJ does not function in terms of processing new restore points.

Here is the output of new BCJ when created with Immediate or Periodic type:

Immediate:
6/22/2022 7:01:31 AM :: Some restore points were not processed
6/22/2022 7:00:39 AM :: Backup Job - VM (0 B) processing finished with warning at 6/22/2022 7:01:55 AM: 0 B transferred at 0 KB/s

Periodic:
6/22/2022 7:05:26 AM :: No restore points found
6/22/2022 7:05:28 AM :: Waiting for new restore points

We have manually moved the previous BCJ job data from the VCC, re-scanned the VCC repository and rescanned the repository on the VBR side.

This appears to be something new in VBR11a, as we have not encountered this with previous versions of VBR.

Case # 05487872

[Mildur]

Hi Gatorheelz

Manipulating the veeam backup configuration database without involving our support first is not supported.
If you have used our provided script (also unsupported, but provided as a courtesy), it would not work for cloud connect repositories. An active Full Backup is required for such backups.

If recommend to working with our support and see, if they can help you. It's not possible to repair your database over the forums.

Thanks
Fabian