Specifications
When to Select This Setting
time in seconds that LifeKeeper should wait before taking the default action (setting this to zero
means “don’t wait before taking default action”).
If the administrator does not run the lk_confirmso command within the time allowed, the failover
will either proceed or be blocked. By default, the failover will proceed. This behavior can be changed
by modifying the CONFIRMSODEF setting in /etc/default/LifeKeeper. CONFIRMSODEF
specifies the action to be taken. If set to "0", the action is to proceed with failover. If set to "1", the
action is to block failover.
Note: Using the Command Line, this option is configured by setting the confirmso!uname flag on
the system which will be performing the failover recovery, where uname refers to the name of the
remote system which has failed. See theLCDI-flag(1M) manual page.
When to Select This Setting
This setting is used in most Disaster Recovery, XenServer and other WAN configurations where the
configuration does not include redundant heartbeat communication paths.
l In a regular site (non-multi-site cluster and non-XenServer), open the Properties page from
one server and then select the server that you want the Confirm Failover flag to be set on.
l For a Multi-site WAN configuration: Enable manual failover confirmation.
l For a Multi-site LAN configuration:Do not enable manual failover confirmation.
l In a multi-site cluster environment – from the non-disaster system, select the DR system and
check the set confirm failover flag. You will need to open the Properties panel and select this
setting for each non-disaster server in the cluster.
l In a XenServer environment, all servers in the list (not just the DR site) need to be checked.
Block Resource Failover On
The Block Resource Failover On setting blocks all resource transfers due to a resource failure from
the given system.
By default, all resource failures will result in a recover event that will attempt to recover the failed
resource on the local system. If local recovery fails or is not enabled, then LifeKeeper transfers the
resource hierarchy to the next highest priority system for which the resource is defined. However, if
this setting is selected on a designated system(s), all resource transfers due to a resource failure will
be blocked from the given system.
When the setting is enabled, the following message is logged:
Local recovery failure, failover blocked, MANUAL INTERVENTION
REQUIRED
Conditions/Considerations
l In a multi-site configuration, do not select Block Failover for any server in the configuration.
l In a XenServer environment, select Block Failover for each system in the cluster.
Remember: This setting will not affect failover behavior if there is a complete system
SteelEye Protection Suite for Linux279