Failover Cluster Support

You can use Veeam Agent for Microsoft Windows operating in the managed mode (within the Veeam Agent management scenario) to protect data processed by a failover cluster. Veeam Agent supports Windows Server Failover Clusters running on any of the supported Microsoft Windows Server OS versions. To learn the full list of versions, see System Requirements.

Veeam Agent supports data backup and restore for the following types of failover clusters:

  • Windows File Server Failover Clusters
  • Windows Server Failover Clusters that run the following applications:
  • Microsoft SQL Server 2008 SP4 or later

Keep in mind that SQL Server Failover Cluster Instances and Always On Availability Groups are supported only for Microsoft SQL Server 2012 or later. To learn about Always On Availability Groups, see Backup of Always On Availability Groups.

  • Microsoft Exchange Server 2013 or later

Microsoft Exchange Database Availability Groups (DAGs) are supported. To learn more, see Backup of Database Availability Groups.

Limitations for Failover Cluster Support

Failover cluster support in Veeam Agent for Microsoft Windows has the following limitations:

  • Always On Availability Groups with no underlying failover cluster (Clusterless Availability Groups) are not supported.
  • Backup of SQL Server failover clusters that store databases on a cluster disk is not supported if at least one of the cluster nodes hosts a local disk with the same mount point.
  • SureBackup of failover clusters is not supported.


Failover Cluster Support NOTE

Veeam Backup & Replication does not support simultaneous processing of Microsoft SQL Server transaction logs on SQL Server clustered instances with identical names. The limitation applies to clustered instances of different failover clusters as well.

For example, you configure two backup jobs that process transaction logs of different failover clusters whose SQL clustered instances have identical names. In case these backup jobs run simultaneously, transaction logs will be processed only by the backup job that started first. The second backup job will not process transaction logs.


In This Section



Page updated 6/11/2024

Page content applies to build