When you want to protect resources on shared SCSI disks, you partition the shared disk into logical volumes using the Windows Disk Management tool. LifeKeeper for Windows can protect shared volumes by defining a volume resource instance. Each instance is assigned a drive letter (for example, G:).

LifeKeeper for Windows brings the volume resource instance into service on the primary server and provides software locks so that a backup server cannot access the volume while it is active on the primary server. In case of a failure of the primary server, LifeKeeper for Windows automatically brings the volume resource into service on the backup server and locks the primary server from accessing the volume resource when it is repaired.

LifeKeeper for Windows also automatically changes the primary and designations so that the failed server is now locked from access to the volume resource. In this way, the resource is protected from inappropriate access while you repair the failed server.

This dynamic redefinition of primary and backup servers is LifeKeeper for Windows’ intelligent switchback feature that allows you to select the appropriate time to bring the resource back into service on the repaired system.

Since LifeKeeper for Windows maintains the volume locks, do not stop LifeKeeper for Windows, as this would disable the locks.


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