Highlighted
kamalt1
2 Iron

SQL virtual client is a primary replica on AoAG - how to backup

I have a customer who has 4 nodes in a SQL cluster.

2 nodes are in the MAIN site

2 nodes are in DR site

The 2 nodes in MAIN are in a FCI with virtual name virtual1 and virtual1 is a primary replica and the other 2 nodes in DR are secondary replica.

SQL in FCI with AoAG is not supported with Avamar hence I have to backup from the primary replica as a stand-alone. When I configure virtual1 on Avamar for backup, I can only see the local DBs, not the ones which are in AoAG.


As per user guide, AoAG in a SQL FCI is not supported and have to backup from primary replica. But can we backup from primary replica if the primary replica is a virtual server?

When I browse the physical node with "avsql --operation=browse --verbose", i get the error specified path '' does not exist or is not accessible

Output of avsql --operation=browse --verbose from 1 physical node.

c:\Windows\system32>avsql --operation=browse --verbose

Dynamically allocated CTL listen port (54664)

avsql Info <6673>: CTL listening on port 54664

avsql Info <10684>: Setting ctl message version to 3 (from 1)

avsql Info <16136>: Setting ctl max message size to 268435456

avsql Info <19484>: ===> sqlconnectimpl::check_smo_version

avsql Info <19482>: Found assembly: 'Microsoft.SqlServer.Smo,fileVersion="10.50.2500.0",version="10.0.0.0000",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"'

avsql Info <19483>: Returning from SMO version check with value: 12

avsql Info <0000>: <=== sqlconnectimpl::check_smo_version

avsql Info <19487>: Start checking for SMO DLL version 12

SQL Server 2011 installed.

SMO 2011 managed DLL loaded.

avsql Error <15125>: Specified path '' does not exist or is not accessible

Terminating CTL listen thread

avsql Info <6451>: avsql returning with exitcode 536870919

Any suggestions are welcome.

0 Kudos
1 Reply
gautamgp
3 Argentium

Re: SQL virtual client is a primary replica on AoAG - how to backup

Not sure if you got this resolved. The configuration is very much supported now. You can configure the failover cluster Avamar client and then add the following "show_db_in_availability_group=true" in the avsql.cmd file.

0 Kudos