Contact Us

U.S: (+1) 888-876-8666

UK: +44 (0) 203-318-5364

Customize Failover Scripts


1 comment

  • Avatar
    Harold Stubbs

    Using Integrated Storage you already can not start a VM somewhere if the downed HV still sees storage, since the storage controllers are managing things and prevent activating in 2 places already.

    For LVM datastore - perhaps taking ~1GB and formatting as some cluster-aware filesystem the HVs could create locks on the VG itself for the VM disks that it has activated as a primary check / using the LVM datastore itself to pass messages? or extending storageAPI so that LVM acts like IS - trying to activate LVM disk requires checking against all the other HVs using management, storage, and backup networks as configured, and only proceeding when the other HVs fail to reply or reply the VM disk isn't active there.

    Comment actions Permalink

Please sign in to leave a comment.