Backup of SQL-Server distributed availability groups

[MariusN]

Hi Gostev,

is there any option / veeam supported way to backup SQL-Server distributed availability groups?

I tried it in a testlab and do receive the expected error messages as followed:
Failed to perform internal backup (testdagDB): SQL AlwaysOn secondary replica backup LSN is greater than redo LSN, transaction log backup will be retried
Collected SQL Server transaction logs do not match any existing database backup: testdagDB
Transaction logs from some databases were not backed up for the last 'x' intervals

As SQL Availability Groups are supported i am looking into this topic for the next "step" to backup DAG Databases as it could be mandatory technique in the future for us.

Currently i do run the following setup:

Cluster1:
sqlnode1
sqlnode2
AGListener1

Cluster2:
sqlnode3
sqlnode4
AGListener2

The database testdagDB is spanned across both clusters / both AG's.
I therefore created a protection group where both clusters are part of , after i created a backup job where the protection is processed by veeam agent (even though all machines are virtual).

Looking forward to hear from you.

Regards
MN

[HannesK]

Hello,
I hope it's okay if someone else than Anton answers

As you asked for agents, distributed AlwaysON availability groups are unsupported

Distributed AlwaysOn Groups are not supported.

As you mentioned, that you are running everything in VMs, you could use VM-based backup


Best regards,
Hannes

[MariusN]

Hello HannesK,

is this something Veeam is working on already? Otherwise you could thread it as an FeatureRequest

I guess the problem won't be solved by backing up on VM-based level when trying to backup a DB being part of Distributed Availablity Groups because of the transaction log (LSN) having a higher / more actual number on another node - even then backup will fail for this specific db being part of the 2nd cluster (secondary).

Regards

[HannesK]

Hello,
for Veeam Agent for Windows, it's a feature request, yes.

I guess the problem won't be solved

I expect that the configuration documented in the link I mentioned is working for VMs. If not, please post a case number that we can check that.

Best regards,
Hannes