HP StorageWorks Storage Mirroring 5.
Legal and notice information © Copyright 2005-2008 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.
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.com/products/storage/software/sm/index.html. For help using Storage Mirroring, refer to the Storage Mirroring online manual or online help.
• Two servers running Microsoft Windows Server® 2003 x64 Edition • Two licensed copies of Storage Mirroring 5.0 or later • Two licensed copies of Oracle 11g for Windows (x64) • In addition, the system hardware must support 64-bit applications Modifying the sample script files After you modify the sample scripts, save them with a new name to remove the SAMPLE_ prefix. Copy the scripts to the directory where Storage Mirroring is installed. The sample batch files provided are only examples.
4. Install Storage Mirroring on the target using the installation defaults. See the Storage Mirroring Getting Started guide for details. Configure and begin mirroring and replication 1. In the Management Console, log in to your source machine. 2. Right-click your source machine and select New, Replication Set. Give the replication set a unique name. 3. In the tree under the replication set name, select the Oracle data you wish to protect.
File Name File Description Default Location Table to Query init.ora.xxxxx Initialization Parameter File Drive letter:\app\ \admin\\pfile N/A control#.ctl Control File Drive letter:\app\ \oradata\ V$CONTROLFILE redo#.log Online Redo Log Drive letter:\app\ \oradata\ V$LOGFILE system*.dbf System Tablespace Drive letter:\app\ \oradata\ V_$DATAFILE undotbs*.
NOTE: There is a unique numeric identifier at the end of the init.ora file (xxxxx) that uniquely identifies initialization files when there is more than one installed. Besides the initialization parameter file (init.ora), which is stored in a text format, administrators can choose to maintain the initialization parameters in a binary server parameter file (spfile.ora). This is installed by default. The Listener service will not start on the target if listener.
sample_postover.bat rem ## ***SAMPLE*** Oracle post-failover script 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 ## This script makes the following two assumptions: rem ## 1. You have created a directory c:\oracle_fo rem ## 2. The dbx_start.
<%ORACLE_FO%\db1_start.sql>%ORACLE_FO%\start_%ORACLE_SID%.log set ORACLE_SID=instance_name2 %ORACLE_HOME%\bin\sqlplus.exe "/ AS SYSDBA" <%ORACLE_FO%\db2_start.sql>%ORACLE_FO%\start_%ORACLE_SID%.log rem ## The following line starts the Oracle Listener service. The outcome is redirected to the rem ## failover directory where a log file is created. Check this log file for errors. NET START OracleOraDb11g_home1TNSListener >>%ORACLE_FO%\start_services.log The following example shows the DB_START.
sample_preback.bat rem ## ***SAMPLE*** Oracle pre-failback script 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 ## This script makes the following two assumptions: rem ## 1. You have created a directory c:\oracle_fo rem ## 2. The db_stop.
6. Select a source machine to monitor by clicking Add Monitor. Type the name of the source machine and click OK. The Monitor Settings window will open. 7. In the Monitor Settings window, select the checkbox for the IP address that is going to failover. 8. Highlight an IP address that you have selected for monitoring and select a Target Adapter that will assume that IP address during failover. Repeat this process for each IP address that is being monitored. 9.
b. Install Storage Mirroring using the installation defaults. c. Install Oracle using the installation settings previously used. 4. Disable all of the NICs on the source. 5. Change one of the NICs on the source to a unique IP address that the target can access. 6. Configure that IP address so that it does not automatically register with DNS. This option is on the Advanced TCP/IP Settings dialog box on the DNS tab. 7.
15. Verify that the selections you have made are correct and click Restore to begin the restoration. The restoration procedure time will vary depending on the amount of data that you have to restore. You can identify a restoration connection because it is enclosed in parenthesis ( ) and it has _Restore appended to the end of the replication set name. The initial restoration is complete when the Mirror Status is Idle.
