V12.2:after upgrade to Veeam V12.2 we are not able to perform backup for our domain controller via GMSA

[apolloxm]

Case ID：07416798

after we upgraded to V12.2 we are not able to backup our domain controller with gMSA service account.

Unable to subscribe to guest processing components: Failed to detect Oracle installation.
Failed to create a process token for MSA account: , domain:
Win32 error:Access is denied.
Code: 5. Failed to detect Oracle installation.
Failed to create a process token for MSA account: , domain:
Win32 error:Access is denied.
Code: 5


The case has been escalated to advanced technical support team. The following log entries confirm that this is a known issue where post upgrade to version 12.1 or 12.2, backup job starts failing with the error "Failed to call RPC function 'Vss.DetectOracleInstallation". (Please note that RPC call ExploreOracleInstances in v12 was replaced by RPC call Vss.DetectOracleInstallation in v12a.)

The support recommended workaround is to switch to domain admin account instead of the gMSA.

We can't accept such bad solution as Veeam already supported the gMSA and for the security policy we are not allow to do like this.

[david.domask]

Hi apolloxm,

Thank you for sharing the case number, and sorry to hear about the issues you're experiencing. The issue identified in the case (641539) is not specifically a Veeam issue, but an issue that appears when there is a misconfiguration with gMSA -- previously, this error was handled as a warning, and now it currently an error.

Ultimately, the gMSA configuration should be reviewed, but will discuss internally on other options to help on your situation.

[apolloxm]

Hello David,

Thanks for your reply! Today I had a remote session with your level 2 support team. the engineer now totally understanding our issue. He told me that he will engage your QA Team on this case. Please let your QA Team look into this and give us a solution as soon as possible. Thanks!

[apolloxm]

The case has been escalated to QA Team since 2024/9/16 this Monday. now is Friday. We didn't get any update from QA Team. We don't know how long we need to wait and when we can get this issue to be fixed.