-
- Veeam Legend
- Posts: 1210
- Liked: 418 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
V12 feature reuqest - make Validator MFA compatible
Hello,
Veeam Backup Validator is currently not able to run when the user account who starts it has MFA enabled. It just fails with:
"Failed to process storage. Failed to validate files."
Just by setting the account i use as a service account it immediately works.
Validator should inform the user about this or at least it should be mentioned in https://helpcenter.veeam.com/docs/backu ... ml?ver=120.
Markus
Veeam Backup Validator is currently not able to run when the user account who starts it has MFA enabled. It just fails with:
"Failed to process storage. Failed to validate files."
Just by setting the account i use as a service account it immediately works.
Validator should inform the user about this or at least it should be mentioned in https://helpcenter.veeam.com/docs/backu ... ml?ver=120.
Markus
-
- Product Manager
- Posts: 14973
- Liked: 3159 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello Markus,
agree, makes sense. Thanks for reporting.
just curious: what's the reason to use the validator as V12 allows to schedule health checks independent from the job run.
Best regards,
Hannes
agree, makes sense. Thanks for reporting.
just curious: what's the reason to use the validator as V12 allows to schedule health checks independent from the job run.
Best regards,
Hannes
-
- Veeam Legend
- Posts: 1210
- Liked: 418 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hannes,
support told me to do this - case 06258440
support told me to do this - case 06258440
-
- Product Manager
- Posts: 14973
- Liked: 3159 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello,
I tried it out and cannot reproduce it. I switched my backup service to run as domain user instead of LOCAL SYSTEM and enabled MFA for my user. To get the validator working with the new per-machine chains, I used this code (KB article is in progress)
It works fine for me. So we need more information how you got the "Failed to process storage. Failed to validate files." error (we can post-pone that until a time when the other issues are fixed).
Best regards,
Hannes
I tried it out and cannot reproduce it. I switched my backup service to run as domain user instead of LOCAL SYSTEM and enabled MFA for my user. To get the validator working with the new per-machine chains, I used this code (KB article is in progress)
Code: Select all
$backup = Get-VBRBackup -Name "BJ-Nano"
$child_backups = $backup.FindChildBackups()
ForEach ($sub_child in $child_backups) {
$id = $sub_child.Id
$name = $sub_child.name
Write-Output "Processing VM $name $id"
cmd.exe /c '"C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Validator.exe" /backup:'$id' '
}
Best regards,
Hannes
-
- Veeam Legend
- Posts: 1210
- Liked: 418 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello Hannes,
first of all our backup server is not in the domain and runs as local system. Is that a problem?
Markus
first of all our backup server is not in the domain and runs as local system. Is that a problem?
Markus
-
- Product Manager
- Posts: 14973
- Liked: 3159 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello,
ah, wrong understanding on my side...
No, LOCAL SYSTEM is the default and recommended in general (exception: remote SQL server with Windows authentication). Workstation / domain should make no difference.
My machine is domain joined and now I was able to get an error. Not exactly your error, but a "VM is unavailable". When I set the account to "service account" in the user settings, then it works.
The case sounds like you are using an upgraded per-machine chain, right? What exact command do you use?
Thanks,
Hannes
ah, wrong understanding on my side...
No, LOCAL SYSTEM is the default and recommended in general (exception: remote SQL server with Windows authentication). Workstation / domain should make no difference.
My machine is domain joined and now I was able to get an error. Not exactly your error, but a "VM is unavailable". When I set the account to "service account" in the user settings, then it works.
The case sounds like you are using an upgraded per-machine chain, right? What exact command do you use?
Thanks,
Hannes
-
- Veeam Legend
- Posts: 1210
- Liked: 418 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello Hannes,
yes, upgraded chains. Just basic Veeam.Backup.Validator.exe /file:backupfile1 /file:incremental1 /file:incremental2
Markus
yes, upgraded chains. Just basic Veeam.Backup.Validator.exe /file:backupfile1 /file:incremental1 /file:incremental2
Markus
-
- Product Manager
- Posts: 14973
- Liked: 3159 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: V12 feature reuqest - make Validator MFA compatible
Hello Markus,
ah okay, thanks!
Best regards,
Hannes
ah okay, thanks!
I just wanted to let you know, that we documented that limitation. https://helpcenter.veeam.com/docs/backu ... ml?ver=120 and I will talk to my colleagues how we can improve that.not able to run when the user account who starts it has MFA enabled
Best regards,
Hannes
Who is online
Users browsing this forum: SnakeSK and 100 guests