How to Configure DiskShare in a Windows Cluster Environment

DiskShare is a Windows-based NFS Server that allows you to share PC directories to UNIX, Linux or any other NFS client. DiskShare supports Windows NT, 2000, and Windows XP. Note, Windows is referred to throughout this document; however, it is a generic term for the DiskShare supported operating systems mentioned.

This document will provide instructions to configure DiskShare for file sharing in a Windows Cluster Environment. It is written from a support analyst’s point of view and deals primarily with the necessary steps to get DiskShare configured for this type of workflow.

Additional Support Documents are located in the DiskShare\Support subdirectory. For detailed information regarding DiskShare configuration see the DiskShare HELP and the Frequently Asked Questions (FAQ) document.

Definition:

A server cluster is a group of independent servers managed as a single system, resulting in higher availability. The Windows Cluster Service can automatically detect the failure of an application or server, and restart the application, either on the same server if it is still alive, or on another surviving server.

NOTES

DiskShare can only be configured in a cluster environment when running Windows NT 4.0 and Windows 2000 only.

DiskShare only supports cluster environments, in which, all servers in the cluster share the data from a ‘common disk’.

Below is an example of setting up DiskShare in a cluster environment. In this example, everything that shall be shared using DiskShare is located on Drive E.

Environment:

A two node cluster running Windows NT Server Enterprise Edition Version 4.0, with SP4 + Hot Fix for "Combo Share", or Windows 2000 Advanced Server.

NOTE

If there are additional disks that are shared via NFS, they must belong to the same cluster group.

Procedure:

1. Install DiskShare on both nodes with a “Typical” installation and reboot.

2. On Windows NT 4.0: Set startup for the DiskShr Service to “Manual” (located at Control Panel - Devices) and Stop the device. This must be done for both nodes.

On Windows 2000: Set the startup for the DsSvc to manual (located at Control Panel – Administrative Tools – Services) and stop the service. Also set the DiskShr device driver to “Demand” (located at Control Panel – Computer Management – System Tools – Device Manager.) Click View then click Show Hidden Devices. Now click Non-Plug and Play Drivers – DiskShr – Properties – Driver tab and Stop the device. This must be done for both nodes.

3. Create a new resource with Window’s Cluster Administrator, using the following information.

Specify the type to be GENERIC Service.
Specify the name of the resource(s) to be,
On Windows NT 4.0: diskshr
When prompted, include the following DiskShare registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DiskShr
HKEY_LOCAL_MACHINE\SOFTWARE\SSC\DiskShare
On Windows 2000: Setup the Generic Services listed below. Note these resources must be created in the following order.

Resource Name	Resource Dependencies	Advanced Settings	Advanced Parameters
dssvc	none	Do not restart	dssvc
rpcxdr	dssvc		rpcxdr
portmap	rpcxdr		portmap
diskshr	portmap		diskshr
NOTE To include PCNFSD functionality, add these two services in the defined order.
kepcnfsd	diskshr		kepcnfsd (default)
pcnfsd	kePcnfsd		pcnfsd (default)

4. On Windows NT 4.0: Use the Cluster Administrator to make the diskshr service on-line.

On Windows 2000: Use the Cluster Administrator to make the diskshr service on-line. Right-click the resource name and click Bring Online.

NOTE

If you are running PCNFSD then bring the "pcnfsd" service defined above 'online' instead of the 'diskshr' service.

Share something on every disk that is going to be shared and mount it from the NFS client and dismount.
Create the folder E:\Diskshare on the node where the service is online.
Edit the following Registry Keys from HKEY_LOCAL_MACHINE on Local Machine, such that, they include the new path, E:\Diskshare. The Registry Keys to be modified are:
SYSTEM\CurrentControlSet\Services\DiskShr\Parameters\SymLinkFile to E:\DiskShare\symlinks.nfs
SYSTEM\CurrentControlSet\Services\DiskShr\Parameters\E\IndexFile to E:\DiskShare\Drivee.ndx
SYSTEM\CurrentControlSet\Services\DiskShr\Parameters\E\InodeFile to E:\DiskShare\Drivee.nod
SOFTWARE\SSC\DiskShare\CurrentVersion\Locking\LockBaseDir to E:\DiskShare
SOFTWARE \SSC\DiskShare\CurrentVersion\Mapping\PasswdFile to E:\DiskShare\passwd
SOFTWARE\SSC\DiskShare\CurrentVersion\Mapping\UnixGroupFile to E:\DiskShare\group
SOFTWARE\SSC\DiskShare\CurrentVersion\RmtabFile\RmtabFile to E:\DiskShare\rmtab

The Registry Keys for the INODE (.NOD) and INDEX (.NDX) must be modified for each drive you have exported. The example in this document only provides information for Drive E.

NOTES

DiskShare can be configured as in any typical workflow, however; DiskShare can ONLY be configured on the node where the service is currently on-line.

In addition, if your NFS client does not handle “stale file handles” correctly, the client may need to dismount and remount. This is an NFS client-related issue and not DiskShare.

The modifications provided in this document must be done in order for DiskShare to fail over successfully in a Windows cluster environment.