Physical Server Switched to Hyper-V VM Need Suggestions
Wasabi is an available target. Make sure the list is expanded if you're not seeing it.
Having said that, you have some considerations for how to handle this customer given the slow broadband connection. At 5Mbps upstream connection, you're looking at a maximum of around 640 KB/Sec - assuming no other traffic. Assuming 50% compression, the full backup might take a very long time (7+ days).
This is what I would probably do:
* Use the VM version to back up the VMs to local storage. Use a low cost 2 mirrored drive NAS at the customer (or whatever local storage you have available that's off the Hyper-V host). That will protect the VMs, but alleviate the broadband speed issues
* Install CloudBerry on each VM (you only have 2) and run file-based backups, as you've been, to cloud storage. In fact, I'd probably do a hybrid backup so you have local backup copies as well
The other option is: If you do not need the VM backups (assuming the VM is easy enough to re-create), then just continue to back up the files to local/cloud storage.
Our Wasabi support does include Synthetic Fulls (as you noted). It's just not clear though how much data will need to be uploaded even with incremental backups (think of the OS changes after a large Windows update). I think even with synthetic fulls, a 5 Mbps connection might be an issue.
You say this is for a customer, so can I ask if you're using Managed Backup or are you using our stand-alone products with your customers. If the latter, you might find moving to Managed Backup much easier to manage and bill customers since it's a subscription model and provides a thin-client management console.