MySQL with Windows Server 2008 R2 Failover Clustering

Windows Server 2008 R2 Failover Clustering

Oracle has announced support for running MySQL on Windows Server Failover Clustering (WSFC); with so many people developing and deploying MySQL on Windows, this offers a great option to add High Availability to MySQL deployments if you don’t want to go as far as deploying MySQL Cluster.

This post will give a brief overview of how to set things up but for all of the gory details a new white paper MySQL with Windows Server 2008 R2 Failover Clustering is available – please give me any feedback. I will also be presenting on this at a free webinar on Thursday 15th September (please register in advance) as well at an Oracle OpenWorld session in San Francisco on Tuesday 4th October (Tuesday, 01:15 PM, Marriott Marquis – Golden Gate C2) – a good opportunity to get more details and get your questions answered.

It sometimes surprises people just how much MySQL is used on Windows, here are a few of the reasons:

  • Lower TCO
    • 90% savings over Microsoft SQL Server
    • If your a little skeptical about this then try it out for yourself with the MySQL TCO Savings Calculator
  • Broad platform support
    • No lock-in
    • Windows, Linux, MacOS, Solaris
  • Ease of use and administration
    • < 5 mins to download, install & configure
    • MySQL Enterprise Monitor & MySQL WorkBench
  • Reliability
    • 24×7 Uptime
    • Field Proven
  • Performance and scalability
    • MySQL 5.5 delivered over 500% performance boost on Windows.
  • Integration into Windows environment
    • ADO.NET, ODBC & Microsoft Access Integration
    • And now, support for Windows Server Failover Clustering!
Probably the most common form of High Availability for MySQL is MySQL (asynchronous or semi-synchronous replication) and the option for the highest levels of availability is MySQL Cluster. We are in the process of rolling out a number of solutions that provide levels of availability somewhere in between MySQL Replication and MySQL Cluster; Oracle VM Template for MySQL Enterprise Edition was the first (overview, webinar replay, white paper) and WSFC is the second.


Solution Overview

MySQL with Windows Failover Clustering requires at least 2 servers within the cluster together with some shared storage (for example FCAL SAN or iSCSI disks). For redundancy, 2 LANs should be used for the cluster to avoid a single point of failure and typically one would be reserved for the heartbeats between the cluster nodes.

The MySQL binaries and data files are stored in the shared storage and Windows Failover Clustering ensures that at most one of the cluster nodes will access those files at any point in time (hence avoiding file corruptions).

Clients connect to the MySQL service through a Virtual IP Address (VIP) and so in the event of failover they experience a brief loss of connection but otherwise do not need to be aware that the failover has happened other than to handle the failure of any in-flight transactions.

Target Configuration

This post will briefly step through how to set up and use a cluster and this diagrams shows how this is mapped onto physical hardware and network addresses for the lab used later in this post. In this case, iSCSI is used for the shared storage. Note that ideally there would be an extra subnet for the heartbeat connection between ws1 and ws3.

This is only intended to be an overview and the steps have been simplified refer to the white paper for more details on the steps.


  • MySQL 5.5 & InnoDB must be used for the database (note that MyISAM is not crash-safe and so failover may result in a corrupt database)
  • Windows Server 2008 R2
  • Redundant network connections between nodes and storage
  • WSFC cluster validation must pass
  • iSCSI or FCAL SAN should be used for the shared storage

Step 1 Configure iSCSI in software (optional)

Create 2 clustered disks

This post does not attempt to describe how to configure a highly available, secure and performant SAN but in order to implement the subsequent steps shared storage is required and so in this step we look at one way of using software to provide iSCSI targets without any iSCSI/SAN hardware (just using the server’s internal disk). This is a reasonable option to experiment with but probably not what you’d want to deploy with for a HA application. If you already have shared storage set up then you can skip this step and use that instead.

As part of this process you’ll create at least two virtual disks within the iSCSI target; one for the quorum file and one for the MySQL binaries and data files. The quorum file is used by Windows Failover Clustering to avoid “split-brain” behaviour.

Step 2. Ensure Windows Failover Clustering is enabled

Ensure that WSFC is enabled

To confirm that Windows Failover Clustering is installed on ws1 and ws3, open the “Features” branch in the Server Manager tool and check if “Failover Cluster Manager” is present.

If Failover Clustering is not installed then it is very simple to add it. Select “Features” within the Service Manager and then click on “Add Features” and then select “Failover Clustering” and then “Next”.



Step 3. Install MySQL as a service on both servers

Install MySQL as a Windows Service

If MySQL is already installed as a service on both ws1 and ws3 then this step can be skipped.

The installation is very straight-forward using the MySQL Windows Installer and selecting the default options is fine.

Within the MySQL installation wizard, sticking with the defaults is fine for this exercise. When you reach the configuration step, check “Create Windows Service”.

The installation and configuration must be performed on both ws1 and ws2, if necessary.

Step 4. Migrate MySQL binaries & data to shared storage

If the MySQL Service is running on either ws1 or ws3 then stop it – open the Task Manager using ctrl-shift-escape, select the “Services” tab and then right-click on the MySQL service and choose “Stop Service”.

As the iSCSI disks were enabled on ws1 you can safely access them in order to copy across the MySQL binaries and data files to the shared disk.

Step 5. Create Windows Failover Cluster

Create the Cluster (without MySQL)

From the Server Manager on either ws1 or ws3 navigate to “Features -> Failover Cluster Manager” and then select “Validate a Configuration”. When prompted enter ws1 as one name and then ws3 as the other.

In the “Testing Options” select “Run all tests” and continue. If the tests report any errors then these should be fixed before continuing.

Now that the system has been verified, select “Create a Cluster” and provide the same server names as used in the validation step. In this example, “MySQL” is provided as the “Cluster Name” and then the wizard goes on to create the cluster.

Step 6. Create Cluster of MySQL Servers within Windows Cluster

Cluster the MySQL Service

Adding the MySQL service to the new Cluster is very straight-forward. Right-click on “Services and applications” in the Server Manager tree and select “Configure a Service or Application…”. When requested by the subsequent wizard, select “Generic Service” from the list and then “MySQL” from the offered list of services. Our example name was “ClusteredMySQL”. Please choose an appropriate name for your cluster. The wizard will then offer the shared disk that has not already been established as the quorum disk for use with the Clustered service – make sure that it is selected.

Once the wizard finishes, it starts up the MySQL Service. Click on the “ClusteredMySQL” service branch to observe that the service is up and running. You should also make a note of the Virtual IP (VIP) assigned, in this case

Step 7. Test the cluster

As described in Step 6, the VIP should be used to connect to the clustered MySQL service:

From there create a database and populate some data.

Migrate MySQL Service Across Cluster

The MySQL service was initially created on ws1 but it can be forced to migrate to ws3 by right-clicking on the service and selecting “Move this service or application to another node”.

As the MySQL data is held in the shared storage (which has also been migrated to ws3), it is still available and can still be accessed through the existing mysql client which is connected to the VIP:

Note the error shown above – the mysql client loses the connection to the MySQL service as part of the migration and so it automatically reconnects and complete the query. Any application using MySQL with Windows Failover Cluster should also expect to have to cope with these “glitches” in the connection.


More users develop and deploy and MySQL on Windows than any other single platform. Enhancements in MySQL 5.5 increased performance by over 5x compared to previous MySQL releases. With certification for Windows Server Failover Clustering, MySQL can now be deployed to support business critical workloads demanding high availability, enabling organizations to better meet demanding service levels while also reducing TCO and eliminating single vendor lock-in.
Please let me know how you get on by leaving comments on this post.

 9,680 total views,  16 views today

16 thoughts on “MySQL with Windows Server 2008 R2 Failover Clustering

  1. thanks for your guide!I settup SQL 2008 Cluster on 2 server 2008 already.Now i want to install MySQL 5.5 cluster on them.But..i don’t know how to do “Step 4. Migrate MySQL binaries & data to shared storage”.
    It’s my final project in my school.Thanks in advange!!!I am very appreciated for your reply ASAP to .
    Thank you once more!!!!(I’M Vietnamese)

  2. thanks for your reply.I’m setup ok.but it still error.The ClusterMySQL just failback on node1.On node2 I can’t start the service MySQL and get error “System error 1067 has occured.The process terminated unexpectedly”.When i change “my.ini” to default basedir & datadir it start normaly.
    Can you help me to fix it!?please!!!

  3. dear Admin,
    very helpful and very clear document.
    But I wold like to request one more thing.
    we want to implement a web portal using Apache, Tomcat and MySQL.
    now I know about MySQL HA configuration, so can you help me for HA configuration for web portal. I meant can I configure the same ways for apache and tomcat like MySQL?
    How can I configure for all services, if one service fail, all service need to move to another node.
    really appreciate for any advice.

    Thanks in advance.
    Thu Ya

  4. Hi,

    I configured and cluster drive is working fine.But mysql service cannot start automatically.
    Any idea, please?

    Thu Ya

  5. Error 1130 has occurred while connecting to mysql using virtual ip

    Could you please let me know the solution

    1. It looks like you’re trying to connect from a user/host combination that isn’t allowed – try this (substituting your username and host IP)…

      mysql> grant all on *.* to ‘username’@’’;

  6. What is the point of copying and updating the basedir to “basedir=”F:/MySQL Server 5.5”” ?

    The service has the hardcoded path below. If I set the basedir to my iscsi path of F:/MySQL Server 5.5, the service won’t start. Since mysql is installed on both servers, what is the point of putting the binaries on shared storage where they could just be accessed locally? Is it needed for the failover cluster? If so, does the service need to be modified?

    “C:/MySQL/MySQL Server 5.6/binmysqld” –defaults-file=”C:MySQLmy.ini” MySQL

    1. The advantage of using binaries on the shared storage is that you can be confident that the exact same version of the MySQL software will be used, if you were using local copies then you’d need to ensure that each had the same version of MySQL. The referenced white paper does describe how to update the service. Note that the paper is based on MySQL 5.5 but as far as I’m aware it should translate easily enough to MySQL 5.6.


      1. Hi Andrew,
        I am unable to configure MySQL 5.6 on windows cluster. I found my.ini file is inside the progaramdata folder instead of program files folder (5.5). Please help me if you know how to configure Mysql 5.6 on windows failover clustering.

        1. Have you tried either copying the .ini file or specifying its location using the –defaults-file option?

          1. hi I have the same issue as Sunil, and is true that the my.ini file is in ProgramData which is is initially hidden. And the my-default.ini is in the Program Files/Mysql.. and these two files are different, so I cannot change the datadir in the my.ini. If you anything I can do because my failover cluster is up and everything running and my virtual disks are healthy, but when I create one database in one machine it does not replicate in the other one. It is really strange because my my-default.ini are pointing to my virtualdisk.

            Thank you for reading, hope if you can help me.

Comments are closed.