Most Common DKCE Clustering Solutions

The following are the most commonly requested clustering related solutions.

Perform a Health Check

How do I add/register an existing DataKeeper Volume to a cluster?

Why has my Role FAILED in WSFC (e.g. SQL, SAP, FileShare, Hyper-V, Generic App)?

• For licensing and rehosting information refer to Licensing

Example of a Basic WFSC Dependency Relationship of Hyper-V and DataKeeper

Hyper-V

Dependency Report for the following:

• 1×1
• Windows Server 2012
• DataKeeper x.x.x
• Hyper-V

Bentgrass2012 DataKeeper Volume K has no required dependencies
Virtual Machine Bentgrass2012 dependencies are Virtual Machine Configuration Bentgrass2012
Virtual Machine Bentgrass2012 required dependencies are Virtual Machine Configuration
Virtual Machine Configuration Bentgrass2012 dependencies are Bentgrass2012 DataKeeper Volume K
Virtual Machine Configuration Bentgrass2012 has no required dependencies

SQL

Dependency Report for the following:

• 1×1
• Windows Sever 2012
• DataKeeper x.x.x
• SQL Server 2008 or higher

DataKeeper Volume E has no required dependencies
IP Address: 172.17.100.57 has no required dependencies
Name: SIOSSQL dependencies are IP Address: 172.17.100.57
SQL Network Name (SIOSSQL) required dependencies are IP Address
SQL Server dependencies are Name: SIOSSQL
SQL Server has no required dependencies
SQL Server Agent dependencies are SQL Server
SQL Server Agent has no required dependencies

File Share

Dependency Report for the following:

• 1×1
• Windows Server 2016
• DataKeeper x.x.x
• File Share

DataKeeper Volume F has no required dependencies
File Server (\\QATESTFS) dependencies are DataKeeper Volume F and Name: QATESTFS
File Server (\\QATESTFS) has no required dependencies
IP Address: 172.17.100.225 has no required dependencies
Name: QATESTFS dependencies are IP Address: 172.17.100.225
QATESTFS required dependencies are IP Address

How to recreate a mirror for an existing clustered DataKeeper Resource

Issue:

A customer may have experienced some issues where a DataKeeper Resource is listed as Offline via Windows Server Failover Cluster.

*Note: An existing job in the DataKeeper GUI will most likely have a RED X status.

Solution:

• Remove all of the old mirror remnants from the Source and Target nodes
• Manually recreate the mirror via the emcmd . createmirror command

To remove the mirror configuration from both nodes:

• cd %extmirrbase%/support (This is a shortcut to the DataKeeper\Support directory)
• run “cleanupmirror (drive letter)”

*Note: Run this command on the Source first. This command performs the following:
• deletes the local mirror only (NO DATA)
• resets the switchover flag
• notifies the driver and service that no mirror is present

To verify that the mirror has been properly removed, execute the following:

• cd extmirrbase (This is a shortcut to the DataKeeper directory)
• run “emcmd . getmirrorvolinfo (drive letter)”
  The output should reflect no mirror e.g. 0 servername 0

Now you are in a position to manually recreate the mirror.

The syntax is as follows:

• emcmd (Source IP) createmirror (drive letter) (Target IP) A or S (Async mirror/Sync Mirror)
  

Upon completion, the DataKeeper UI will now reflect a Resyncing status. This can also can be verified from a command line by executing:

• emcmd . getmirrorvolinfo e
  The output will reflect “E: 1 servername (Target IP) 2, where 2 is a mirror definition, indicating a Resyncing status
  

Return to Windows Failover Clustering and online the Failed DataKeeper Resource.