SteelEye 4.5.0 manuel d'utilisation

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. Other brand and product names used herein are for identification pu[...]

Table of Contents Introduction ................................................................................................................................3 Document Contents .............................................................................................................3 LifeKeeper Documentation ...................................[...]

[...]

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. The LifeKeeper ® for Linux SAMS Recovery Kit provides a mechanism to rec[...]

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. LifeKeeper Documentation The following is a list of LifeKeeper related info[...]

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 Guide • Sendmail Advanced Message Server Installation Guide • Sendmail Advanced Message Server User’s Guide • Sendmail Switch Installation Guid[...]

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. You must install the same version of LifeKeeper software and any patches on each server. [...]

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. Currently,[...]

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. In an active/standby configuration, one server acts as a primary mailhub or mailserver, while the other server acts as a back[...]

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. Protected Files, Directories and Services The SAMS Recovery Kit protects th e following configuration and data directories: • /etc/mail ?[...]

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. Masquerading can[...]

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. MX r ecords also provide a mechanism o[...]

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 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 se[...]

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. 6. The MTA and MSP spool directories (e.g., /var/spool/mqueue and /var/spool/clientmqueue) o[...]

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.e. Server 1), the Recovery Kit moves the /etc/md, /etc/mail, and /var/md/[...]

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.e. Server 2), the Re[...]

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 unmount[...]

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. • Create a Resource Hierarchy . Creates an application resource hierarch[...]

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 Resource Hierarchy Table (right-hand pane) of the status display window to perform all the configuration tasks, except Creating a Resource Hierarchy [...]

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 . From the drop down menu, select Create Resource Hierarchy . IMPORTANT: The switchable IP address should be under LifeKeeper protection before creating the SAMS [...]

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 . Intelligent switchback requires administrative intervention to switch the instance back to the [...]

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. The list will show only those IP addresses that are in-service on this server. Important: Verify that the priority of the IP Tag on the primary server is higher than the priority of the IP Tag on[...]

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 . . . END succes[...]

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. From the LifeKeeper GUI menu, select Edit , then Resource . From the drop down menu, select [...]

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. 5. Another information box appears confirming that the SAMS res[...]

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 [...]

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 SAMS resource ic on in the left-hand pane or right- click on the SAMS resource box in the right-hand pane the of the GUI window and choose Extend Resou[...]

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. You can choose either intelligent or automatic . Intelligent switchback requires adm[...]

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. If there were some requirements that had not been met, LifeKeeper would not allow you to select the Next button, and the Back button would[...]

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. You cannot change the Netmask that appears in the box. Note: This dialog box will not appear if you are extending this SAMS resource immediately following i[...]

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. 14. An information box will appear veri fying that the extension is being Extending resource instances for sams Creating dependencies Setting switchback ty pe for hierarchy Creating equivalen[...]

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 . From the drop down menu, select Unextend Res[...]

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. E C S C L H Creating Resource Instance “sams” with id “sams” [...]

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. For example, an in service request executed on a backup server causes the application hierarchy to be placed in service on the ba[...]

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. Other messages from ot[...]

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. See the LifeKeeper error log for additional troubles[...]

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.conf file. ERROR: Failed to move “$DIR” to “$SHARED_FS” LifeKeeper was unable to move a directory and its contents to the shared fi[...]

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. ERROR: Failed to create LifeKeeper “mail” Resource Type “sams” on serve[...]

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. Error - canextend () – Failed to copy “$CONFIG_FILE_NAME” on server ?[...]

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. Review all the resources that are LifeKeeper-protected on the sp[...]

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. It indicates that the SAMS daemons that are to be brought in-service are already running on the specif[...]

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. SAMS Resource Health Monitoring Error Messages daemon is not responding on $IP:$PORT quickCheck: sams: attempting local recovery of [...]