Filter
Top Products
Active/Standby Scenario
The gray arrows represent dangling links (i.e. the files on Server 2 are
linked to the shared storage device, but the shared device is not
mounted on Server 2. Therefore, the links on Server 2 are not active).
Configuration Notes
During the extension of the SAMS resource instance to the backup server
(i.e. Server 2), the Recovery Kit symbolically links the SAMS configuration
and data directories /etc/md, /etc/mail, and /var/md/store to the versions on
the shared file system. Note: The existing directories on Server 2 are saved
with a .LK extension.
IMPORTANT: If your specific SAMS configuration requires any other files
to be LifeKeeper-protected, these files must be manually moved to the shared
file system and linked back to their original locations on each server after the
extension of the SAMS resource hierarchy.
Figure 5 Switchover/Failover of the SAMS Hierarchy from
Server 1 to Server 2
Server 1
Shared
Storage
Server 2
etc/mail
etc/md
var/md/store
mqueue
/
etc/mail
/etc/md
/var/md/store
/var/spool/mqueue* /var/spool/mqueue*
/etc/mail
/etc/md
/var/md/store
* The symbolic link /var/spool/mqueue/ must be created manually.
The gray files and directories are symbolically linked to files on the
shared storage device.
The black arrows represent active symbolic links (i.e. the files on Server
2 are actively linked to the shared storage device after the resource is
switched or failed over).
LifeKeeper for Linux 15