HP StorageWorks Storage Mirroring application notes Guidelines for using Blackberry Enterprise server for IBM Lotus Domino Part number: T2558–96060 First edition: April 2007
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Document overview This document is a Storage Mirroring application note. An application note provides guidelines on the use of Storage Mirroring in a specific environment. This document contains: • Document overview—Explains what an application note contains, how it should be used, what you need to know before trying to use the application note, and where you can go for more information.
• Guidelines for using Lotus Domino with Storage Mirroring :In addition, the following application notes include best practices to assist with your implementation: • Guidelines for Minimizing Downtime During Failback and Restoration Using Storage Mirroring—This document describes an alternate restoration method that reduces the amount of downtime incurred during failback and restoration.
In addition, you may need to include the following directories, depending on your environment configuration: • Tempdb files. You should always include the tempdb files, unless you can determine that they are not being used by any application. Some applications, including Prophecy, PeopleSoft, and BizTalk, write data to the tempdb file. • Any other directories (even if on different drives) that you may have created to store SQL data files.
Target Source BlackBerry Enterprise Server Lotus Domino Storage Mirroring Microsoft SQL Server BlackBerry Enterprise Server Lotus Domino Storage Mirroring Microsoft SQL Server Mail Server Domino Mail Server Microsoft SQL Server can be installed on either the same server as BlackBerry Enterprise Server, or on a separate server. This application note assumes that both are installed on the same server.
If the MDS Connection service is being used on the source server, then the SQL besmgmt database will need to be automatically updated during failover. The besmgmt database does not automatically have a SQL user associated with it when it is created, so the SQL user must be added so that the machinename record can be updated with the failover script. NOTE: BlackBerry server name: Windows login information: Database name: SRP ID: SRP License Key: CAL License Key: 4.
• • • BlackBerry Router • BlackBerry Synchronization Service MSDE: • MSSQLServer • Distributed Transaction Coordinator • SQLServerAgent Lotus Domino: • Lotus Domino Server (dominodata) Configure and begin mirroring and replication The following steps create the Storage Mirroring replication set and establish the connection between the source and target. 1. On the source, select Start, Programs, Storage Mirroring, Management Console. 2. Double-click your source machine to log on. 3.
Configure failover and begin failure monitoring The following failover instructions apply to all configurations. 1. If a failure occurs, you will want to have the appropriate services start on the target automatically. To do this, create a batch file on the target called postover.bat using the sample batch file. Save the batch file to the same directory on the target where your Storage Mirroring files are installed.
SAMPLE_POSTOVER.BAT REM ***SAMPLE*** post-failover script for Blackberry Enterprise Server for Lotus Domino and MSDE. REM You may need to remark out some commands depending on the function of your target. REM This sample batch file is provided as an example only. Because no two REM environments or configurations are exactly the same, you MUST modify REM this script in order to make the solution work in your environment.
SAMPLE_UpdateMachineNameTarget.SQL /*********************************************************************** SAMPLE SQL script to change the machine name in the BESMGMT database. This will allow the Blackberry MDS service to function correctly after failover occurs on the target server. This script should be executed by the post failover script. This sample file is provided as an example only.
SAMPLE_PREBACK.BAT REM ***SAMPLE*** pre-failback script for Blackberry Enterprise Server and MSDE with Lotus Domino. REM You may need to remark out some commands depending on the function of your target. REM This sample batch file is provided as an example only. Because no two REM environments or configurations are exactly the same, you MUST modify REM this script in order to make the solution work in your environment. REM The following commands stop the services for Blackberry Enterprise Server.
SAMPLE_UpdateMachineNameSource.SQL /*********************************************************************** SAMPLE SQL script to change the machine name in the BESMGMT database. prior to failback so that the Blackberry MDS Connection Service functions properly after failback and restore. This sample file is provided as an example only. Because no two environments or configurations are exactly the same, you MUST modify this script in order to make the solution work in your environment.
3. 4. • • • 5. 6. 7. If you must rebuild your hard drive, complete the following. If you do not need to rebuild your hard drive, skip this step and continue with step 4. a. Install Windows. Since your source machine is not connected to the network, use the source’s original name and IP address. b. Register the source server into the same Domino Directory as your mail server, and assign it a Server ID as described in ”Preparing the source” on page 6. c. Install Lotus Domino Server on the source server.
You must also run the Storage Mirroring DTCL automated restoration script, which can be found in the Storage Mirroring User’s guide, to complete the remaining steps in this section. NOTE: 12. • • • • Complete the appropriate fields. Original Source—The name of the source machine where the data originally resided. Restore From—The name of the target machine that contains the replicated data. Replication Set—The name of the replication set to be restored.
