My mitigation for Cold Start is having the Hyper-V server that hosts a DC / DHCP not be part of the domain and have a couple entries in the HOSTS file. In fact my latest deployment (yes the sbs2011) the Hyper-V host points to a public DNS server so I can remote to it even if all the guests on it drop offline.
At Hyper-V client #2 (they have two Hyper-V hosts) I have on host on the domain and the other off-domain. I can manage both from one console, I just have to use local credentials for the off-domain one. Dave -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Tuesday, March 13, 2012 10:56 AM To: NT System Admin Issues Subject: Re: New to virtualization On Tue, Mar 13, 2012 at 11:04 AM, David Mazzaccaro <[email protected]> wrote: > I am starting to investigate moving our aging network infrastructure > into the virtual world. Your questions sound similar to the ones I had a few months ago. You should prolly review this thread: http://www.mail-archive.com/[email protected]/msg106517.html > I guess the way it would work is that the VMs would reside on the SAN, > and the 3 hosts would call up the SAN to load each VM utilizing the > host's CPU, RAM, NIC, etc.)... right? Right. The storage for each VM lives on the SAN. The VMs run on the HP servers. It's basically just a different way of attaching disks. > Being very new to VM, does the above scenario seem to make sense? For some value of "sense". > It is hard for me to imagine all that traffic going between the SAN > and the host servers w/o creating a huge bottleneck (over gig > Ethernet) As opposed to what? > Do people recommend virtualizing every server? Varies. From what I've seen, a common recommendation is to have some core IP & AD infrastructure (DNS and DC) available on a dedicated physical box, for a "cold start" scenario. Otherwise the VM host can end up trying to talk to DNS or DC to start the VM which holds for DNS/DC. > Is 7 TB of storage enough (probably only 3 usable after array config)? That depends *entirely* on how much data you're storing. > I have done a little more reading, and from what I understand w/ 3 > Windows Enterprise licenses, I would be limiting myself to 12 VMs. Yes, and the host would be restricted to providing VM hosting *only*. You're not permitted to do anything else on the host OS. > However, if I went w/ 3 Windows Datacenter licenses, for a small > increase in price - I would get unlimited VMs? Yes. Be aware that you need a DC license *per physical processor* (chip package), and it's a minimum of two per physical host. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
