SQL is most definately Always on availability group.

Within windows failover clustering, each Availability group appears as a Role where the listener and "other resource" lists the Availability group

we selected always on sql when running cluster configuration wizard

oh wow i can see ALL databases now which is a step forward i suppose.

i was under the impression that i registere each availability group and it's listener as it's own client and i would only see those databases under each client?

does that make sense?

Hi Chris,

         Before I answer your queries, Can I have the following Details

                1. Is SQL also in Failover Clustering or just in "Always On" Availability Group ?

                2. If SQL is both in "Failover Clustering" and "Always On" then the databases that you want to backup are spread across both configurations ?

                3. While running the Avamar cluster client wizard on the SQL server which option did you choose

                             SQL ?

                         or SQL Always ON ?

Good. Then create avsql.cmd file under the shared "var" directory. Add the following line '--show_db_in_availability_group=true and save it.

Take the Avamar cluster group offline and make it online using the Failover Cluster Manager. Try to browse and let me know if you are able to view the DB's in Always ON group.

hrmmm i do have an SR open with EMC who's investigating as i have another customer who uses Always on Availability groups and when i browse that client in Avamar under Windows SQL it shows up as databaselistener\availabilitygroup as opposed to just (local)

i'll keep digging and see what they come up with.

We need to see the databases on a per availability group basis to stagger backups

that's what i'm working with EMC for

I 100% selected AlwaysON Sql yet it's not displaying the client with the databaselistener\availability group

i will bring this up with them when they finish their investigation    

As all of them are part of the Same Cluster, it would not work. We have few customer's here with similar configuration and that is how we made it work.

If you think my answer has resolved your query, please mark that as solution so that others can leverage if they face similar situation.

Thanks

databaselistener\availabilitygroup this format comes if you run the "Avamar Cluster Wizard" and choose "SQL ALwaysON" as the option. This will only protect the DB's which are in Availability Group and would not protect the DB's in Failover Clustering.

FYI here's the output of "View Cluster Configuration" (it's been sanitized to remove customer numbers)

SQL 'AlwaysOn' Cluster Configuration:

All Available cluster 'CLUSTER01' Nodes:

     Node name = DB01 (local node)

          Node status = Up

          Is Proxy Node = False

          Avamar Windows Client installed = True

          Avamar Backup Plug-in for SQL AlwaysOn installed = True

          List of available IPv4 addresses:

               Node's IPv4 address = 172.28.119.1

               Node's IPv4 address = 10.10.10.1

     Node name = DB02

          Node status = Up

          Is Proxy Node = False

          Avamar Windows Client installed = True

          Avamar Backup Plug-in for SQL AlwaysOn installed = True

          List of available IPv4 addresses:

               Node's IPv4 address = 172.28.119.2

               Node's IPv4 address = 10.10.10.2

     Node name = DB52

          Node status = Up

          Is Proxy Node = False

          Avamar Windows Client installed = True

          Avamar Backup Plug-in for SQL AlwaysOn installed = True

          List of available IPv4 addresses:

               Node's IPv4 address = 172.27.119.2

               Node's IPv4 address = 10.10.10.4

     Node name = DB51

          Node status = Up

          Is Proxy Node = False

          Avamar Windows Client installed = True

          Avamar Backup Plug-in for SQL AlwaysOn installed = True

          List of available IPv4 addresses:

               Node's IPv4 address = 172.27.119.1

               Node's IPv4 address = 10.10.10.3

Viewing current configuration information for the SQL AlwaysOn Cluster Client for cluster 'CLUSTER01'

Cluster Client Settings:

     Cluster group name  = WTI

          Backup cluster client name = EMC Avamar Backup Agent resource for WTI

          Cluster client's var directory = \\witness01\avs\wti

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool8-UAT-Utilities

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool8-UAT-Utilities

          Cluster client's var directory = \\witness01\avs\uatutilities

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool7-Utilities

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool7-Utilities

          Cluster client's var directory = \\witness01\avs\utilities

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool2-NZ

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool2-NZ

          Cluster client's var directory = \\witness01\avs\nz

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool6-UAT

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool6-UAT

          Cluster client's var directory = \\witness01\avs\uat

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool4-HK

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool4-HK

          Cluster client's var directory = \\witness01\avs\hk

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool5-SG

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool5-SG

          Cluster client's var directory = \\witness01\avs\sg

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool3-AU

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool3-AU

          Cluster client's var directory = \\witness01\avs\au

          Backup cluster client IP =

          Network mask =

     Cluster group name  = Pool1-AU

          Backup cluster client name = EMC Avamar Backup Agent resource for Pool1-AU

          Cluster client's var directory = \\witness01\avs\au

          Backup cluster client IP =

          Network mask =

Avamar Server Settings:

     Avamar backup server name = ava23-cntrl01.baas.syd.intellicentre.net.au

     Avamar backup server IP = 172.28.92.41 (field not used)

     Avamar Domain for cluster client = /customer

     Port number = 28001

     Cluster client's var directory = \\witness01\avs\sg

     Cluster client local port number = 28003

Nodes with Cluster Client Installed:

     Node name = DB01

     Node name = DB02

     Node name = DB52

     Node name = DB51

Hi,

was this case successful finished? Does your Setup now work fine?

which collation do you have for your DB?