In order to safely create a shared-storage volume resource, the user must ensure that only one system at a time has write access to the volume at any time. This includes the time prior to the creation of the LifeKeeper for Windows instance.

Since LifeKeeper for Windows cannot recognize that the volume is shared before an instance is created, manual steps must be taken to ensure that the volume is never writable on two or more systems at the same time.

To protect the volume from simultaneous write access, use the following procedure. In this example, two systems – SYSA and SYSB – are connected to shared storage. This storage is configured with two volumes which should be assigned drive letters E and F on both systems, then protected with LifeKeeper for Windows volume instances.

  1. Power on SYSA, while leaving SYSB powered off.
  1. Install LifeKeeper if it has not been installed.
  1. Assign drive letters E and F to the volumes; format with NTFS if not formatted yet.
  1. Power off SYSA.
  1. Power on SYSB.
  1. Install LifeKeeper if it has not been installed.
  1. Assign drive letters E: and F: to the shared volumes.
  1. In a command prompt, run the following commands:

%LKBIN%\volume -p E

%LKBIN%\volume -p F

  1. Reboot SYSB. It will come up with the E: and F: drives locked.
  1. Power on SYSA. It will come up with the E: and F: drives writable.
  1. Create volume resources for E: and F: on SYSA and extend to SYSB.

An alternative to powering the systems off is to use Disk Management to take the shared physical disk offline.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment