Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Hyper-V Failover Clustering

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    2 Posts 2 Posters 72 Views
    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.
    • B
      bimmerdriver
      last edited by

      I've been running pfSense on Windows Server 2022 Hyper-V. The server has a 2-port I350 NIC for LAN and WAN. I'm setting up another Windows Server 2022, also with a 2-port I350 NIC. I would like to set up up the second server to run a backup pfSense in case of a hardware failure or some other outage.

      I understand from reading about CARP/HA that I would need static addresses to use that method of HA. My ISP allows multiple independent IPv4/IPv6 connections but they aren't static.

      I'm wondering about using Windows Server Failover Clustering. Is it a viable way to provide high availability?

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @bimmerdriver
        last edited by

        @bimmerdriver You need one IP that can move between the routers. Technically both WANs can be private IPs…Comcast business allows for this even if their modem is bridged, then the shared IP is a public. Maybe that helps.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.