In versions of LifeKeeper for Windows v8.10.0 or earlier, if a parent resource (a resource higher in the resource hierarchy) is stopped, lower resources (child resources) are not monitored, even if they are in service (ISP), and no local recovery or failover will be performed if a problem occurs in the lower resources.
In the example above, MSExch.0 is a parent resource. If this resource is stopped, all lower resources (DNS.0, Vol.L and Vol.X), are not monitored.
The dependency relationships specified by the resource hierarchy tell LifeKeeper for Windows the appropriate order for bringing resource instances in service and out-of-service. In the example resource hierarchy, LifeKeeper for Windows cannot bring the MSExch.0 resource into service until it successfully brings into service the DNS and volume instances.
Resources belonging to the same resource hierarchy can only be brought in service (ISP) on the same server. If a problem occurs with one of the resources and it fails over to another server, the resources belonging to the same resource hierarchy will move together.
With the default setting, if a resource higher in the resource hierarchy (parent resource) is stopped, lower resources (child resources) are not monitored, even if they are in service (ISP), and no local recovery or failover will be performed if a problem occurs. This is the same behavior as with LifeKeeper for Windows v8.10.0 or earlier.
This behavior can be changed in later versions of LifeKeeper for Windows v8.10.1 and newer. If you want to change the behavior, set the variable MONITOR_CHILD_WHEN_PARENT_IS_OSU to 1 in the %LKROOT%\etc\default\LifeKeeper file and restart the LifeKeeper service. When the MONITOR_CHILD_WHEN_PARENT_IS_OSU variable is set, even if a higher resource in the resource hierarchy is stopped, lower resources in the hierarchy that are in-service (ISP), will be subject to monitoring and local recovery. and a failover will be performed if an error is detected.
In the example above, MSExch.0 is a parent resource. When the MONITOR_CHILD_WHEN_PARENT_IS_OSU is set to 1, and the MSExch.0 resource is stopped, all lower resources (DNS.0, Vol.L and Vol.X), will be subject to monitoring and local recovery. and a failover will be performed if an error is detected.
Post your comment on this topic.