SIOS DataKeeper Cluster Edition
(Version 8 Update 8 Maintenance 2)
Released January 13, 2022
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 2019, 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
|New in This Release|
|Windows Server 2022 Support|
|Windows 2011 Support|
|Fixed memory leak in ExtMirrSvc. See this IMPORTANT NOTICE for more information.|
|New in Version 8.8.1|
|New in Version 8.8.0|
|New in Version 8.7.2|
|Support for VMware vSphere 7.0
See the Support Matrix for supported configuration details.
|New in Version 8.7.1|
|DataKeeper Cluster Edition now supports Azure Stack on Windows 2019|
|New in Version 8.7.0|
|Full Support of Windows 2019 with Secure Boot|
|DataKeeper now supports AWS Nitro System|
|New in Version 8.6.5|
|New in Version 8.6.4|
|DataKeeper now supports Windows 2019 (Restrictions v8.6.4 only)|
|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.|
|New in Version 8.6.3|
|This Performance Monitor Counter value is the age of the oldest write request in the write queue. Refer to Queue Current Age.|
|New in Version 8.6.2|
|DataKeeper now includes the DataKeeper Signal package to deliver events to SIOS iQ.|
|New in Version 8.6.1|
|New in Version 8.6|
|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.|
|New in Version 8.5.1|
|DataKeeper now supports Windows 2016.|
|SIOS VSS Provider has been disabled by default.|
|New in Version 8.5|
|CHANGEMIRRORTYPE command is used to change the mirror type of a mirror that is part of a DataKeeper job.|
|Users can modify the effective size of an entry in the DataKeeper intent log (bitmap) by changing the BitmapBytesPerBlock registry value.|
|New in Version 8.4|
|DataKeeper Volume Resource Health Check determines if the underlying volume device becomes unreachable.|
|Target writes are now tracked in a persistent target bitmap file.|
|New in Version 8.3|
|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.|
|mirrorcleanup.cmd 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 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).|
|DKHEALTHCHECK .Support status and issue identification tool. Provides command line interface for basic mirror status and problem detection.|
|New in Version 8.2.1|
|New in Version 8.2|
|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.|
|New in Version 8.1|
|New in Version 8.0.1|
|New in Version 8.0.|
|DataKeeper now allows you to have a replication target which resides outside of the failover cluster.|
|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.|
|DataKeeper now supports Windows 2012 R2.|
The following is a list of the latest bug fixes and enhancements.
|PW-5495||Fixed memory leak in ExtMirrSvc|
|steeleye-lkHOTFIX-Gen-LB-PL-7172-9.5.1-7154.x86_64.rpm||Support for load balancers in Microsoft Azure and Google Cloud Platform||The Generic ARK for Load Balancer probe reply (Gen LB) provides a mechanism to receive and respond to a health check probe for load balancer target instances of load balancer instances in Microsoft Azure (Azure) and Google Cloud Platform (GCP) environments.|
|steeleye-lkHOTFIX-core-PL-11771-9.6.0-7333.x86_64.rpm||This patch fixes a problem related to failures during switchover of NFS hierarchies. In particular, in SAP environments, the fuser process has been observed to hang.||This patch avoids problematic hangs related to the fuser process.|
|steeleye-lkHOTFIX-ROUTE53-PL-11129-9.6.0-7333.noarch.rpm||Addresses failure of the Route53 recovery kit when accessing the AWS CLI from nodes without internet access or configured AWS role.||This patch exports NO_PROXY within the value_domain script prior to attempting an AWS CLI call.|
|steeleye-lkHOTFIX-SAP-PL-13003-9.6.0-7333.x86_64.rpm||Due to a change made in the SAP HA Script Connector Library, interprocess communication may fail between the SAP HA Script Connector Library and SAP SIOS HA Cluster Connector routines on the affected SAP kernel versions and patch levels listed below.||This patch allows SIOS SAP HA Cluster Connector routines to communicate successfully with the SAP HA Script Connector Library on the affected SAP kernel versions and patch levels listed above.|
DataKeeper Cluster Edition Requirements
|Server Components||See the DKCE Support Matrix
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.
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.
Contact Microsoft for a fix 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.)
|User Interface|| See the DKCE Support Matrix
System Requirements for DataKeeper
|Memory (with no mirrors or jobs configured)||
Baseline Memory Usage:
Total = 167,277.7KB or 167.28 MB
|Processor||Refer to Windows Processor Requirements.|
|Disk size||667 MB|
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.
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
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 SIOS DataKeeper Cluster Edition, refer to the DataKeeper Cluster Edition Quick Start Guide.