Instruction/ maintenance manual of the product 4.5.0 SteelEye
Go to page of 43
LifeKeeper ® for Linux v4.5.0 Sendmail Advanced Message Server (SAMS) Recovery Kit Administration Guide Revision B 07/2004.
The product described in this book is a licensed product of SteelEye ® Technology, Inc. SteelEye, SteelEye Technology, and LifeKeeper are registered trademarks of SteelEye Technology, Inc. Linux is a registered trademark of Linus Torvalds. Sendmail is a trademark of Sendmail, Inc.
Table of Contents Introduction ................................................................................................................................3 Document Contents ........................................................................
.
SAMS Recovery Kit Administration Guide Introduction The Sendmail Advanced Message Server (SAMS) is a suite of comm ercial messaging applications. These applications provide various services to clients, such as POP and IMAP, as well as storing and transferring e-mail messages.
Introduction • LifeKeeper Configuration Tasks. A description of the tasks for creating and managing your SAMS resource hierarchies using the LifeKeeper GUI. • Troubleshooting . This section provides a list of informational and error messages with recomm ended solutions.
Requirements Reference Documents The following is a list of reference documents associated with the SAMS product and the LifeKeeper SAMS Recovery Kit: • S endmail Advanced Message Server Reference G.
Requirements • Servers. The Recovery Kit requires two or more supported computers configured in accordance with LifeK eeper requirements described in the LifeKeeper Release Notes , which are shipped with the LifeKeeper product media. • LifeKeeper software.
Configuring SAMS with LifeKeeper Configuring SAMS with LifeKeeper This section contains information you should consider before you start to configure SAMS and examples of typical LifeKeeper SAMS configurations. Please refer to your LifeKeeper Online Product Manual for instructions on configuring your LifeKeeper Core resource hierarchies.
Configuring SAMS with LifeKeeper Figure 1 illustrates how SAMS works in a LifeKeeper environment. An active/standby configuration means that only one instance of SAMS can run at one time within the LifeKeeper-protected pair.
Configuring SAMS with LifeKeeper server may fail when a switchover to the backup server occurs. Note that the SAMS Recovery Kit does not require the switchable IP address to have an MX record on the DNS server.
Configuring SAMS with LifeKeeper Sendmail Configuration File The following are a few more important points to note in the Sendmail configuration file ( /etc/mail/sendmail.cf ). Masquerading Masquerading is used to translate an email address with a given hostname into the address of the domain or that of another mailhub/m ailserver.
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 assum e mail-handling responsibilities for other hosts that are not configured to accept mail, such as a null client.
Active/Standby Scenario Active/Standby Scenario The configuration scenario in this section will describe the file movement and the symbolic linking that takes pl ace in a LifeKeeper-protected SAMS env.
Active/Standby Scenario to the switchable IP address when asked for the “Host Name” in the Sendmail Switch installer program. 5. SAMS is tested to ensure that it will work properly on both servers using equivalent configurati on options on both servers.
Active/Standby Scenario The black arrows represent active symbolic links (i.e. the files on Server 1 are actively linked to the shared storage device after the resource is created). Configuration Notes During the creation of the SAMS resource instance on the primary server (i.
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, t he links on Server 2 are not active). Configuration Notes During the extension of the SAMS resource instance to the backup server (i.
Active/Standby Scenario The gray arrows represent dangling links (i.e. the files on Server 1 are linked to the shared storage device, but the shared device is not mounted on Server 1. Therefore, t he links on Server 1 are not active). Configuration Notes When Server 2 becomes the active or primary server, the following occurs: 1.
LifeKeeper Configuration Tasks LifeKeeper Configuration Tasks You can perform the following configuration tasks from the LifeKeeper GUI. The following four tasks are described in this guide, as they are unique to a SAMS resource instance, and different for each Recovery Kit.
LifeKeeper Configuration Tasks same drop down menu choices as the Edit m enu. This, of course, is only an option when a hierarchy already exists. You can also right click on a resource instance in the.
LifeKeeper Configuration Tasks To create a resource instance from the primary server, you should complete the following steps: 1. From the LifeKeeper GUI menu, select Edit , then Resource .
LifeKeeper Configuration Tasks 2. Select the Switchback Type. This dictates how the SAMS instance will be switched back to this server when it comes back into service after a failover to the backup server. You can choose either intelligent or automatic .
LifeKeeper Configuration Tasks 5. Select the IP Tag. This is a tag name given to the IP Resource hierarchy that the SAMS resource will be de pendent upon.
LifeKeeper Configuration Tasks Creating mail/sams resource… BEGIN creation of resource “sams” on server “smokey” at Fri Oct 12 10:31:34 EDT 2001 Creating Resource instance “sams with id “sams” on server “smokey” devicehier: Using /opt/LifeKeeper/lkadm/subsys/scsi/dev ice/bin/devicehier to construct the hierarchy .
LifeKeeper Configuration Tasks 10. Click the Done button to exit the Create Resource Hierarchy menu selection. Deleting a Resource Hierarchy To delete a resource hierarchy from all the servers in your LifeKeeper environment, complete the following steps: 1.
LifeKeeper Configuration Tasks sams Click on the Next button to proceed to the next dialog box. 4. An information box appears confirming your selection of the target server and the hierarchy you have selected to delete. sams Click on the Delete button to proceed to the next dialog box.
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 .
LifeKeeper Configuration Tasks dialog box will not appear , since the wizard has already identified the template server in the create stage. This is also the case when you right- click on either the S.
LifeKeeper Configuration Tasks Click on the Next button to proceed to the next dialog box. 5. Select the Switchback Type. This dictates how the SAMS instance will be switched back to this server when it comes back into service after a failover to the backup server.
LifeKeeper Configuration Tasks 7. An information box will appear explaining that LifeKeeper has successfully checked your environment and that all the requirements for extending this SAMS resource have been met.
LifeKeeper Configuration Tasks appear if you are extending this SAMS resource immediately following its creation. Click on the Next button. 10. This dialog box is for information purposes only.
LifeKeeper Configuration Tasks Click on the Next button to proceed to the next dialog box. 13. Select or enter the IP Resource Tag . Click on the Next button.
LifeKeeper Configuration Tasks 15. Click the Done button in the last dialog box to exit from the Extend Resource Hierarchy menu selection. Note: Be sure to test the functionality of the new instance on both servers. Unextending Your Hierarchy 1. From the LifeKeeper GUI menu, select Edit , then Resource .
LifeKeeper Configuration Tasks 4. An information box appears confirming the target server and the SAMS resource hierarchy you have chosen to unextend. sams Click the Unextend button. 5. Another information box appears confirming that the SAMS resource was unextended successfully.
LifeKeeper Configuration Tasks Performing a Manual Switchover from the GUI You can initiate a manual switchover from the LifeKeeper GUI by selecting Edit , then Resource , then finally In Service from the drop down menu.
Troubleshooting Troubleshooting This section provides a list of messages that you may encounter during the process of creating, extending, removing and restoring a LifeKeeper SAMS hierarchy, and, where appropriate, pr ovides additional explanation of the cause of the errors and necessary action to resolve the error condition.
Troubleshooting ERROR: Must specify Sendmail configuration file name The name of the Sendmail configuration file m ust be specified. Enter the correct name for the configuration file ( /etc/mail/sendmail.cf ). Unknown error in script mailhier, err=$ERR An unknown error has occurred in the script.
Troubleshooting ERROR: Message store directory setting invalid or not found in mail store configuration file “$MS_CONF” The ms-path variable is missing or contains an incorrect value in the /etc/md/store/ms.
Troubleshooting ERROR: Failed to create LifeKeeper Application “mail” on server “$SERVER” LifeKeeper was unable to create the LifeKeeper application type “mail” on the specified server. See the LifeKeeper error log for additional troubleshooting information.
Troubleshooting Error - canextend () - The “$DIR” directory does not exist on server “$TARGET_SYSTEM” The specified SAMS directory does not exist on the target system. Create the directory on the target system and attempt to extend the SAMS resource hierarchy again.
Troubleshooting Error - extend () - LifeKeeper Internal ID ($ID) is already being used by another resource type on “$SERVER” LifeKeeper uses an Internal Resource Identifier that must be unique for all servers in a cluster. There is al ready a resource that has the same ID as SAMS.
Troubleshooting restore: sams: ERROR: sendmail configuration file “$FILE” is em pty The Sendmail configuration is empty or does not exist. restore: sams: SAMS is already running on $IP:$PORTLIST This message is for informational purposes only.
Troubleshooting LifeKeeper was unable to stop the SAMS processes. The actual error messages from subprocesses are displayed within this message. See the LifeKeeper error log for additional troubleshooting information.
An important point after buying a device SteelEye 4.5.0 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought SteelEye 4.5.0 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data SteelEye 4.5.0 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, SteelEye 4.5.0 you will learn all the available features of the product, as well as information on its operation. The information that you get SteelEye 4.5.0 will certainly help you make a decision on the purchase.
If you already are a holder of SteelEye 4.5.0, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime SteelEye 4.5.0.
However, one of the most important roles played by the user manual is to help in solving problems with SteelEye 4.5.0. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device SteelEye 4.5.0 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
