Справочник Пользователя для SteelEye LifeKeeper for Linux 4.5.0
LifeKeeper Configuration Tasks
Important: The user must be careful when deleting the SAMS resource
hierarchy. The SAMS Recovery Kit keeps the backup server’s copy of
the configuration and data directories on the backup server itself. These
directories are moved to /etc and renamed with the extension .LK. When
the hierarchy is deleted, these .LK directories are renamed to their
original names on the backup server. On the primary server, the
configuration and data directories are copied from the shared file system
to their original locations and the SAMS daemons are left running.
hierarchy. The SAMS Recovery Kit keeps the backup server’s copy of
the configuration and data directories on the backup server itself. These
directories are moved to /etc and renamed with the extension .LK. When
the hierarchy is deleted, these .LK directories are renamed to their
original names on the backup server. On the primary server, the
configuration and data directories are copied from the shared file system
to their original locations and the SAMS daemons are left running.
6. Click
the
Done button to exit out of the Delete Resource Hierarchy menu
selection.
Extending Your Hierarchy
After you have created a hierarchy, you will want to extend that hierarchy to
another server in the cluster. There are three possible scenarios to extend
your resource instance from the template server to a target server. The first
scenario is when you “Continue” from creating the resource into extending
that resource to another server. The second scenario is when you enter the
Extend Resource Hierarchy task from the edit menu as shown below. The
third scenario is when you right click on an unextended hierarchy in either
the left or right hand pane. Each scenario takes you through the same dialog
boxes (with a few exceptions, which are clearly detailed below).
another server in the cluster. There are three possible scenarios to extend
your resource instance from the template server to a target server. The first
scenario is when you “Continue” from creating the resource into extending
that resource to another server. The second scenario is when you enter the
Extend Resource Hierarchy task from the edit menu as shown below. The
third scenario is when you right click on an unextended hierarchy in either
the left or right hand pane. Each scenario takes you through the same dialog
boxes (with a few exceptions, which are clearly detailed below).
1. If you are entering the Extend wizard from the LifeKeeper GUI menu,
select Edit, then Resource. From the drop down menu, select Extend
Resource Hierarchy. This will launch the Extend Resource Hierarchy
wizard.
Resource Hierarchy. This will launch the Extend Resource Hierarchy
wizard.
2. The first dialog box to appear will ask you to select the Template Server
where your SAMS resource hierarchy is currently in service. It is
important to remember that the Template Server you select now and the
Tag to Extend that you select in the next dialog box represent an in
service resource hierarchy. An error message will appear if you select a
resource tag that is not in service on the template server you selected.
The drop down box in this dialog provides the names of all the servers in
your cluster.
important to remember that the Template Server you select now and the
Tag to Extend that you select in the next dialog box represent an in
service resource hierarchy. An error message will appear if you select a
resource tag that is not in service on the template server you selected.
The drop down box in this dialog provides the names of all the servers in
your cluster.
Note: If you are entering the Extend Resource Hierarchy task
immediately following the creation of a SAMS resource hierarchy, this
immediately following the creation of a SAMS resource hierarchy, this
LifeKeeper for Linux
25