Specifications

Server Failure
Server Failure
If both your primary and backup servers become inoperable, your DataKeeper resource will be
brought into service/activated only when both servers are functional again. This is to avoid data
corruption that could result from initiating the resynchronization in the wrong direction. If you are
certain that the only operable server was the last server on which the resource was “In Service
Protected” (ISP), then you can force it online by right-clicking the DataKeeper resource and then
selecting Force Mirror Online.
Resynchronization
During the resynchronization of a DataKeeper resource, the state of this resource instance on the
target server is “Resyncing”. However, the resource instance is “Source” (ISP) on the primary
server. The LifeKeeper GUI reflects this status by representing the DataKeeper resource on the
target server with the following icon:
and the DataKeeper resource on the primary server with this icon:
As soon as the resynchronization is complete, the resource state on the target becomes “Target” and
the icon changes to the following:
The following points should be noted about the resynchronization process:
l A SteelEye DataKeeper resource and its parent resources cannot fail over to a target that was
in the synchronization process when the primary failed.
l If your DataKeeper resource is taken out of service/deactivated during the synchronization of
a target server, that resource can only be brought back into service/activated on the same
system or on another target that is already in sync (if multiple targets exist), and the
resynchronization will continue.
l If your primary server becomes inoperable during the synchronization process, any target
server that is in the synchronization process will not be able to bring your DataKeeper resource
into service. Once your primary server becomes functional again, a resynchronization of the
mirror will continue.
SteelEye Protection Suite for Linux303