Most Common DKCE Networking Solutions

The following are the most commonly requested networking related solutions.

SIOS DataKeeper Service Will Not Start

DataKeeper Service Stopped Unexpectedly

Issues/Symptoms:

The DataKeeper Service periodically stops. The System Event Viewer will produce the following:

Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date:
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
User: SYSTEM
Computer:
Description:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: disp+work.exe (12276) consumed 4458348544 bytes, disp+work.exe (10580) consumed 3786977280 bytes, and disp+work.exe (6068) consumed 1657556992 bytes.

Solution:

ExtMirrSvc logs that it stopped because it couldn’t spawn a GUI thread. This is probably due to all the memory being used up by disp+work.exe processes.

Errors from “extmirrsvc” service when establishing mirror

Issue:

When trying to configure SIOS DataKeeper Cluster Edition, it is not able to identify the server name or IP addresses even though the servers are reachable via PING, NetBIOS and Telnet.

Solution:

Ensure that the account used to start the SIOS DataKeeper Service is a member of the local Administrators Group on both nodes.

Also if you’re using a Host file for name resolution, ensure the hostname and ipaddress for both nodes are populated in the hostfile. Once added, restart the SIOS DataKeeper Service via the Services Applet.

Server Overview in DataKeeper Not Showing Servers

DataKeeper Server Overview Showing Remote System (not remote drives)

Issue:

DataKeeper Server Overview showing remote system, but not remote drives

Solution:

Ensure that if you’re using a hostfile, the following must be present on both nodes:

The Full Qualified Domain Name/FQDN is being used

All host entries are identical on both nodes

Volume Missing in Server Overview when Attempting to Create a Mirror

Issue:

When attempting to create a mirror via the DataKeeper GUI you may notice the following:

Target Volume is present in Server Overview but after attempting to create, the Volume disappears

When attempting to manually create the mirror using EMCmd <system> CREATEMIRROR <volume letter> <target system> <Type>. You may receive an error message “Status = 317”

Solution:

It was determined that the Target volume disk was smaller than the Source.

Rules for mirror creation are as follows:

Source & Target must be equal in size or Target must be larger than the Source

This can be verified by viewing the Total Capacity of the volume (select Properties) via Disk Management or by using the following emcmd command:

EMCmd <system> GETVOLUMEINFO <volume letter> <level>, This output, Total Space in particular, needs to meet the criteria for mirror creation. Once resolved by increasing/shrinking the volumes, you should be able to successfully create a mirror.