Specifications

Bringing a DataKeeper Resource In Service
breaks the mirror, unmounts the file system (if applicable), stops the md device and kills the nbd
server and client.
WARNING: Do not take your DataKeeper resource out of service unless you wish to stop mirroring
your data and remove LifeKeeper protection. Use the Pause operation to temporarily stop mirroring.
1. In the right pane of the LifeKeeper GUI, right-click on the DataKeeper resource that is in
service.
2. Click Out of Service from the resource popup menu.
3. A dialog box confirms the selected resource to be taken out of service. Any resource
dependencies associated with the action are noted in the dialog. Click Next.
4. An information box appears showing the results of the resource being taken out of service.
Click Done.
Bringing a DataKeeper Resource In Service
Bringing a DataKeeper resource in service is similar to creating the resource: LifeKeeper starts the
nbd server and client, starts the md device which synchronizes the data between the source and
target devices, and mounts the file system (if applicable).
1. Right-click on the DataKeeper resource instance from the right pane.
2. Click In Service from the popup menu. A dialog box appears confirming the server and
resource that you have selected to bring into service. Click In Service to bring the resource
into service.
3. An information box shows the results of the resource being brought into service. Any resource
dependencies associated with the action are noted in the confirmation dialog. Click Done.
Testing Your Resource Hierarchy
You can test your DataKeeper resource hierarchy by initiating a manual switchover. This will
simulate a failover of the resource instance from the primary server to the backup server.
Performing a Manual Switchover from the LifeKeeper GUI
You can initiate a manual switchover from the LifeKeeper GUI by selecting Edit, Resource, and
InService. For example, an in-service request executed on a backup server causes the DataKeeper
resource hierarchy to be taken out-of-service on the primary server and placed in-service on the
backup server. At this point, the original backup server is now the primary server and original primary
server has now become the backup server.
After the switchover, the state of the DataKeeper resource on the target server is set to “Resyncing”
in the LifeKeeper GUI. Once the resynchronization is complete the state will change to “Target”,
which is the normal Standby condition.
Note: Manual failover is prevented for DataKeeper resources during resynchronization.
290Installation and Configuration