@Dashrender said in XS 7 or HyperV 2016:
@FATeknollogee said in XS 7 or HyperV 2016:
@Dashrender said in XS 7 or HyperV 2016:
Wouldn't that mean exposing your XS to the internet? I suppose not if you lock the inbound ports to the IP of the XO, where ever it's hosted. So from a management point of view, that's great, but I don't think most would end up using the backup portion in that situation, soooo...
How is this different from using (as an example) the built-in replication tool in Hyper-V? Either way you still need the 'net?
I've never tested this, so I am working from an assumption. But upon the assumption here is my explanation.
You have a XS host in your office in Dallas, 100 Mb internet connection.
The MSP has a XO VM running in a hosted DC in Cali that's used to manage the XS host. How does the data flow to the backup target? Does it flow through the XO system then to the target? I know that Veeam works this way. Assuming it does flow through the XO box, the data would flow out the 100 Mb connection to the XO, and then to where ever the backup target is. Assuming that's at the customer site, that would also be on that single 100 Mb connection.
Again - I admit to an assumption here - if my assumption is wrong, please don't be an ass about it, just inform me, and the rest here.
So with that assumption, assuming you want your first backup target to be onsite, then you'd either need a separate backup solution, or another copy of XS locally that runs backups inside the network.
Actually, no, Veeam does not work that way.
By default, the paid version of Veeam installs proxy stuff on each host as well as the box that Veeam is installed on. When a backup job runs, it chooses the best place to run through each time unless you specify a specific option in the backup job.