+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 29 of 29
Windows Server 2008 R2 Thread, Hyper-V in Technical; No way I would do that, it would produce a massive single fail point for your network. Much better to ...
  1. #16
    zag
    zag is offline
    zag's Avatar
    Join Date
    Mar 2007
    Posts
    3,800
    Thank Post
    904
    Thanked 419 Times in 352 Posts
    Blog Entries
    12
    Rep Power
    87
    No way I would do that, it would produce a massive single fail point for your network.

    Much better to have 1 or 2 physical servers as DC's.

    I also keep my fileserver physical as it has so much disk IO.

  2. #17

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Quote Originally Posted by zag View Post
    No way I would do that, it would produce a massive single fail point for your network.

    Much better to have 1 or 2 physical servers as DC's.

    I also keep my fileserver physical as it has so much disk IO.
    Where's the single fail point?

  3. #18
    zag
    zag is offline
    zag's Avatar
    Join Date
    Mar 2007
    Posts
    3,800
    Thank Post
    904
    Thanked 419 Times in 352 Posts
    Blog Entries
    12
    Rep Power
    87
    Quote Originally Posted by Hightower View Post
    Where's the single fail point?
    First off I wouldn't trust hyper-V with any DC's myself, I've had them go down for no reason or loose network connection, its just another point of failure to add to a DC in my opinion. By running a DC on a virtual host you are just adding to the things that can go wrong.

    I think the main concern would be with a failure of the hyper-V holding the Master controller DC, that would mean your couldn't log into the other hyper-v hosts.

  4. Thanks to zag from:

    Hightower (4th February 2011)

  5. #19

    Join Date
    Mar 2007
    Posts
    1,782
    Thank Post
    80
    Thanked 293 Times in 224 Posts
    Rep Power
    86
    Run at least one dc, even if its a nackered old box. If your vm infrastructure goes down you'll need a dc to recover!.

  6. Thanks to strawberry from:

    Hightower (4th February 2011)

  7. #20
    maark's Avatar
    Join Date
    Feb 2006
    Location
    leicester
    Posts
    473
    Thank Post
    90
    Thanked 74 Times in 66 Posts
    Rep Power
    38
    I have one physical DC and one on hyper v.
    Never had a problem with hyper v one but as pointed out if your whole hyper v setup went down you could find it tricky to get AD back up.

  8. Thanks to maark from:

    Hightower (4th February 2011)

  9. #21

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Well, I want three DC's on the three new servers. Is it even worth virtualising them then, or am I far better leaving them as physical machines with the Server 2k8 OS directly on them?

  10. #22

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    What about this - would this setup be fine?

    New Idea.png

    I was under the impression that the way I wanted to do it, if I lost a physical host the VM would failover to another host, thus keeping all three DC's up and running. What happens in this new example if I lose the first DC?

    If you had 3 new servers and a SAN, with ~700 users what would be your ideal setup?

  11. #23

    m25man's Avatar
    Join Date
    Oct 2005
    Location
    Romford, Essex
    Posts
    1,631
    Thank Post
    49
    Thanked 462 Times in 337 Posts
    Rep Power
    140
    in Blue Peter Fashion,
    Here's one I did earlier..

  12. #24

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241

  13. #25

    Join Date
    Mar 2007
    Posts
    1,782
    Thank Post
    80
    Thanked 293 Times in 224 Posts
    Rep Power
    86
    i'd keep the 3 vm hosts and just get something cheap to run as a dc, Use as many dc's as you need to load balance logons, but its worthwhile having at least one physical and one virtual in case of distaster recovery. prehaps use the physical dc as a backup server as well.

  14. Thanks to strawberry from:

    Hightower (4th February 2011)

  15. #26

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Quote Originally Posted by strawberry View Post
    i'd keep the 3 vm hosts and just get something cheap to run as a dc, Use as many dc's as you need to load balance logons, but its worthwhile having at least one physical and one virtual in case of distaster recovery. prehaps use the physical dc as a backup server as well.
    That's now what I'm thinking. Physical DC can just be DC/DHCP/DNS etc as well as backup and AV server. Then VM DC's (x2) can be file servers for users but do nothing else (except the jobs of a DC and file server).

    How's that sound? Physical DC to have RAID 1 HDD's for OS, and 2 Hyper-V boxes RAID 1 HDD's for Hyper-V OS, but everything else on SAN? Does that sound about right?

    M$ article here states: Planning Considerations for Virtualized Domain Controllers
    You should attempt to avoid creating potential single points of failure when you plan your virtual domain controller deployment. You can avoid introducing potential single points of failure by implementing system redundancy. For example, consider the following recommendations while keeping in mind the potential for increases in the cost of administration:

    • Run at least two virtualized domain controllers per domain on different virtualization hosts, which reduces the risk of losing all domain controllers if a single virtualization host fails.
    • As recommended for other technologies, diversify the hardware (using different CPUs, motherboards, network adapters, or other hardware) on which the domain controllers are running. Hardware diversification limits the damage that might be caused by a malfunction that is specific to a vendor configuration, a driver, or a single piece or type of hardware.
    • If possible, domain controllers should be running on hardware that is located in different regions of the world. This helps to reduce the impact of a disaster or failure that affects a site at which the domain controllers are hosted.
    • Maintain physical domain controllers in each of your domains. This mitigates the risk of a virtualization platform malfunction that affects all host systems that use that platform.
    It's all very interesting, but starting to make me VERY uncertain of which route I should head down.

    EDIT: My bad, didn't even read it properly lol. "Maintain physical domain controllers in each of your domains. This mitigates the risk of a virtualization platform malfunction that affects all host systems that use that platform." Well there we go. M$ advice to have physical too.
    Last edited by Hightower; 4th February 2011 at 01:13 PM.

  16. #27

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,220
    Thank Post
    873
    Thanked 2,716 Times in 2,301 Posts
    Blog Entries
    11
    Rep Power
    780
    Quote Originally Posted by Hightower View Post
    Microsoft recommend that a physical DC is running, and that virtualised servers are ran as member servers. As in my diagram here:

    Attachment 9362

    We want to run all our DC's as virtualised servers (otherwise what's the point of virtualising them in a failover way as we could lose the physical DC and be screwed) as in this diagram. Is this actually possible? Does anyone have their setup similar to this?

    Attachment 9363
    Yes its totally possible, the considerations are, don't image or snapshot a DC VM if you have more than one because it can mess the AD database. If your VM Hosts are domain joind they will have issues if they boot and can't talk to a DC. We got around this by putting a DC/Global catalogue on one of the VM host servers which handles the initial auth.

  17. #28

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Quote Originally Posted by SYNACK View Post
    Yes its totally possible, the considerations are, don't image or snapshot a DC VM if you have more than one because it can mess the AD database. If your VM Hosts are domain joind they will have issues if they boot and can't talk to a DC. We got around this by putting a DC/Global catalogue on one of the VM host servers which handles the initial auth.
    So you're running a Hyper-V cluster, and all your DC's are virtualised?

  18. #29

    Join Date
    Mar 2007
    Posts
    1,782
    Thank Post
    80
    Thanked 293 Times in 224 Posts
    Rep Power
    86
    its all about playing the odds, likelyhood of distaster x impact of disaster. Having one physical and one virtual dc is good sense, having antivirus on the physical is a waste, it should be on a singular vm for so it cna be recovered easily and moved between servers but it doens't need to be available for disaster recovery. File servers are fine virtual, but maybe have them use dfs to the physical dc so you have a live copy of the data and can change dfs to point to the dc is needed. Then look at things like dns, dhcp, make sure they're in more than one place and that a singular fault/event wont take them out.

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Anyone using Hyper-V?
    By gshaw in forum Windows Server 2008
    Replies: 20
    Last Post: 30th September 2010, 09:43 AM
  2. Hyper-V
    By leco in forum Windows Server 2008 R2
    Replies: 3
    Last Post: 7th April 2010, 07:49 PM
  3. Hyper V2
    By monkeyx in forum Windows Server 2008
    Replies: 7
    Last Post: 11th November 2009, 06:38 PM
  4. DO NOT SNAPSHOT HYPER-V DC!!!!!!!
    By AWicher in forum Thin Client and Virtual Machines
    Replies: 20
    Last Post: 19th August 2009, 10:34 PM
  5. My first play with Hyper-V
    By localzuk in forum Windows Server 2008
    Replies: 30
    Last Post: 6th March 2009, 01:16 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •