You are here: Configuration Considerations > Using Network Attached Storage

Using Network Attached Storage

There are a couple of special considerations to take into account when configuring LifeKeeper to use an NFS file server (Network Attached Storage) as cluster storage.

Use the NAS Recovery Kit

The optional Network Attached Storage (NAS) recovery kit is required when using an NFS server as a shared storage array with LifeKeeper for Linux.  Install the NAS recovery kit (and a license) on each cluster node.  See the NAS Recovery Kit documentation for more details.

Possible Error Message

When using Network Attached Storage (NAS) with Sybase ASE, you may experience Sybase not restarting following a failover due to a system crash.  The Sybase error log should indicate the cause of the error.

Sybase ASE 12.x

00:00000:00000:2011/05/10 09:54:33.47 kernel  Adaptive Server Enterprise Developer Edition.
00:00000:00000:2011/05/10 09:54:33.47 kernel  basis_dlock: file
'/s10/sybase-data1254/data/master.dat' already in use by a SQL Server
00:00000:00000:2011/05/10 09:54:33.47 kernel  kdconfig: unable to read primary master device
00:00000:00000:2011/05/10 09:54:33.47 server  kiconfig: read of config block failed

Sybase ASE 15.x

00:00:00000:00000:2011/05/09 16:08:51.66 kernel  Adaptive Server Enterprise(Developer Edition)
00:00:00000:00000:2011/05/09 16:08:51.66 kernel  basis_dlock: file '/s10/sybase-data155/data/master.dat' already in use by an ASE
00:00:00000:00000:2011/05/09 16:08:51.66 kernel  kdconfig: unable to read primary master device
00:00:00000:00000:2011/05/09 16:08:51.66 server  kiconfig: read of config block failed
 

This indicates that the Sybase dataserver has set an NFS lock on the file "master.dat" on the NFS file system that is being controlled by LifeKeeper. The lock was not cleared by the system crash, so LifeKeeper is unable to bring the dataserver back into service. Sybase thinks that some other process is using the master.dat file.

Solution

To fix this, mount the NFS file system that will hold master.dat with the "nolock" NFS option before the File System resource is created.  By default, NFS allows file locks to be set.  If the "nolock" option is used before resource creation, LifeKeeper will pick up this option and use it each time it brings the file system resource in service.  Since LifeKeeper will be controlling access (from the cluster nodes) to the file system containing master.dat, the lock is not typically critical. The NFS mount options used during testing were "rw,sync,tcp,nfsvers=3,noac,nolock".

It is not necessary to use the "nolock" on other file systems used by the Sybase resource hierarchy such as the file system where the Sybase ASE binaries are located.

If the NAS File System resource has already been created without the "nolock" option set, use the following procedure to change the mount option:

  1. Using the LifeKeeper GUI, take the file system resource that needs to be changed out of service.  This can be done from the LifeKeeper GUI putting the pointer on the file system resource and doing a right mouse click, and select "Out of Service" from the dropdown menu.  This action may take parent resources out of service as well.

OutofService.jpg

  1. Confirm the "Out of Service" action and allow the process to complete.
  2. Once the file system resource is out of service, you can put the pointer on the resource and do another right mouse click, and from the dropdown menu select "Change Mount Options."

ChangeMountOptions.jpg

  1. In the popup window add "nolock" to the line of options, and click "Set Value."  You will need to repeat steps 3 and 4 for each node in the cluster.

ChangeOptionsPopup.jpg

  1. Bring the NAS File System resource back in service by doing a right mouse click, and selecting "In Service."
  2. The File System resource's property panel should now reflect that "nolock" is one of the current mount options.

nolockPropPanel.jpg

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.