https://www.veeam.com/blog/restoring-in ... veeam.html
I was just reading the above article about what's needed to restore your entire environment from backup assuming the Repository is safe. From what I gather you get one server online with a fresh (workgroup?) copy of Windows, install VBR, import the license keys, and connect the repository. All well and good. Then it says to add the hypervisor hosts (let's say they're Hyper-V) to restore the backups to. WELL, what if the hypervisors are domain joined and all my domain controllers were virtualized? I realize that's not best practice but that's where we're at now and I'm trying to plan for the worst, ie every single domain-joined system becomes infected and we have to wipe all the servers down to bare metal before restoring from backup.
Would we have to spin up and configure a workgroup-joined Hyper-V host to restore the PDC to before proceeding with the rest of the network, and then rebuild that WG host as the last step? Or is there a better way of handling this? I briefly thought of having a physical DC that can be more easily restored from bare metal but that seems generally discouraged. Also note that we have agent-level backups of our Hyper-V hosts' OS volumes but I imagine they wouldn't behave right if we restored them and there's no DC to be found.
-
- Enthusiast
- Posts: 47
- Liked: 4 times
- Joined: Nov 14, 2019 7:12 pm
- Full Name: Chris Lukowski
- Contact:
Who is online
Users browsing this forum: No registered users and 154 guests