I could spin up a spare server, restore C, restore the VMs. As an alternate (say the building burned to the ground), the config and backup copies are stored on another campus. Ideally, restoring C will restore the config. The config backup is stored on the host (C:) and copied somewhere else. My quest is "restore to usability as quickly as possible." Restore the VMs using VB&R.ĭo you also backup the Veeam B&R configuration?
Our restore procedure from bare metal is 1.
Veeam backup hyper v install#
We also install Veeam Endpoint on those hosts to back them up. We install VB&R on our hosts to backup the guests from local storage and send them to other places (tape, cross-site, etc.).
Veeam backup hyper v full#
We install the full GUI on every host and use it to manage the VMs on that host. The WS license terms for Hyper-V role clearly state that you can install anything on the host that is used to "manage the VMs." That includes management software and backup software. Also look into air gapping your backups and the 3-2-1 rule. I was just offering up some ideas for you. You really wouldn't want it to be running with typical users since you need this thing secured. If the workstation is only used for administrative purposes, then effectively it is a server. I agree with this 99%, however there are always exceptions yes. Veeam does not recommend installing their software on a domain-joined workstation. You can also just install Veeam on a workstation with drives for the backup target. Since for about maybe 4-5 months when my LTO unit died. Thanks! Would you be able to provide any documentation to support this statement? Just asking because I've read all sorts of opinions on this matter.
Once you install anything else beyond the Hyper-V tools, you need a license. The rule only applies to Microsoft platform. If you install that application on the host, Microsoft will have you buy another license.
0 kommentar(er)
