Specifications

Troubleshooting
Symptom Suggested Action
Primary server
cannot bring the
resource ISP when it
reboots after both
servers became
inoperable.
If the primary server becomes operable before the secondary server, you
can force the DataKeeper resource online by opening the resource
properties dialog, clicking the Replication Status tab, clicking the Actions
button, and then selecting Force Mirror Online. Click Continue to
confirm, then Finish.
Error creating a
DataKeeper
hierarchy on
currently mounted
NFS file system
You are attempting to create a DataKeeper hierarchy on a file system that is
currently exported by NFS.You will need to replicate this file system before
you export it.
DataKeeper GUI
wizard does not list
a newly created
partition
The Linux OS may not recognize a newly created partition until the next
reboot of the system. View the /proc/partitions file for an entry of your newly
created partition. If your new partition does not appear in the file, you will
need to reboot your system.
Resources appear
green (ISP) on both
primary and backup
servers.
This is a “split-brain” scenario that can be caused by a temporary
communications failure. After communications are resumed, both systems
assume they are primary.
DataKeeperwill not resync the data because it does not know which
system was the last primary system. Manual intervention is required.
If not using a bitmap:
You must determine which server was the last backup, then take the
resource out of service on that server. DataKeeper will then perform a FULL
resync.
If using a bitmap (2.6.18 and earlier kernel):
You should take both resources out of service, starting with the original
backup node first. You should then dirty the bitmap on the primary node by
executing: $LKROOT/lkadm/subsys/scsi/netraid/bin/bitmap –d
/opt/LifeKeeper/bitmap_filesys
(where /opt/LifeKeeper/bitmap_filesys is the bitmap filename). This will
force a full resync when the resource is brought into service. Next, bring the
resource into service on the primary node and a full resync will begin.
If using a bitmap (2.6.19 and later kernel or with RedHat Enterprise Linux
5.4 kernels 2.6.18-164 or later or a supported derivative of RedHat 5.4 or
later):
You must determine which server was the last backup, then take the
resource out of service on that server. DataKeeper will then perform a partial
resync.
338Troubleshooting