You must enable HPE 3PAR Web Services API Server on your 3PAR. You must have a fiber channel link to your 3PAR.Ĥ. You don't have to configure it, but it has to be on there.ģ.
#Veeam backup hyper v install
Install the Hyper-V role to your proxy server through Programs and Features. So if your Hyper-V server is "Windows Server 2012 R2" then you must use that same OS for your proxy server.Ģ. The OS version should mirror what your Hyper-V server uses. Steps required to achieve direct SAN Hyper-V backups from HPE 3PAR:ġ. So there are some advantages to just using the on-host proxy. With Hyper-V 2016, I'd probably just stick with the on-host proxy when you are using CSVs since Hyper-V 2016 no longer takes a snapshot of the host volume unless you use an off-host proxy. In case of SMB file share, the off-host proxy just need to have access to the file share. This means it is up to the hardware vendor to provide functionality, Veeam does not do anything specific on their end. How an off-host proxy works will depend on whether you are using CSVs with iSCSI/Fiber Channel/SAS or SMB file shares to present your storage to your Hyper-V cluster.įor an off-host proxy with CSVs, your storage vendor must provide a hardware VSS provider to allow the storage snapshots to be mounted by the off-host proxy. In the default on-host proxy with Hyper-V, the Hyper-V host is what accesses your storage, and then sends it to your backup repository. Backup proxies work quite differently in Hyper-V vs.