With NMM 8.x that works for sure.  Did you use cluster name as client resource?

Hi Hrvoje,

yes, I have a Cluster client ressource.

Regards

Heiko

Are these AAG (AlwasyOnGroup) configured with Default SQL Instance or Named SQL Instances?  Below saveset entries are pertains to default instances.

MSSQL:

MSSQL#

MSSQL# :

You may need to include the correct SQL instance name in the saveset to complete the backup without any issues.

MSSQLSERVER is for a default instance.  Pls. check whether the AG db's are configured with Named instance.

In the properties of the AG there is no instance defined.

Get-ItemProperty 'HKLM:\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL'

PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL

PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names

PSChildName  : SQL

PSDrive      : HKLM

PSProvider   : Microsoft.PowerShell.Core\Registry

MSSQLSERVER  : MSSQL11.MSSQLSERVER

Can you post the screen shot of AG properties (using Primary replica)?

Cluser nodes are "dghams200" and "dghams201". AO Cluster is "dghams203".

Thanks for the screen shots!!  Can you post the AG owner instances (Instances names used for AG creation).  Hope in both the nodes "SQL Standalone instances are running";  I mean, no SQL Virtual server is configured for this AG.  Couple of follow-up queries:-

1. Did you try to configure using NMC Client configuration wizard?

2. Did you provided the SQL Server credentials in the NMC Client (Remote user and pwd field)

3. Did you try to run the AAG backup using debug level = 9 (-D9)

Please revert the above details....