Feature Request: Contained availability groups support in Veeam

[olopezoe]

Use case and business impact:
In a regular Availability Group, we have to keep server level objects on each node in sync. That means jobs, proxies, operators, logins, server roles, server permissions, database encryption keys, credentials, various certificates, mail accounts, mail profiles, etc. Logins are especially annoying because they are really based on the SID which is kind of hidden. It is a significant effort to keep it all in sync and only fails when we fail over.

Contained Availability Groups move all that configuration into the Availability Group. Add a login once and all servers have it. The load on the DBA is significantly reduced. And the number of failures on failover is also reduced. Microsoft introduced this feature in SQL Server 2022 and enhanced it in SQL Server 2025. It is a feature they are actively working on. We expect the few remaining limitations to be addressed in upcoming releases.

Our plan is that all future Availability Groups will be Contained Availability Groups. We expect everyone else will do the same as they gradually migrate to new Availability Groups.

Environment:
VBR 12.3.2.4165
SQL 2022 Enterprise, Contained availability groups
Windows Server 2019

The expected outcome:
We need to do incremental log backups on those CAG databases using Veeam.