We are trying to configure our Veeam backup off-host proxy, but have encountered some challenges.
- Hyper-V Cluster, using CSV stored on v7000 presented via FC
- Veeam off-host Proxy, connected to v7000 via FC, with all CSVs mapped
On the v7000 we have created two Volumes which is mapped to the fictive VSS_FREE host (which essentially are all the VSS Writers installed on the Hyper-V hosts and off-host Proxy).
The names of these volumes are "VSS_Snapshot_001" and "VSS_Snapshot_002"
Demo Backup Scenario:
We have a backup job with several VMs, which are spead out on multiple CSVs.
When we initiate the backup, the hardware VSS starts creating flashcopy mappings, and the first backup is successful. If the second VM is on the same CSV, it uses the current flashcopy mapping, and that too is successful. When it starts the third job which is on a different CSV, it creates a new flashcopy mapping, and that too is successful.
At this stage, both of the pools are now in a flashcopy state, and therefore, the subsequent backups fail, because there are no free pools.
It seems that the VSS Hardare provider is not stopping or unmapping the flashcopy job after the backup job is "Closing Snapshot". It almost seems like the VSS Hardware Provider has initiated the wrong kind of FlashCopy Job.
This is how it looks like in the FlashCopy Window inside the v7000 console:
Does anybody know how we can tell the VSS Hardware Provider to initiate the FlashCopy with correct options, or at least make it remove the mapping after Veeam states "Closing Snapshot"?