Filter
Top Products
Configuring SAMS with LifeKeeper
DNS, Sendmail and LifeKeeper
DNS offers a mechanism (MX Records) for specifying backup or alternate
hosts for mail delivery. This mechanism also allows hosts to assume
mail-handling responsibilities for other hosts that are not configured to
accept mail, such as a null client. MX records also provide a mechanism of
forcing all mail to go to the hub machine or mail server. MX records specify
a mail exchanger for a domain name (i.e. a host that will process and/or
forward mail for the specified hostname). As an example, this is done by
adding entries into the DNS server as follows:
himalaya.sc.steeleye.com IN MX 10 relay.steeleye.com.
In the example, the server himalaya.sc.steeleye.com has an MX record that
will cause mail for this server to be delivered to relay.steeleye.com. The
server which is to be LifeKeeper protected should not have any MX records.
The LifeKeeper-protected switchable IP address that is used during the
SAMS resource hierarchy creation should be used for MX records instead.
Configuration Requirements
To understand the configuration scenario in the next section, keep these
configuration requirements in mind:
• LifeKeeper hierarchy administration. When performing LifeKeeper
administration, the primary server refers to the location that the SAMS
instance is currently running. System administration takes place on this
server when creating a LifeKeeper hierarchy.
• Shared disk resource. When you use LifeKeeper, shared storage
resources that are under LifeKeeper protection are reserved for use by
one server. This prevents inadvertent corruption of the data by other
servers in the cluster. When a server fails, the highest priority backup
server establishes ownership of the disk resources and locks out all other
servers.
LifeKeeper for Linux 11