ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Solved Hyper-V Failover Clustering

    IT Discussion
    hyper-v replication failover-clustering
    5
    7
    227
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403
      DustinB3403 last edited by

      Anyone know if Failover Clustering can be enabled on two existing Hyper-V hosts with VMs running, and replication occurring between the two hosts for a single VM?

      travisdh1 1 Reply Last reply Reply Quote 0
      • travisdh1
        travisdh1 @DustinB3403 last edited by

        @DustinB3403 said in Hyper-V Failover Clustering:

        @travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.

        Looking at different ways to try and remediate this from occurring again.

        You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.

        Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.

        J Dashrender 2 Replies Last reply Reply Quote 3
        • travisdh1
          travisdh1 @DustinB3403 last edited by

          @DustinB3403 said in Hyper-V Failover Clustering:

          Anyone know if Failover Clustering can be enabled on two existing Hyper-V hosts with VMs running, and replication occurring between the two hosts for a single VM?

          Can it be, sure. Does anyone in their right mind want to tackle it, nope.

          The pain point will be getting the storage setup to make it happen. My first thought would be a couple Starwind VMs to handle storage replication for that VM. Lots of overhead for not much gained I don't think.

          Does it have to be true HA? Could they survive 5-10 minutes for Veeam to boot a backup copy if the VM goes down?

          DustinB3403 1 Reply Last reply Reply Quote 0
          • DustinB3403
            DustinB3403 @travisdh1 last edited by

            @travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.

            Looking at different ways to try and remediate this from occurring again.

            travisdh1 1 Reply Last reply Reply Quote 0
            • travisdh1
              travisdh1 @DustinB3403 last edited by

              @DustinB3403 said in Hyper-V Failover Clustering:

              @travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.

              Looking at different ways to try and remediate this from occurring again.

              You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.

              Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.

              J Dashrender 2 Replies Last reply Reply Quote 3
              • J
                Jimmy9008 @travisdh1 last edited by

                @travisdh1 said in Hyper-V Failover Clustering:

                @DustinB3403 said in Hyper-V Failover Clustering:

                @travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.

                Looking at different ways to try and remediate this from occurring again.

                You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.

                Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.

                I agree with one DC on each host. Otherwise, that is a lot of additional complexity to have a cluster and shared storage just for this one issue...

                1 Reply Last reply Reply Quote 2
                • Dashrender
                  Dashrender @travisdh1 last edited by

                  @travisdh1 said in Hyper-V Failover Clustering:

                  Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.

                  This was my same thinking.

                  1 Reply Last reply Reply Quote 0
                  • dbeato
                    dbeato last edited by

                    You can have replication if you have Starwind Clustering on the hosts (That's how I have some customers). That said, even on those situations I have a DC on the Local Host Hyperv of one of the servers or have a Site to Site VPN with a DC on Azure or AWS as a failsafe.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post