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:
-
A SteelEye DataKeeper resource and its parent resources cannot fail over to a target that was in the synchronization process when the primary failed.
-
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.
- 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.