HP StorageWorks Storage Mirroring application notes Guidelines for using Windows SharePoint Services with Storage Mirroring Part number: T2558–96057 Fifth edition: April 2007
Legal and notice information © Copyright 2005-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 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.
Configurations Windows SharePoint Services (WSS) combines stateless front-end web servers and back-end database servers. It can be configured in two different ways. • Single Standalone Server—In a standalone SharePoint environment, a single server is configured to run Windows SharePoint Services, Internet Information Services (IIS), and Microsoft SQL Server.
• Server Farm—In a server farm configuration, one or more servers are configured as front-end web servers, running both WSS and IIS, accessing 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.
of a source failure. In order to prevent overwriting the target's error logs, you will need to replicate the log files to a different location on the target. Create a separate replication set for the error logs and select the “All to One” mapping option.
To enable SQL 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 Windows SharePoint Services Configuration and Content Database Name Windows SharePoint Services Configuration and Content Database Path 7. Install Storage Mirroring on each source server using the installation defaults. See the HP W Storage Mirroring getting started guide for details.
Preparing the target(s) 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.
• World Wide Web Publishing Service • Simple Mail Transfer Protocol (SMTP) • Network News Transfer Protocol (NNTP) • HTTP SSL (Secure Sockets Layer) • SharePoint Timer Service 12. Install SQL on the target using the same configuration as the source. 13. Disable the SQL server auto-start policies. Verify that SQL Server and SQL Server Agent are not set to auto-start. 14.
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 _POSTOVER.
6. In the Monitor Settings window, mark the IP address that is going to failover and verify that Adding Source Identity to Target is selected. 7. Under Active Directory, enable Failover Hostname and Failback Hostname. 8. Click Account and specify a username and password with full domain administrative privileges. 9. Highlight the machine name under Names to Monitor and click Scripts. Specify the scripts that were created earlier using postover.bat for the target post-failover script and preback.
NOTE: You can also run the Storage Mirroring DTCL automated restoration script, which can be found in the HP StorageWorks Storage Mirroring user’s guide, to complete the remaining steps in this section. 12. Complete the appropriate fields as described below. • 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.
