Support for AlwaysOn Availability Groups

In this article

    AlwaysOn Availability Groups allow you to increase fault tolerance between active and hot-standby databases without involving shared physical disks, which is quite important for virtualization of Microsoft SQL Servers. Veeam Backup & Replication supports AlwaysOn Availability Groups for virtualized Microsoft SQL Server 2012 or later.

    Image-level Backup of Microsoft SQL Server VMs

    During image-level backup of a Microsoft SQL Server VM, Veeam Backup & Replication requests and analyzes information about databases that are included in the AlwaysOn Availability Groups. Depending on the retrieved information, Veeam Backup & Replication creates a VSS snapshot with or without COPY_ONLY flag. The VSS_BS_COPY flag for VSS snapshot is triggered if the VM represents a secondary node for at least one AlwaysOn Availability Group.

    Veeam Backup & Replication also detects to what cluster the database belongs. If the backup job does not include all VMs from the cluster, an information message will be issued.

    Retrieved information is saved for further log identification.

    Transaction Log Backup

    Transaction log backup can be performed only for those databases that were successfully backed up, either on the primary or on the secondary node of AlwaysOn Availability Group.

    The transaction logs processing interval may be the same or may differ through VMs included in AlwaysOn Availability Group. If the interval is different, Veeam Backup & Replication will use minimal value (by default, 15 minutes).

    At each log processing interval, Veeam Backup & Replication chooses the AlwaysOn Availability Group node for which transaction logs will be backed up.

    Logs are backed up from one node of the AlwaysOn Availability Group. To become a subject for log backup, the node must meet the following criteria:

    • Required Veeam Backup & Replication components can be installed on this node (the VM must be running).
    • If there are any logs remaining in the temporary folder on the node of AlwaysOn Availability Group, this means these logs were not backed up to the backup repository during the previous session of the transaction log backup job, so this AlwaysOn Availability Group node must be processed first.
    • Databases in the AlwaysOn Availability Groups for this node were successfully backed up for the last two processing intervals.
    • Veeam Backup & Replication can establish a network connection to the node or PowerShell Direct connection, if a connection over the network cannot be established. PowerShell Direct is used for VMs that reside on Microsoft Hyper-V Server 2016 or later and run Microsoft Windows 10 or Microsoft Windows Server 2016 or later. Veeam Backup & Replication requires Microsoft PowerShell 2.0 or later to work over PowerShell Direct.
    • The node that you want to back up must be specified in the Backup Preferences of your Availability Group Properties. Note that Veeam Backup & Replication will not back up transaction logs for the primary node if this node if the necessary Veeam Backup & Replication components are not installed on this node and this VM is not running.

    Support for AlwaysOn Availability Groups Note:

    When you configure a backup job to process Distributed Availability Groups transaction logs, select either primary or secondary distributed availability group. Otherwise, the log chain of the distributed group databases might become inconsistent.

    When you configure a backup job to back up transaction logs for other Distributed Availability Groups, use the Perform copy only mode. See Application-Aware Processing to learn more about the copy only mode. You can also use the exclude feature to prevent Guest-OS database from being processed. See Exclude Objects from Backup Job to learn more on excluding objects. To read about distributed availability group limitations, see Configure distributed availability group.

    I want to report a typo

    There is a misspelling right here:


    I want to let the Veeam Documentation Team know about that.