Recommendations for Hyper-V or practical experience, summarize?

Question

Backup

Good afternoon Toaster!
Several questions have accumulated on the topic of virtualization in Hyper-v.
In general, the question is addressed to those who have already had practical experience with the Hyper-V hypervisor.
Question:
1. Is it worth the question to raise the second machine with AD DS services physically or virtually? But there’s also to take into account that this is the first experience with hyper-v, and for example, when the hyper-v manager on the client in remote access fell off at 2 a.m. and the virtual machines went out :), then I was a little cheered up ...
Fortunately, rdp worked, I ran it through powershell, by the way about ps, the knowledge is minimal, but I'm learning.
So how is it better to start a second CD virtually or physically?
2. Network adapters. On Habré and Microsoft, they recommend separating virtual machines into different physical network adapters so that there are no interruptions in the network. AD, a file server and a proxy squid on ubuntu. AD and a file server are running on one physical network adapter on my server sit, hang a proxy on another?
3.Question of backup. After installing the virtual machine, you need to take care that it can be picked up when it falls. There will be no cluster and storage system for sure. Backups will be added to the server.
Backup all VMs or just data?
Similarly with AD, the systems section or the entire server.?
Here is the idea if the physical server breaks down so that everything can be raised in 1-1.5 hours.
The question turned out to be capacious, but here I would like to hear advice and recommendations.
Thanks in advance .
Links to the manual would be interesting.

Answer 1

1. Habr is a habr, but Technet is still a more authoritative resource in matters of Windows systems. There is no reason to have a physical domain controller. If you have lost all VMs (including CD), you can always log in as a local admin and restart whatever your heart desires.
2. Habr is a habr, but Technet is still ... It is worth proceeding from the requirements for the network (bandwidth, technologies used, etc.). Most likely, two to four physical gigabit network adapters will be enough for you. Combine them in teaming, create an external virtual switch on top. Create a virtual adapter (checkbox when creating the switch) for the host system, assign it an IP and, if necessary, a VLAN. When creating a VM, add the required number of network adapters with the corresponding VLANs.
3. Windows Backup Services is still the most alive, and it can backup Hyper-V. Quite tolerable and also free solution.
PS If you have no experience in virtualization from the word "completely", go to Microsoft Virtual Academy and look and read a couple of introductory courses. Enough to get started, you'll figure it out along the way.

Answer 2

Actually, as I see it
1. Find an old PC with at least a dual-core processor, a 40GB hard drive, and 4GB of RAM - it is desirable that the hardware be reliable, proven. Here on it also raise AD DS.
2. I won't give you a definite answer here. It all depends on the individual characteristics of your infrastructure. From what you described, it is more correct to hang up a proxy on a separate interface.
3. You can backup completely virtual machines with free Veem in conjunction with a PowerShell script. That's just the reliability of your backup will be rather weak - you will store it on the same server, can you still buy at least some single-disk storage system?