Skip to main content
Solved

'Four-eyes' authorization broken after configuration restore?

  • June 29, 2026
  • 3 comments
  • 16 views

Hi there, I am still looking to find the solution out there, but it may be much quicker to ask.

Scenario is my old VBR server was on VMWare, and a backup of the config was taken.

The backup has been recovered on a brand new VBR server, now on HyperV, different server name and IP. The old server is long gone.

Restoring the config worked great, but now I cannot pass any ‘four-eyes’ approvals as the users that were on there, do not exist on this new server. I added the users to this new server, using the same usernames, but they do not have access to this new VBR server.

If I add the users to the server as admins, that itself kicks off another four eyes approval.

So, how do I get around this? Is there a way to disable that feature when dealing with a new box? Thanks in advance!

Best answer by Chris.Childerhose

You typically need to disable it before the configuration backup, but during restore of it the 4-eyes should be disabled by default.  Leave it off until you sort out your users.

If that does not work, then you need to contact support to get them to manipulate the DB to turn it off so you can work to update users.

3 comments

Chris.Childerhose
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • Answer
  • June 29, 2026

You typically need to disable it before the configuration backup, but during restore of it the 4-eyes should be disabled by default.  Leave it off until you sort out your users.

If that does not work, then you need to contact support to get them to manipulate the DB to turn it off so you can work to update users.


  • Author
  • Comes here often
  • June 29, 2026

Thanks, I did expect the restore to turn it off - it didn’t so it remains on. It’s impossible to turn it off if it was a disaster scenario to be fair, so I did expect this to automatically turn off like the MFA. I will log a ticket thanks.


Chris.Childerhose
Forum|alt.badge.img+22

Thanks, I did expect the restore to turn it off - it didn’t so it remains on. It’s impossible to turn it off if it was a disaster scenario to be fair, so I did expect this to automatically turn off like the MFA. I will log a ticket thanks.

No problem.  Yeah, typically it does turn off with config restore, from what my experience is.  Hopefully, support gets you sorted.  Let us know.