Active/Standby Scenario
Active/Standby Scenario The configuration scenario in this section will describe the file movement
and the symbolic linking that takes place in a LifeKeeper-protected SAMS
environment from the creation of the resource hierarchy, to the extension of
that hierarchy to a backup server, to finally what occurs when the backup
server takes over after a switchover or failover.
Figure 2 Before the SAMS Hierarchy is Created
/var/spool/mqueue
/etc/mail
/etc/md
/var/md/store
Server 2
Shared
Stora
g
e
Server 1
/var/spool/mqueue
/etc/mail
/etc/md
/var/md/store
Configuration Notes:
1. The smiswitchgui and smserver packages are installed on both servers.
2. The same versions of the LifeKeeper Core, IP Recovery Kit and the
SAMS Recovery Kit are installed on both servers. The Core and
LifeKeeper GUI are initialized and made operational.
3. Because the SAMS resource instance requires a dependency on an
existing IP resource instance, a separate IP address must be obtained.
This IP address must be placed under LifeKeeper protection by creating
an IP resource instance on Server 1 and extending it to Server 2.
Note: Refer to the LifeKeeper IP Recovery Kit Administration Guide to
create the IP resource instance.
4. All SAMS configuration files (i.e. sendmail.cf, ms.conf) are configured
with the IP address that was LifeKeeper protected in Step 3. In particular,
keep in mind that you should provide the domain name that corresponds
12 SAMS Recovery Kit Administration Guide