Symptom Possible Cause
Mount point is not included in the selection when creating resources Possible causes are as follows:

  • PowerShell/PowerCLI is not installed
  • An ESXi host is not registered
  • disk.enableUUID parameter is not set
  • The virtual hard disk is on a datastore that is not shared
  • SCSI controller sharing is configured as “virtual” or “physical”


    Error details are recorded in /var/log/lifekeeper.log. Check the log and review the settings.

Stopping LifeKeeper may halt the system. Stopping LifeKeeper without stopping resources (lkstop -f) may halt the entire system. Refer to the following page for more information.
Stopping LifeKeeper halts OS when using VMDK for Shared Storage Recovery Kit Issue:
Stopping LifeKeeper may halt the operating system in LifeKeeper for Linux with VMDK as Shared Storage Recovery Kit configuration.
  • Stopping LifeKeeper during a LifeKeeper upgrade may also cause this issue.

Cause:
When running the command (lkstop -f) which stops LifeKeeper without stopping resources, monitoring processes continue to be done. It is determined as a failure and the system halts.

Solution:
There is a patch available to solve this issue. Contact support at support@us.sios.com or log a case through the support portal at support.us.sios.com to request the patch for this issue.

Workaround:
If you plan to upgrade LifeKeeper in the environment with VMDK resources, please contact SIOS Customer Support.

If the patch has not been applied, please follow the steps below when stopping LifeKeeper in an environment with VMDK resources.

This issue will not occur if there are no existing VMDK resources.
  • If you can stop VMDK resources.
    Stop all VMDK resources.
    # /opt/LifeKeeper/bin/perform_action -t <VMDK resource tag name> -a remove
    Stop LifeKeeper with lkstop command after verifying that the VMDK resources are stopped.
    # /opt/LifeKeeper/bin/lkstop

  • If you cannot stop VMDK resources.
    If the VMDK resources are In Service, switch those resources to the backup server.
    (Perform this on the backup server.)
    # /opt/LifeKeeper/bin/perform_action -t <VMDK resource tag name> -a restore
    Stop LifeKeeper of the previous active server.
    # lkstop

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