SIOS DataKeeper Cluster Edition
(Version 8 Update 6 Maintenance 4)
Released April 25, 2019
Read This Document Before Attempting To Install Or Use This Product!
This document contains last minute information that must be considered before, during and after installation.
SIOS Datakeeper Cluster Edition is a highly optimized host-based replication solution which integrates seamlessly with Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2008 R2/2008 R2 SP1 Failover Clustering. Features of Windows Server Failover Clustering such as cross-subnet failover and tunable heartbeat parameters make it easy for administrators to deploy geographically dispersed clusters. SIOS DataKeeper provides the data replication mechanism which extends both versions of Windows Clustering, allowing administrators to take advantage of these advanced features to support non-shared disk high availability configurations.
Once SIOS DataKeeper Cluster Edition is installed, a new storage class resource type called DataKeeper Volume is available. This new SIOS DataKeeper Volume resource can be used in place of the traditional Physical Disk shared storage resource to enable geographically dispersed clusters, also known as multi-site clusters.
New Features of SIOS DataKeeper Cluster Edition v8
|Windows 2019 Support
|DataKeeper now supports Windows 2019 (Restrictions)
|Delay Writes when Write Queue limit is reached
|Introduced the BlockWritesOnLimitReached tunable, which will delay writes when a mirror’s queue reaches the HighWater or ByteLimit, rather than pausing the mirror and going into a resync state.
|Queue Current Age
|This Performance Monitor Counter value is the age of the oldest write request in the write queue.
|Integration with SIOS iQ
|DataKeeper now includes the DataKeeper Signal package to deliver events to SIOS iQ.
|Microsoft SQL Server 2017 Support
|DataKeeper supports Microsoft SQLServer 2017.
|Tunable Write Queue Byte Limit
|Users can specify the maximum number of bytes that can be allocated for the write queue of a mirror by changing the WriteQueueByteLimitMB registry value.
|Windows 2016 Support
|DataKeeper now supports Windows 2016.
|SIOS VSS Provider has been disabled by default.
|This EMCMD command is used to change the mirror type of a mirror that is part of a DataKeeper job.
|Tunable bitmap block size
|Users can modify the effective size of an entry in the DataKeeper intent log (bitmap) by changing the BitmapBytesPerBlock registry value.
|DataKeeper Volume Resource Health Check
|DataKeeper Volume Resource Health Check determines if the underlying volume device becomes unreachable.
|Target Bitmap File
|Target writes are now tracked in a persistent target bitmap file.
|DataKeeper Notification Icon
|The DataKeeper Notification Icon shows a summary of your DataKeeper mirrors in the Windows Notification Tray. In addition to the display functions, the DataKeeper Notification Icon also serves as a shortcut to managing your DataKeeper mirrors.
|This command will remove all remnants of a mirror for a selected volume on the local system only and should only be run when recommended by SIOS Support.
|Powershell cmdlet support
|Powershell cmdlets that can be used to create job(s), create mirror(s), remove job(s), remove mirror(s) and fetch information about a volume used in DataKeeper (New-DataKeeperMirror, New-DataKeeperJob, Remove-DataKeeperMirror, Remove-DataKeeperJob, Add-DataKeeperJobPair, Get-DataKeeperVolumeInfo).
|Support status and issue identification tool. Provides command line interface for basic mirror status and problem detection.
|DataKeeper Non-Mirrored Volume Cluster Resource
|The DataKeeper Non-Mirrored Volume Cluster Resource allows users to use a local volume in a failover cluster without requiring that it be part of a mirror. Some of the common use cases for this feature include enabling rolling cluster OS upgrades on existing hardware and moving tempdb to local storage in SQL 2008 R2 clusters and earlier.
|Replicate to Node Outside of Cluster
|DataKeeper now allows you to have a replication target which resides outside of the failover cluster.
|Operating System Support
|DataKeeper now only supports Windows 2008R2 and later 64-bit Operating Systems. To run on an earlier version of Windows or on 32-bit systems, you must use DataKeeper v7.
|Windows 2012 R2 Support
|DataKeeper now supports Windows 2012 R2.
The following is a list of the latest bug fixes and enhancements.
|DKCE did not resolve split brain
|BSOD on shutdown if volume goes offline just after boot time on target node
|emcmd SETSNAPSHOTLOCATION command does not validate the snapshot path
|Briefly delay writes to allow resync to complete
|DKCE logs error events continuously when DataKeeper Volume resource is created with no physical volume on the current node
|Memory leak – shared disk taken offline / online
|Implement BlockWritesOnLimitReached tunable
|License Manager not working properly in some locales (date calculations)
|License Manager incorrectly reports invalid host ID
|Removed rewind from DataKeeper
|Remove non-mirroring target nodes from Possible Owners list
|Remove shared target nodes from Possible Owners list
|Prevent product installation on Windows 2019 systems with Secure Boot enabled
|Possible data corruption if unlocked target is rebooted
Product Definitions and Platforms
|See the DKCE Support Matrix
| Hotfix – KB 951308
If protecting Hyper-V resources, Hotfix KB 958065
Note: These hotfixes are not required for Windows Server 2008 R2/2008 R2 SP1.
Microsoft Hotfix KB 2741477 is now available that will allow NICs to be added to a Virtual Machine after the VM has been placed into a Failover Cluster. (For more information, see Hyper-V Host Cluster Error.)
|See the DKCE Support Matrix
| MMC 3.0 – download from:
Note: All servers should run the same version of Windows and the same version of DataKeeper software.
Make sure you verify the following settings prior to installing and configuring SIOS DataKeeper Cluster Edition.
- Important: SIOS Technology Corp. recommends that users use Domain accounts that have local Admin privileges on all servers running DataKeeper. If you are using Local accounts, the username and passwords must match on all servers running DataKeeper. This recommendation is for all editions and all platforms.
- Follow Microsoft best practices for deploying geographically dispersed clusters, including changing the quorum mode majority node setting with a file share witness.
- DataKeeper Failover Cluster registration is automatic and occurs 60 seconds after the following events have occurred on each cluster node:
- A DataKeeper Cluster Edition license has been installed on each cluster node.
- The Windows server Failover Clustering feature has been installed on each server.
- A Windows server Cluster configuration has been formed.
Local Security Policy Requirement
If your Windows servers are not in a domain and you are going to run the DataKeeper Service as the local system account, the Local Security policy setting “Network Access: Let Everyone permissions apply to anonymous users” must be enabled.
Microsoft has introduced new driver signing restrictions with Windows Server 2019. Windows 2019 systems that are configured with the Secure Boot UEFI BIOS feature enabled will not boot if any SIOS product is installed unless Windows Driver Signing checks are disabled. Disabling driver signing checks is an interactive task that has to be done each time the system is booted. To use any SIOS product with Windows 2019 either disable Secure Boot in the UEFI BIOS settings or use a legacy BIOS bootloader.
Cloud environments such as AWS and Azure do not currently enable Secure Boot and it is not anticipated that this will change. However, given the uncertainty of the current and future status of Secure Boot use in the various cloud environments, we do not recommend or support running SIOS products on any production Windows Server 2019 workloads hosted in a 3rd-party Cloud environment.
The restriction regarding Secure Boot will be addressed in a future SIOS product release.
If using DataKeeper with SCVMM 2012, you must use SCVMM 2012 SP1.
Windows Server 2012
For issues and enhancements related to Windows Server 2012, see the following topics:
WSFC 2012 Failover Cluster Manager UI Defect
WSFC 2012 New File Server Type Not Supported
Manual Creation of a Mirror in WSFC
WSFC 2012 Cluster Creation Default Setting Issue
WSFC 2012 File Shares Cannot be Created for File Server Resource
WSFC 2012 Server Manager — Incorrect Volume Display
WSFC 2012 Server Manager — DataKeeper “Disk” Not Shown as Clustered
Windows Server 2012 Default Information Missing During Mirror Creation
Windows Server 2012 DataKeeper MMC Snap-in Crash
Windows Server 2012 — Simultaneous Move of Multiple Clustered File Server Roles Can Result in DataKeeper Switchover Failures
Windows Server 2012 iSCSI Target Role Does Not Support Dynamic Disks
Using iSCSI Target with DataKeeper
Windows 2008 R2
SIOS DataKeeper includes a kernel-mode driver (ExtMirr.sys) which is signed with a SHA-256 signature. If you are installing on a Windows 2008 R2 system that has not been updated with Microsoft hotfixes, it might not be able to boot with such a driver. Please refer to this bulletin from Microsoft for more information, in particular the first event listed which applies to Windows 2008 R2 SP1.
If you are updating SIOS DataKeeper, and your previous version was version 8.6.2 or later, then your system does have SHA-256 driver support (the 8.6.2 driver is signed with SHA-256). In that case you can safely install this version of DataKeeper.
DataKeeper Cluster Edition Quick Start Guide
To get started using SteelEye DataKeeper Cluster Edition, refer to the DataKeeper Cluster Edition Quick Start Guide.