HP StorageWorks Storage Mirroring application notes High availability for SharePoint Portal Server Part number: T2558–96058 Fourth edition: April 2007
Legal and notice information © T2558–96058 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. This document contains proprietary information, which is protected by copyright.
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 Optimizing your Storage Mirroring Solution—This document describes several configuration changes that can be used to optimize Storage Mirroring replication and mirror performance and improve the manageability of your data protection solution. Getting help Hewlett-Packard has application notes that describe how to configure Storage Mirroring with a variety of popular third-party applications. These application notes are available on the Storage Mirroring web site: http://h18006.www1.hp.
roles and changing the component configuration, see your SharePoint Portal Server product documentation.
• Server Farm—In a server farm configuration, multiple role servers are configured to access data from a SQL Server database located on an independent server. Again, Storage Mirroring can be used to replicate and failover the SQL server to an independent target server.
greatly reduce the amount of required bandwidth, you should check with your application vendor and test the failover process to ensure complete recovery of your application. • Any other directories (even if on different drives) that you may have created to store SQL database (.mdf) or transaction (.ldf) files • The SQL Log directory (:\Program Files\Microsoft SQL Server\MSSQL\Log).
To enable SharePoint Portal Server to work with MSDE (SQL Express 2000) and SQL Server 2005 Express, Named Pipes and TCP/IP need to be added to the Enabled Protocols. By default, these are disabled. They must be enabled to accept remote connections. • For MSDE, you must run the “svrnetcn.exe” command, which is located in the “C:\Program Files\Microsoft SQL Server\80\Tools\Binn” directory.
Back -End SQL Server SharePoint Portal Server Configuration and Content Database Name SharePoint Portal Server Configuration and Content Database Path 7. Install Storage Mirroring on each source server using the installation defaults. See the HP StorageWorks Storage Mirroring getting started guide for details.
Preparing the target 1. Configure each Windows 2003 target as a member server in the same Active Directory domain or trusted domain environment as the source. 2. Install Storage Mirroring on each target server using the installation defaults. See the HP StorageWorks Storage Mirroring getting started guide for details. 3. The remaining target preparation steps are dependent on what role your target must take on in the event of a source failure.
• Simple Mail Transfer Protocol (SMTP) • Network News Transfer Protocol (NNTP) • HTTP SSL (Secure Sockets Layer) • SharePoint Timer Service • Microsoft SharePointPS Search • Microsoft Single Sign-on Service • SharePoint Portal Administration • SharePoint Portal Alert 12. Install SQL on the target using the same configuration as the source. 13. Stop the following services and set them to manual startup so that all SQL files are closed on the target so that the source can replicate the changes.
Configure failover and begin failure monitoring The following steps should be performed on the target machine. 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 below. Save the batch file to the same directory on the target where your Storage Mirroring files are installed.
SAMPLE_PREBACK.BAT rem ***SAMPLE*** pre-failback script for SharePoint Portal Server and SQL 2000. 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 rem rem rem You may need to remark out some commands depending on the function of your target. The following commands should be used if your target is functioning as a back-end SQL target.
NOTE: If you must rebuild your hard drive, continue with step 3. If you do not need to rebuild your hard drive, verify that the Storage Mirroring connection on the source has been disconnected (right-click the connection in the Storage Mirroring Management Console and select Disconnect) and then continue with step 4. 3. 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.
16. Reestablish the Storage Mirroring replication set and connection. 17. On the Mirroring tab, select File differences with the Use block checksum option. NOTE: If the target has been previously mirrored to or restored, select File differences with the Use block checksum option so that only the changed data is sent across the network.
