May I ask you what's wrong with that approach? Do you have concerns about hosts resources? You might want to try assign an off-host proxy role to a VM, please check this article for details.it would just take a toll on the hosts that running the vm that is being backed up,
No, that should not cause any performance problems since proxy does not generate much IO. I guess you don't have local storage on the hosts (probably installed directly to usb stick), is that correct?If I use a vm as a proxy - this vm would reside on the same san storage as the vm's being backed up, would that be a problem?
PTide wrote: - to install a VM on the local storage and use it as an off-host proxy. The problem is that such approach is not supported by MS. Please check these articles: 1 and 2.
On-host proxy might consume more resources than you'd want it to, while having an "off-host" proxy inside a VM ensures that it won't eat more than the VM actually has available. Another, and probably more efficient way to curb the on-host proxy's appetite is to limit the number of concurrent tasks.How can running a hype-v VM inside one of the hosts be a solution?
Users browsing this forum: Google [Bot] and 1 guest