Specifications

Scenario 2

Considering scenario 1, Server 2 (still the primary server) becomes inoperable during the

resynchronization with Server 1 (now the backup server).

Result: Because the resynchronization process did not complete successfully, there is potential for

data corruption. As a result, LifeKeeper will not attempt to fail over the DataKeeper resource to

Server 1. Only when Server 2 becomes operable will LifeKeeper attempt to bring the DataKeeper

resource in-service (ISP) on Server 2.

Scenario 3

Both Server 1 (primary) and Server 2 (target) become inoperable. Server 1 (primary) comes back up

first.

Result: Server 1 will not bring the DataKeeper resource in-service. The reason is that if a source

server goes down, and then it cannot communicate with the target after it comes back online, it sets

the following flag:

$LKROOT/subsys/scsi/resources/netraid/$TAG_data_corrupt

This is a safeguard to avoid resynchronizing data in the wrong direction. In this case you will need to

force the mirror online on Server1, which will delete the data_corrupt flag and bring the resource into

service on Server 1. See Force Mirror Online.

Note: The user must be certain that Server 1 was the last primary before removing the $TAG_data_

corrupt file. Otherwise data corruption might occur. You can verify this by checking for the presence

of the last_owner flag.

Scenario 4

Both Server 1 (primary) and Server 2 (target) become inoperable. Server 2 (target) comes back up

first.

262Introduction