The topic you requested could not be found.
Related topics are listed below.

Windows Server 2012 MMC Snap-in Crash

DataKeeper Cluster Edition Technical Documentation » DataKeeper Troubleshooting » Known Issues and Workarounds » Windows Server 2012 Specific Issues » Windows Server 2012 MMC Snap-in Crash

Description When using the DataKeeper user interface (MMC Snap-in) on Windows Server 2012, the mmc.exe process may crash unexpectedly due to an internal .Net or Windows Presentation Foundation (WPF) issue. The error may show up on the screen and/or the event…

Extending a Traditional 2-Node Cluster to a Shared-Replicated Configuration

DataKeeper Cluster Edition Technical Documentation » User Guide » Clustering » Extending a Traditional 2-Node Cluster to a Shared-Replicated Configuration

Add a Shared Node Using Windows Server 2008R2 or 2012 When using Windows Server 2008R2 or 2012, a 1×1 2-Node replicated cluster using DataKeeper Volumes can be extended to a 2×1 shared and replicated 3-Node cluster by using either of the following…

Windows Server 2012 Specific Issues

DataKeeper Cluster Edition Technical Documentation » DataKeeper Troubleshooting » Known Issues and Workarounds » Windows Server 2012 Specific Issues

For issues related to Windows Server 2012, see the following topics: __________________________________________________________________________________________________________________ Windows Server 2012 MMC Snap-in Crash Windows Server 2012 DataKeeper Switchover…

WSFC 2008 R2 SP1 Procedure Change

DataKeeper Cluster Edition Technical Documentation » DataKeeper Troubleshooting » Known Issues and Workarounds » WSFC 2008 R2 SP1 Procedure Change

Description When using WSFC 2008 R2 SP1, the procedure for Extending a Traditional 1×1 2-Node WSFC Cluster to a Shared-Replicated 3-Node Cluster has changed. The WSFC mmc GUI must not be used for adding a node that is hosting a DataKeeper shared…

User Interface

DataKeeper Cluster Edition Technical Documentation » SIOS DataKeeper Cluster Edition Introduction » User Interface

SIOS DataKeeper User Interface The SIOS DataKeeper User Interface uses a standard MMC snap-in interface. The left pane displays the Console Tree view. This includes the Jobs and Reports. Currently, there are two reports available – Job Overview and Server…

SIOS DataKeeper Cluster Edition Introduction

DataKeeper Cluster Edition Technical Documentation » SIOS DataKeeper Cluster Edition Introduction

SIOS DataKeeper Overview DataKeeper with High Availability – Cluster Edition Overview SIOS DataKeeper is a highly optimized host-based replication solution which ensures your data is replicated as quickly and as efficiently as possible from your source server…

Components

DataKeeper Cluster Edition Technical Documentation » SIOS DataKeeper Cluster Edition Introduction » Components

DataKeeper Components SIOS DataKeeper for Windows is comprised of the following components: DataKeeper Driver (ExtMirr.sys) – The DataKeeper Driver is a kernel mode driver and is responsible for all mirroring activity between the mirror…

Extending a Traditional 2-Node WSFC Cluster to a Third Node via DataKeeper

DataKeeper Cluster Edition Technical Documentation » User Guide » Clustering » Extending a Traditional 2-Node WSFC Cluster to a Third Node via DataKeeper

When replicating from a WSFC 2-node cluster to a third node via DataKeeper, the following tasks are required: Replace the existing WSFC physical disk resource with a DataKeeper volume resource that supports data replication. Change the quorum type to Node…

Third Party Product Files

DataKeeper Cluster Edition Installation Guide » Installation » Third Party Product Files

The following third party files were not developed by SIOS Technology Corp. but are installed during the SIOS Protection Suite/DataKeeper installation process. Path and File Name Provider Purpose…

Known Issues and Workarounds

DataKeeper Cluster Edition Technical Documentation » DataKeeper Troubleshooting » Known Issues and Workarounds

Included below are known issues open against DataKeeper and DataKeeper Cluster Edition as well as possible workarounds and/or solutions. __________________________________________________________________________________________________________________ Access to…

Extending a Traditional 2-Node WSFC SQL Server Cluster to a Third Node via DataKeeper

DataKeeper Cluster Edition Technical Documentation » User Guide » Clustering » Extending a Traditional 2-Node WSFC SQL Server Cluster to a Third Node via DataKeeper

When replicating from a WSFC SQL Server 2-node cluster to a third node via DataKeeper, the following tasks are required: Replace the existing WSFC physical disk resource with a DataKeeper volume resource that supports data replication. Change the quorum type to…

DataKeeper Cluster Edition Release Notes

DataKeeper Cluster Edition Release Notes

SIOS DataKeeper Cluster Edition Release Notes Version 8.6.3 (Version 8 Update 6 Maintenance 3) !IMPORTANT: If using Windows 2008 R2 SIOS DataKeeper includes a kernel-mode driver (ExtMirr.sys) which is signed with a SHA-256 signature. If you are…

DataKeeper Troubleshooting

DataKeeper Cluster Edition Technical Documentation » DataKeeper Troubleshooting

The topics in this section contain important information about known issues and restrictions offering possible workarounds and/or solutions. ________________________________________________________________________________________________________________ Known Issues…

Installing Core

DataKeeper Cluster Edition Installation Guide » Installation » Installing Core

Installing the DataKeeper Cluster Edition Core Software SIOS DataKeeper Cluster Edition uses the Flexera InstallShield product to provide a standard installation interface. A license must be obtained and installed for each server in the cluster. We recommend that you…

Extending a Clustered DataKeeper Volume to a Node Outside the Cluster

DataKeeper Cluster Edition Technical Documentation » User Guide » Clustering » Extending a Clustered DataKeeper Volume to a Node Outside the Cluster

DataKeeper Volume cluster resources can be extended to a DR Node for Disaster Recovery purposes. In the event of a complete failure of all systems in the cluster, data will be accessible on the DR Node (referred to as the “DR Node”). Here you will find instructions…