To be clear, it is no longer needed to backup Hyper-V guests at all. One of the significant changes that helped in achieving that was the removal of the hard dependence on the Hyper-V host VSS provider. Hyper-V backup has seen major improvements in Windows Server 2016, especially around performance, scalability and reliability and scalability. I’m not going to repeat all that info here.
#VEEAM BACKUP PROXY SOFTWARE#
To fully appreciate the steps forward made by Windows Server 2016 Hyper-V Backup I encourage you to read two articles on the StarWind Software blog: Hyper-V backup challenges Windows Server 2016 needs to address and Windows Server 2016 Hyper-V Backup Rises to the challenges. The information here is valid for any good hardware VSS provider like the one VSAN from StarWind provides (see Do I need StarWind Hardware VSS provider?) Major Changes in Windows Server 2016 Hyper-V Backup But in this article, I revisit the use of a hardware VSS provider dedicated specifically to some changes in Windows Server 2016 and its use by Veeam Backup & Replication v9.5 or later.
It has aged well and you can still use it as a guide to set it all up.
#VEEAM BACKUP PROXY HOW TO#
Many years ago, I wrote a white paper on how to configure a VEEAM Off-host backup proxy server for backing up a Windows Server 2012 R2 Hyper-V cluster that uses a hardware VSS provider with VEEAM Backup & Replication 7.0. StarWind Virtual Tape Library (VTL) OEM.Software as a Service (SaaS) & Financing.StarWind Virtual Tape Library Appliance (VTLA).
0 kommentar(er)
