We are in the middle of replacing our "legacy backup" with Veeam. I have to say, I expected to be happier with the result.
One problem I am having is the way you can attach VMs to a job. For vSphere, we just used the folder structure, which enables me to create a job per customer and also ensures that newly created VMs automatically get added to the right backup job even when I am not the one creating the VM.
In Hyper-V, this just seems impossible. As far as I can see, the only options I have is to add hosts, clusters, cluster folders, CSVs and single VMs.
- Adding per host makes little sense considering Live Migration.
- Per cluster and cluster folder leaves me with big, unwieldy job sizes.
- Per VM makes it so I have to manually add each new VM, putting us at risk of forgetting to back up a VM.
- Per CSV is what I have at the moment but that leads to the CSV entering paused state. Also, the job size is still too large for my liking and application aware processing is a veritable bitch to configure. Not to mention that the customers demanding encryption are not satisfied with sharing an encryption password.
So my question is why it's not possible to add VMs based on the cloud they're attached to in VMM? I have attached all hosts and clusters via the VMM server so that information should be available to Veeam.