new VBR v13 and protection group issues

[ortoscale]

Hi.

i'm getting this error when trying to apply protection group policy via new VBR server.

Failed : Failed to send backup job configuration to _MACHINE_ Error: Failed to generate certificate for _MACHINE_ : host is managed by another backup server razor

is there any way to force machines to start using new VBR v13?

would running this on old v12 Veeam help?

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
ProtectionGroupIgnoreOwnership DWORD=1

any other suggestions?

[david.domask]

Hi ortoscale,

The config parameter should still be valid, but the normal way would be to use the Uninstall Everything option on the original backup server (if it still exists) and then let discovery run as normal on the v13 backup server.

If you elect for the config parameter, be sure to remove it once you're done with moving to the v13 backup server.

[robnicholsonmalt]

normal way would be to use the Uninstall Everything option on the original backup server

Not usually possible in a disaster scenario. I've just rebuilt my lab set-up after my lab server failed. I've installed v13 whereas before it was v12. I didn't feel that restoring a v12 backup configuration into v13 was a sensible thing to do (would have have worked?)

Also the "HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication" key doesn't exist on the server backed up by the old server. Just these keys - do I have to create the Veeam Backup and Replication key? These are the keys present:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Agent]
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Agent for Microsoft Windows]
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Installer]
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam EndPoint Backup]

Also, if Veeam can detect the situation, why can't it offer a solution in the console? It's got access to the target server.

[robnicholsonmalt]

Few minutes later... I've added this key and no difference:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
"ProtectionGroupIgnoreOwnership"=dword:00000001

Also checked on a new working server and the Veeam Backup and Replication key doesn't exist there either.

[david.domask]

The configuration parameter will need to be created, it is not present by default yes.

As far as I'm aware the parameter is still respected, so if you're seeing different behavior @robnicholsonmalt, please open a Support Case and let Veeam Support review the debug logs (use the 3rd radio button to export logs from the Backup Server itself after reproducing the issue; note the protection group you tested with)

Share your case number once created, thanks!

[robnicholsonmalt]

I know I'm being pedantic but terminology is important with registry. HKEY_LOCAL_MACHINE\SOFTWARE\Veeam is the root key and Veeam Backup and Replication is a sub-key, but they're both keys. ProtectionGroupIgnoreOwnership is a value of type DWORD with value 1.

Anyway, I tried adding the value to all sub-keys including the missing one:

Windows Registry Editor Version 5.00

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
"ProtectionGroupIgnoreOwnership"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Agent]
"ProtectionGroupIgnoreOwnership"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Agent for Microsoft Windows]
"ProtectionGroupIgnoreOwnership"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Installer]
"ProtectionGroupIgnoreOwnership"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam EndPoint Backup]
"ProtectionGroupIgnoreOwnership"=dword:00000001

Rebooted the server) and no difference on rescan - same warning:

Code: Select all

08/04/2026 11:00:26 Warning : Failed to connect to rivendell.middle-earth.co.uk Details: Failed to generate certificate for rivendell.middle-earth.co.uk: host is managed by another backup server ELROND.middle-earth.co.uk

This is a lab/community edition so I don't tend to get much joy with raising support tickets but I will do to get the case number after I've tried a few more things. For example, there is the option to remove everything... I've taken a snapshot of the target backup.

Later... couldn't remove either as managed by the old server. Neither could I uninstall everything...

[robnicholsonmalt]

Case #08052584 submitted.