-
- Service Provider
- Posts: 12
- Liked: 2 times
- Joined: Sep 30, 2021 11:28 am
- Full Name: Benny G.
- Contact:
Issue with Restoring config on consoles with MFA enabled
I will try keep this short but we have just come across an issue when restoring Veeam config onto a new server (part of a migration), when the B&R server is not part of the domain.
When MFA is enabled, the restore/migrate process completes fine but then you get a 'Account cannot be found' message when trying to load the B&R console.
Much scratching of the head and I have worked out the problem.
The account SID is stored in the database table dbo.backup.security.accounts.
To regain access, I simply edited the account SID to match the account on the new server we have migrated to, and also updated the NT4_Name column as the server name changed too.
I hope this helps someone in the future, and I think it is something that Veeam maybe need to fix/account for when restoring configuration to a new server.
Not sure if updating this table causes any other problems but so far backups are going through successfully.
When MFA is enabled, the restore/migrate process completes fine but then you get a 'Account cannot be found' message when trying to load the B&R console.
Much scratching of the head and I have worked out the problem.
The account SID is stored in the database table dbo.backup.security.accounts.
To regain access, I simply edited the account SID to match the account on the new server we have migrated to, and also updated the NT4_Name column as the server name changed too.
I hope this helps someone in the future, and I think it is something that Veeam maybe need to fix/account for when restoring configuration to a new server.
Not sure if updating this table causes any other problems but so far backups are going through successfully.
-
- Product Manager
- Posts: 14963
- Liked: 3158 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
Hello,
yes, that makes sense if the SIDs don't match anymore. There is another workaround from the release notes (temporarily switch to community edition which does not support MFA)
Best regards,
Hannes
yes, that makes sense if the SIDs don't match anymore. There is another workaround from the release notes (temporarily switch to community edition which does not support MFA)
Best regards,
Hannes
-
- Service Provider
- Posts: 12
- Liked: 2 times
- Joined: Sep 30, 2021 11:28 am
- Full Name: Benny G.
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
I did try this, but even on community edition it shows 'account cannot be found' when you try to login.
-
- Product Manager
- Posts: 14963
- Liked: 3158 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
hmm okay... then thanks again for sharing, I will check with my colleagues on how we can improve that.
-
- Chief Product Officer
- Posts: 31964
- Liked: 7436 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
@Egor Yakovlev let's please look at this issue more closely, apparently still a problem in 12.1
-
- Product Manager
- Posts: 2589
- Liked: 712 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
Investigating.
-
- Product Manager
- Posts: 2589
- Liked: 712 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Issue with Restoring config on consoles with MFA enabled
Confirmed this behavior in case when [MFA is enabled] + [Configuration Restore wizard mode is "Migrate"] + [New server does not have that SID](workgroup or non-original domain).
We will definitely fix that in one of the future updates, but for now it is safe to use "Restore" mode instead or follow with steps in KB4477.
/Thanks!
We will definitely fix that in one of the future updates, but for now it is safe to use "Restore" mode instead or follow with steps in KB4477.
/Thanks!
Who is online
Users browsing this forum: Bing [Bot], d.artzen and 123 guests