The way I do it:

- define nodes in AAG (FQDN) - normally two nodes

- define 3rd node which is using cluster name to access it - this one has to be shortname

- add to remote access of virtual node those physical ones

Configure backup for all 3 nodes since "local" nodes contain system DBs.  I suspect you might have an issue with the fact that you use FQDN for backup of AAG DBs over cluster name which is something I have seen in past and since went for approach with shortname for cluster names.

Hi,

Thanks for the reply.

I assume I've managed to do that - I have three clients, one for the instance name and two for the physical clients...

They all run successfully, but still only backups the standalone databases - it keeps saying that the CPI Database will be excluded as it is part of Availability group.

Hello.

You need to specify the Availability Group Name in the saveset. In the form:

MSSQL$(instance_Name)#(Availability_Group_Name):(database)

Example:

MSSQL$SS01#AGTCLU01:

This saveset, backups all databases of instance SS01 in the availability group AGTCLU01.

As system databases are not in Availability group, you will need to backup them with the physycal nodes, as ussual (MSSQL$instance:master, MSSQL$instance:model, MSSQL$instance:msdb). Set a backup client for each physical node.

Hi,

If I understood correctly, considering the following image, my saveset should be MSSQL$LST-REC#AG-REC: right? Because it gave an error.

43708:(pid 16864):Start time: Mon Sep 11 17:48:52 2017

153897:(pid 16864):Computer name: SVWA-BDC-CPD01     User name: administrator

Check the detailed logs at 'C:\Program Files\EMC NetWorker\nsr\applogs\nsrsqlsv.log'.

38571:(pid 16864): Bad switch: -o

38562:(pid 16864): Unsupported savegrp option -o will be ignored

107092:(pid 16864):Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe: Original file name: nsrsqlsv.exe Version: 9.0.1.614 Comments: Supporting SQL 2005, SQL 2008, SQL 2008 R2, SQL 2012 and SQL 2014

100224:(pid 16864):Unable to proceed backup. Unsupported saveset specified

43709:(pid 16864):Stop time: Mon Sep 11 17:49:10 2017

--- Job Indications ---

lst-rec:MSSQL$LST-REC#AG-REC:: retried 1 times.

As ledugarte said, you don't specify name of AAG there.  You only specified named instance, but for AAG there is futher naming convention (see docs or what ledugarte already mentioned in his post).

Hi,

So, basically the saveset should be MSSQL$(instance_Name)#(Availability_Group_Name):(database) where:

(Instance_Name) = REC

(Availability_Group_Name) = AG-REC

(database) = CPI

In the pic below you can double check the Instance name and AAG Name.

Using then SaveSet MSSQL$REC#AG-REC:

43708:(pid 34840):Start time: Tue Sep 12 09:33:56 2017

153897:(pid 34840):Computer name: SVWA-BDC-CPD01     User name: administrator

Check the detailed logs at 'C:\Program Files\EMC NetWorker\nsr\applogs\nsrsqlsv.log'.

38571:(pid 34840): Bad switch: -o

38562:(pid 34840): Unsupported savegrp option -o will be ignored

107092:(pid 34840):Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe: Original file name: nsrsqlsv.exe Version: 9.0.1.614 Comments: Supporting SQL 2005, SQL 2008, SQL 2008 R2, SQL 2012 and SQL 2014

100224:(pid 34840):Unable to proceed backup. Unsupported saveset specified

43709:(pid 34840):Stop time: Tue Sep 12 09:34:14 2017

--- Job Indications ---

lst-rec:MSSQL$REC#AG-REC:: retried 1 times.

Am I misunderstanding something?

In your first post, you said your cluster name is LST-REC.ad.xpto.com and your windows cluster name is alwayson.ad.xpto.com.

What client instance you created for the cluster?. You should create client instances for each node, and cluster client should be created with "alwayson"...

Please make sure to check compatibility with version you use.  Earlier versions of module didn't support AAG with named instances - do not know top of my head where this changed, but check release notes.