Welcome back to the second part of the blog where we talk about implementing SIOS DataKeeper Cluster Edition, this blog will show you how to configure & set up DataKeeper.

Part 1: Installing SIOS DataKeeper

Step 1: Install SIOS DataKeeper onto your servers, make sure it’s installed on all devices.

Make sure you have chosen the correct version of the DataKeeper setup.

Step 2: click on the DataKeeper Setup, and go through the wizard. This is just the wizard to configure setting DataKeeper up, once you have completed it, you will no longer use this unless you need to repair or modify DataKeeper.

Step 3: Go through & check the service logon account setup is how you want it, this can be a domain server account or LocalSystem Account, it depends on how you want your setup, but for this instance, we are going with domain as it is recommended.

Step 4: on the next page you will see your userID, the userID is automatically populated, so we entered in a password that we would like to use to log in.

Step 5: once you have completed going through the wizard, you will be met with the SIOS license key manager, this is what you will need to activate your license, click on Install License File, open up another box & press license file browser, search for your license, select it.

Please note: licenses can be obtained from the license portal or to get in touch (contact form link) to discuss trial licenses.

Step 6: once you have selected your License, it will show here, with the information & expiry date. Once you have done this you are ready to load into DataKeeper. Click exit, the pop up will show, you will have the option to restart or do it later. Make sure you have done this on both or more servers.

Part 2: Connecting to servers & creating a job.

Step 1: Once you have installed DataKeeper, open it up, and you will see the main screen & click connect to a server, it will bring up this pop-up where you will enter the IP address, servername or FQDN (fully qualified domain name) of the server you want to connect to.

On the right hand side, you will see Actions, you can see multiple options here if they don’t show up in the middle.

Step 2: Once you have entered the IP address, select on the main page again Create A New Job, which will open this pop-up, enter the information such as name & description & create job, and it will take you through the New Mirror wizard.

Please note: Check that both disks are to be identical in size and be online and formatted. You can check this in Disk Management.

If the options are empty when selecting a source or mirror target, then it is a sign that there is no disk suitable for replication, this might be due to disk size differences, offline disks, page files, or corrupted file systems, you will need to investigate to resolve this.

Step 3: Once happy, click next to Choose A Target, check the details but all should be correct, click next to configure details & complete the wizard. Once you have, this pop-up will show about auto-registering for WSFC, click yes.

Step 4: Once you have selected yes, it will take a minute to create the job, then inside DataKeeper GUI you will see your jobs. You can see the information of the Name, description, the job state whether its mirroring or paused etc.

The DataKeeper Volume can now be assigned to a role, ensure that the dependencies are correctly configured for the role then test the failover in both directions to ensure everything is configured correctly.


Creating a Windows Server Failover Cluster involves navigating a labyrinth of technical complexities and ensuring meticulous configuration to achieve high availability and disaster recovery for critical applications. The process demands a deep understanding of Windows Server environments, network settings, shared storage configurations, and more. Recognizing the intricate challenges you may face, our team is dedicated to simplifying this journey for you. With our expertise in Microsoft technologies, we are here to guide you through every step of creating a robust failover cluster, ensuring your systems are resilient against failures.