Using Standalone Veeam Agent for Microsoft Windows with a Microsoft Failover Cluster

Limitations and Considerations

Clusters

• Backup is supported but without any support for application consistency.
• There is no guarantee of application transaction consistency when the application files are located on clustered disks, RDMs, or other shared media. Such objects must be excluded from backup in order for the node protection to be successful. A possible workaround is to use a native application backup utility for storing the backup of the disk in question.
   

SQL Always-ON

• The primary node backup is supported. 
• Transaction log backup is disabled and not supported when Veeam Agent for Microsoft Windows is installed on the Always-On node.
• The entire computer, volume level, or file level backup and log truncation will work unless failover is performed.
• Veeam Agent for Microsoft Windows operating in standalone mode is unable to track node state changes, which may affect the backup. To continue backup, such a node must be switched back to the primary state.
• Simultaneous backup of the primary and secondary nodes is not supported.
   

Exchange DAG

• A separate backup of either the active or passive node is supported.
• The entire computer, volume level, or file level backup and log truncation will work unless failover occurs.
• Veeam Agent for Microsoft Windows operating in standalone mode is unable to track node state changes, which may affect the backup. To continue backup, such a node must be switched back to the primary state.
• Simultaneous backup of the primary and secondary node is not supported.
  

The current article covers cluster backup workarounds which could be used for a standalone version of Veeam Agent for Microsoft Windows.

Keep in mind that Windows Server Failover Cluster is completely supported in Agent Management functionality. The following article contains all the details on how to set it up - https://www.veeam.com/kb2463