{"id":3686,"date":"2014-07-22T15:00:18","date_gmt":"2014-07-22T15:00:18","guid":{"rendered":"http:\/\/www.backupassist.com\/blog\/?p=3686"},"modified":"2019-11-07T07:46:51","modified_gmt":"2019-11-07T07:46:51","slug":"10-tips-for-best-practice-hyper-v-backups","status":"publish","type":"post","link":"https:\/\/www.backupassist.com\/blog\/10-tips-for-best-practice-hyper-v-backups","title":{"rendered":"10 tips for best practice Hyper-V backups"},"content":{"rendered":"

\"hyper-v<\/a><\/p>\n

 <\/p>\n

Backing up Hyper-V virtual machines<\/a> can become complicated once you factor in host data, volumes, domains, disks, VSS writers, services and the resulting issues that can arise. To keep the backups of your virtual machines as simple and robust as the environments themselves, we\u2019ve put together a list of 10 tips for best practice Hyper<\/a>-V backups.<\/p>\n

<\/p>\n

1. Do not install other roles or applications on your Hyper-V host.<\/h2>\n

Your physical Hyper-V host server should only have one function, to be the Hyper-V host server. It should not double as a file server, a DNS server or, even worse, an application server. Any non-Hyper-V software and data should be on another physical server or one of the Hyper-V guests (VMs).<\/p>\n

If you don\u2019t follow this advice, you can complicate host level backups and affect the stability of the host server itself. Any problem with another role or application on the Hyper-V host can impact the guests. Even something as simple as a patch to an application could require a physical server reboot, and cause an outage for all of your Hyper-V guests (VMs) and the services they provide.<\/p>\n

2. Only assign a single role or application to each guest<\/h2>\n

Each Hyper-V guest (VM) should only have a single role or application. It\u2019s easy enough to make another guest, and dedicated environments are what make virtual machines so great.<\/p>\n

For backups, having only one role or application per guest makes it easier to:<\/p>\n