VBR Migration to New Server Error when accessing User and Roles

Was the old server domain joined and is the new server also domain joined? All the same users exist?

Even then, it shouldn't stop the users and roles setting from opening. Have you created a support ticket for this issue? 

Not sure if versions matter but support will be best to help with this.

Both are domain joined and the users are the same for both.

I have not opened a support ticket yet. I’m trying a couple of thing to see if this error would go away. If not, I’ll check with support.

Thanks!

If you do go with support report back the fix once you know.

Because of the complexity of what you did...best to go through Support as Chris suggested. Let us know what they find & the resolution. 

during migration or restore of configuration backup (at the end) is showing that credentials are restored properly. 

missing credentials are domain credentials or local?

if domain, i can image that connection was missing, so that could be the problem

I had a similar issue when I migrated a customer from MSSQL to PGSQL with a domain-joined construct (which I don’t recommend anymore, different topic).

The support was able to help so that’s absolutely the best way to go.

How did you do the migration? With the configuration restore?

The error is about Veeam being unable to decrypt the secrets in the configuration database -- Veeam uses a salt for a few versions now in addition to the machine key on the original server to encrypt secrets in the database -- if the database was migrated manually (i.e., just moving the database files), this will not work as the salt + machine key are not included this way, and the new server cannot decrypt the secrets.

Use this process only to migrate the VBR server to a new server: https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120

That is a great question. I never considered that a manual database migration might have been attempted, and that certainly could explain this error. 

I did not manually moved the DB. As pointed out, I have followed the instructions on https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120.

I opened a ticket with support a couple of days ago and we’re still figuring out the issue. We will do a remote session and will update you folks. 

Thanks again for all your feedback! 

Sounds good ​@spider32 . Keep us posted what they find out.

Hi ​@spider32 - did you get an answer to your question and if so can you please share so we can mark an answer as “Best Answer” even if it is yours.

Great glad to hear you got things fixed up.

Glad to hear Support got you sorted ​@spider32 👍🏻