We have been using Veeam Backup & Replication for a long time - it's an awesome product. However it's biggest weakness in my opinion is backing up a Windows Cluster (for example a Windows File server cluster). This is because the Windows cluster needs shared storage (for example in-guest iscsi initiator). I got excited when I saw that Esxi 5.5 added support for virtual RDM's shared across two Esxi hosts, but it won't allow snapshots in this configuration so Veeam still won't work.
However, I've been wondering whether Veeam Endpoint Backup could assist in this configuration. I installed it as a test on a Windows 2012 R2 File server Failover cluster we have - interestingly Veeam detected the data disk on the 'active' Windows node, but not on the standby cluster node. The potential issue here is that if I configure Veeam Endpoint to backup the active node, and the node subsequently becomes the standby node, then Veeam Endpoint will be unable to backup the disk any longer.
On the standby cluster node, the shared disk is visible in diskmgmt.msc but marked as 'reserved'. However a query using diskpart seems to suggest the disk is available as read only. So, I have two questions.
a) Could the logic of Veeam Endpoint be modified to support backing up the 'reserved' cluster disk on the passive node? The fact DiskPart seems to suggest the disk is read only is promising - it sounds very similar to the Direct San backup method where the disk is attached to the backup node but 'offline' so the backup node doesn't write to it.
b) is there some sort of ability to control Veeam Endpoint through the command line? Or better still, have a pre-job script option? I could potentially have a pre-job script which forces the cluster to switch over to the node Veeam Endpoint is running on.
Apologies for the long post, but the way I see it, this is the closest we've been able to get with backing up a Windows Failover Cluster using Veeam