Included below are known issues open against DataKeeper and DataKeeper Cluster Edition as well as possible workarounds and/or solutions.
__________________________________________________________________________________________________________________
- Split-brain Can Occur in DataKeeper Even When Quorum/Witness is Configured
- Access to Designated Volume Denied
- Antivirus Software Exclusion List for LifeKeeper and DataKeeper for Windows
- Bitmap Writes Unexpectedly Fail When Any Volume is Removed (disk offline or partition deleted)
- DataKeeper Does Not Support Lowercase Drive Letters as Mirror Endpoint for Jobs
- DataKeeper Volume Not Available as Cluster Resource Type
- During an upgrade, the GUI shows the incorrect state for the target server
- Error Creating a Mirror, return value 61 when extending a Volume in the LK for Windows GUI
- Failed/Delayed Updating Status
- Failed to Create Mirror
- Failed to create the file needed for quorum
- Hyper-V Host Cluster Error
- Live Migration Failure
- MaxResyncPasses Value
- Dangling Sources
- Mirroring with Dynamic Disks
- New Resources Offline But Unlocked
- Recover Kit for Route 53 Stops Working after Changing Instance Type
- Server Login Accounts and Passwords Must Be Same on Each Server in the Cluster
- System Event Log – Create Mirror Failed in the GUI
- Unable to Determine Previous Install Path
- Unexpected Order of the Upper Filters List May Cause Inability to Boot or Inability to Create Page Files
- User Interface – Failed to Create Mirror
- User Interface – Shows Only One Side of the Mirror
- Updating OpenJDK to v24.0.1 disables allowing a Security Manager for any Java process
- Windows Restore result shared storage in a locked and RAW state
- Windows Server 2016 Specific Issues
Post your comment on this topic.