Using Simpana Software to perform DR restore of Oracle to point in time.

Transcription

1 Using Simpana Software to perform DR restore of Oracle to point in time. ID: Legacy Identifier: Document Type: Technical Solution Created: Jul 25, :09 PM Modified: Jun 30, :28 AM Version(s): Operating System(s): All Product(s): Oracle, Oracle Rac Capabilities: All Issue This document will provide an example of a DR restore of an Oracle 10g database using the Simpana Version 9.0 interface. Example is demonstrated using a UNIX\Linux Oracle Server. Windows based Oracle will be similar but with Noted exception during the process steps. Before removing the database, for this example, a Full and Incremental backup was run through the Simpana Software. Also, be sure to have the "Control File Auto-Backup" enabled in RMAN or through the Simpana Software at the "instance properties" of the database in question. After the last backup is run and completed, the backup history is brought up in the interface, and the details of the last incremental backup are examined. From the "General" tab of the Job Details window, the "Next SCN" # is noted and recorded. (This will be used for this example recovery point (PIT).)

2 Here is a screen shot from this example: Figure 1. At this point the protected database is then shut down, and removed from the server. The SPFile is also deleted. Below is the user session from the Oracle server showing the deletion of the database as well as the SPFile: [oracle@unixdboraent ~]$ sqlplus / as sysdba SQL*Plus: Release Production on Wed May 23 15:34: Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release

3 Production With the Partitioning, OLAP and Data Mining options SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release Production With the Partitioning, OLAP and Data Mining options [oracle@unixdboraent ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/volgroup00-logvol % / /dev/sda % /boot none % /dev/shm /dev/mapper/oraclegroup00-oralogvol % /oradata /dev/sdc % /iscsi/disk1 /dev/sdd % /oracle [oracle@unixdboraent ~]$ cd /oradata/oradb/ [oracle@unixdboraent oradb]$ ls control01.ctl control03.ctl redo01.log redo03.log system01.dbf undotbs01.dbf control02.ctl example01.dbf redo02.log sysaux01.dbf temp01.dbf users01.dbf [oracle@unixdboraent oradb]$ rm -rf./* [oracle@unixdboraent oradb]$ ls [oracle@unixdboraent oradb]$ df -lk Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/volgroup00-logvol % / /dev/sda % /boot none % /dev/shm /dev/mapper/oraclegroup00-oralogvol % /oradata /dev/sdc % /iscsi/disk1 /dev/sdd % /oracle [oracle@unixdboraent oradb]$ cd $ORACLE_HOME [oracle@unixdboraent 10g]$ cd dbs [oracle@unixdboraent dbs]$ ls hc_auxdb.dat hc_tsrst220.dat initdw.ora lktestc snapcf_auxdb.f hc_iscsidb.dat hc_tsrst7.dat init.ora lktsrst7 snapcf_oradb.f hc_oradb.dat initauxdb_cv.ora inittestc.ora orapwauxdb

4 spfileoradb.ora hc_orcl.dat #initauxdb.ora# lkauxdb orapworadb hc_testc.dat initauxdb.ora lkoradb orapwtestc dbs]$ rm spfileoradb.ora dbs]$ ls hc_auxdb.dat hc_testc.dat #initauxdb.ora# inittestc.ora lktsrst7 snapcf_auxdb.f hc_iscsidb.dat hc_tsrst220.dat initauxdb.ora lkauxdb orapwauxdb snapcf_oradb.f hc_oradb.dat hc_tsrst7.dat initdw.ora lkoradb orapworadb hc_orcl.dat initauxdb_cv.ora init.ora lktestc orapwtestc After the database was deleted, attempting to start the database results in the following error: dbs]$ sqlplus / as sysdba SQL*Plus: Release Production on Wed May 23 15:39: Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to an idle instance. SQL> startup nomount ORA-01078: failure in processing system parameters LRM-00109: could not open parameter file '/oracle/10g/dbs/initoradb.ora' SQL> exit Disconnected Since the instance MUST be started in a no-mount state for RMAN to restore any data, RMAN MUST be used to start the instance when the SPFile is gone. Below shows the instance getting started in "NOMOUNT" mode when the SPFile is missing: [oracle@unixdboraent dbs]$ rman target / Recovery Manager: Release Production on Wed May 23 15:40: Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database (not started)

5 startup force nomount startup failed: ORA-01078: failure in processing system parameters LRM-00109: could not open parameter file '/oracle/10g/dbs/initoradb.ora' starting Oracle instance without parameter file for retrival of spfile Oracle instance started Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes exit Recovery Manager complete. At this point the Oracle instance is ready for the restore to be started through the CommVault interface. Solution Steps Resolution 1. From the CommCell Browser interface, right click on the instance and select "All Tasks" "Restore". For the purpose of this example the following options were selected: "Restore Control File" "Restore SP File" "Restore Data" "Recover" and "NO CATALOG"

6 Figure 2. NOTE: The database "Status:" at the bottom left corner (Figure 2.) of the window is "Started" This means that the interface is able to connect to the instance which is "Started" in "no-mount" mode. 2. Select the "Advanced" button to open the "Oracle Advanced Restore Options" window where the appropriate additional options for this restore will be set. 3. From "Oracle Advanced Restore Options" window select the "Options" tab. 4. Select the "Open DB" checkbox and confirm it is checked. 5. Select the "Set DBID" checkbox and confirm it is checked. 6. Set the "Reset Logs" dropdown to "Yes":

7 Figure Select the "Restore" tab. 8. Confirm default option "Restore Data" checkbox is checked. 9. Confirm default option "From the Latest Backup" radio button is selected.

8 Figure Select the "Ctrl & SP Files" tab. 11. For the "Restore Control File" section make sure the "Restore From" and the option to restore "From auto Backup" are selected. 12. For the "Restore SP File" section make sure the 'Restore From" and the option to restore "From auto Backup" are selected. If the last backup job chosen to restore from is NOT from the same day as the restore job being run, then select and add the "To Point In Time" parameters.

9 NOTE: This will GREATLY reduce the time it takes for the RMAN process to search for the backup from within the CommServe Database. STEP 13. For the "Restore Control File" use the Completion Time Date and Time from the "Job Details for Job: xxxxxxxx" window (Figure 1.) where the Next SCN number was recorded. STEP 14. For the "Restore SP File" use the Completion Time Date and Time from the "Job Details for Job: xxxxxxxx" window (Figure 1.) where the Next SCN number was recorded. Figure 5. NOTE: One additional option to use when the name of the backup piece that contains the Control File or SP File is known. The "From backup piece" radio button option can then be used to restore directly from the piece in question. Using this option would negate the need to use the "Set DBID" option (Figure 3. Step 5) from the "Options" tab. 15. Select the "Recover" tab from the "Oracle Advanced Restore Options" window. 16. Confirm the Recover Checkbox is checked.

10 17. Select the SCN radio button and enter the SCN number from the "Job Details for Job: xxxxxxxx" window (Figure 1.) where the Next SCN number was recorded. Figure Select OK on the "Oracle Advanced Restore Options" window. The Oracle Restore Options window should be visible. 19. Select the "Script Preview" button (Figure 2.) on the bottom left. The RMAN script can now be reviewed (Before executing the actual restore). For this restore the resulting script can be observed in the pop-up window: (Figure 7.)

11 Figure 7. Since the entire script preview cannot be viewed in Figure 7 the script content has been copied out and pasted here: Example Script Preview ******CONTROL FILE/SPFILE RESTORE SCRIPT****** SET DBID ; run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1)" restore spfile from autobackup ; startup force nomount; } exit; SET DBID ; run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1)" restore controlfile from autobackup ; sql 'alter database mount'; } exit; ******DATA RESTORE SCRIPT****** run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1)" allocate channel ch2 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch2)" restore database ; } exit; run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1)"

12 allocate channel ch2 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch2)" recover database until scn ; sql "alter database open resetlogs"; } exit; 20. Close the Rman Script for Restore Job window by selecting OK (Figure 7). At this point the restore can be started. 21. Select the "OK" button (Figure 2.) to start the restore. The database will now be restored and recovered to the point in time referenced by the SCN # leaving the database "OPEN" when the job completes. After this job completed, below is the user session showing the restored data files as well as the SP File: [oracle@unixdboraent dbs]$ pwd /oracle/10g/dbs [oracle@unixdboraent dbs]$ ls hc_auxdb.dat hc_testc.dat #initauxdb.ora# inittestc.ora lktsrst7 snapcf_auxdb.f hc_iscsidb.dat hc_tsrst220.dat initauxdb.ora lkauxdb orapwauxdb snapcf_oradb.f hc_oradb.dat hc_tsrst7.dat initdw.ora lkoradb orapworadb spfileoradb.ora hc_orcl.dat initauxdb_cv.ora init.ora lktestc orapwtestc [oracle@unixdboraent dbs]$ cd /oradata/oradb/ [oracle@unixdboraent oradb]$ ls control01.ctl control03.ctl redo01.log redo03.log system01.dbf undotbs01.dbf control02.ctl example01.dbf redo02.log sysaux01.dbf temp01.dbf users01.dbf Below is a sqlplus session showing the status of the database after the completed restore and recovery: [oracle@unixdboraent oradb]$ sqlplus / as sysdba SQL*Plus: Release Production on Wed May 23 16:09:

13 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release Production With the Partitioning, OLAP and Data Mining options SQL> select status from v$instance; STATUS OPEN SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release Production With the Partitioning, OLAP and Data Mining options [oracle@unixdboraent oradb]$ The RMAN restore session has also been captured (From the Simpana Software) and can be seen below showing the phases of the RMAN restore as executed through the Simpana Software processes: Rman Script: [SET DBID ; run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 10 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:2:1 -bal 0 -rcp 0 -ms 2 -p 1 -cn unixdboraent -vm Instance001)" restore spfile from autobackup ; startup force nomount; } exit; ] Rman Log:[ Recovery Manager: Release Production on Wed May 23 15:50:38 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: DUMMY (not mounted) using target database control file instead of recovery catalog

14 executing command: SET DBID 2> 3> 4> 5> 6> 7> allocated channel: ch1 channel ch1: sid=36 devtype=sbt_tape channel ch1: CommVault Systems for Oracle: Version 9.0.0(BUILD84) Starting restore at May :50:41 channel ch1: looking for autobackup on day: channel ch1: autobackup found: c channel ch1: SPFILE restore from autobackup complete Finished restore at May :56:02 Oracle instance started Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Recovery Manager complete. ] Rman Script: [SET DBID ; run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 10 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:2:1 -bal 0 -rcp 0 -ms 2 -p 1 -cn unixdboraent -vm Instance001)" restore controlfile from autobackup ; sql 'alter database mount'; } exit; ] Rman Log:[ Recovery Manager: Release Production on Wed May 23 15:56:26 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: oradb (not mounted) using target database control file instead of recovery catalog executing command: SET DBID

15 2> 3> 4> 5> 6> 7> allocated channel: ch1 channel ch1: sid=156 devtype=sbt_tape channel ch1: CommVault Systems for Oracle: Version 9.0.0(BUILD84) Starting restore at May :56:29 channel ch1: looking for autobackup on day: channel ch1: autobackup found: c channel ch1: control file restore from autobackup complete output filename=/oradata/oradb/control01.ctl output filename=/oradata/oradb/control02.ctl output filename=/oradata/oradb/control03.ctl Finished restore at May :02:38 sql statement: alter database mount released channel: ch1 Recovery Manager complete. ] Rman Script: [run { allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:3:1 -bal 0 -rcp 0 -ms 2 -p 2 -cn unixdboraent -vm Instance001)" allocate channel ch2 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch2,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:3:1 -bal 0 -rcp 0 -ms 2 -p 2 -cn unixdboraent -vm Instance001)" restore database ; } exit; ] Rman Log:[ Recovery Manager: Release Production on Wed May 23 16:03:10 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: ORADB (DBID= , not open) using target database control file instead of recovery

16 catalog 2> 3> 4> 5> 6> 7> 8> 9> allocated channel: ch1 channel ch1: sid=158 devtype=sbt_tape channel ch1: CommVault Systems for Oracle: Version 9.0.0(BUILD84) allocated channel: ch2 channel ch2: sid=155 devtype=sbt_tape channel ch2: CommVault Systems for Oracle: Version 9.0.0(BUILD84) Starting restore at May :03:17 Starting implicit crosscheck backup at May :03:17 Crosschecked 4 objects Finished implicit crosscheck backup at May :03:23 Starting implicit crosscheck copy at May :03:23 Crosschecked 9 objects Finished implicit crosscheck copy at May :03:24 searching for all files in the recovery area cataloging files... no files cataloged channel ch1: starting datafile backupset restore channel ch1: specifying datafile(s) to restore from backup set restoring datafile to /oradata/oradb/sysaux01.dbf restoring datafile to /oradata/oradb/example01.dbf channel ch1: reading from backup piece 8vnbn7r4_1_1 channel ch2: starting datafile backupset restore channel ch2: specifying datafile(s) to restore from backup set restoring datafile to /oradata/oradb/system01.dbf restoring datafile to /oradata/oradb/undotbs01.dbf restoring datafile to /oradata/oradb/users01.dbf channel ch2: reading from backup piece 8unbn7r4_1_1 channel ch2: restored backup piece ( Appended) piece handle=8unbn7r4_1_1 tag=tag t channel ch2: restore complete, elapsed time: 00:02:26 channel ch1: restored backup piece ( Appended) piece handle=8vnbn7r4_1_1 tag=tag t channel ch1: restore complete, elapsed time: 00:02:41 Finished restore at May :06:14 released channel: ch1 released channel: ch2 Recovery Manager complete. ] Rman Script: [run {

17 allocate channel ch1 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:3:1 -bal 0 -rcp 0 -ms 2 -p 2 -cn unixdboraent -vm Instance001)" allocate channel ch2 type 'sbt_tape' 76,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch2,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 7 -ins 61 -at 0 -j jt 18325:3:1 -bal 0 -rcp 0 -ms 2 -p 2 -cn unixdboraent -vm Instance001)" recover database until scn ; sql "alter database open resetlogs"; } exit; ] Rman Log:[ Recovery Manager: Release Production on Wed May 23 16:06:30 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: ORADB (DBID= , not open) using target database control file instead of recovery catalog 2> 3> 4> 5> 6> 7> 8> 9> 10> allocated channel: ch1 channel ch1: sid=157 devtype=sbt_tape channel ch1: CommVault Systems for Oracle: Version 9.0.0(BUILD84) allocated channel: ch2 channel ch2: sid=156 devtype=sbt_tape channel ch2: CommVault Systems for Oracle: Version 9.0.0(BUILD84) Starting recover at May :06:38 channel ch1: starting incremental datafile backupset restore channel ch1: specifying datafile(s) to restore from backup set destination for restore of datafile 00003: /oradata/oradb/sysaux01.dbf destination for restore of datafile 00005: /oradata/oradb/example01.dbf channel ch1: reading from backup piece 98nbn8k3_1_1

18 channel ch2: starting incremental datafile backupset restore channel ch2: specifying datafile(s) to restore from backup set destination for restore of datafile 00001: /oradata/oradb/system01.dbf destination for restore of datafile 00002: /oradata/oradb/undotbs01.dbf destination for restore of datafile 00004: /oradata/oradb/users01.dbf channel ch2: reading from backup piece 97nbn8k3_1_1 channel ch1: restored backup piece ( Appended) piece handle=98nbn8k3_1_1 tag=tag t channel ch1: restore complete, elapsed time: 00:01:25 channel ch2: restored backup piece ( Appended) piece handle=97nbn8k3_1_1 tag=tag t channel ch2: restore complete, elapsed time: 00:01:25 starting media recovery channel ch1: starting archive log restore to default destination channel ch1: restoring archive log archive log thread=1 sequence=8 channel ch1: restoring archive log archive log thread=1 sequence=9 channel ch1: reading from backup piece 9cnbn8o9_1_1 channel ch1: restored backup piece ( Appended) piece handle=9cnbn8o9_1_1 tag=tag t channel ch1: restore complete, elapsed time: 00:00:07 archive log filename=/oracle/flash_recovery_area/oradb/archivelog/2012_0 5_23/o1_mf_1_8_7vtjxllv_.arc thread=1 sequence=8 channel default: deleting archive log(s) archive log filename=/oracle/flash_recovery_area/oradb/archivelog/2012_0 5_23/o1_mf_1_8_7vtjxllv_.arc recid=5259 stamp= archive log filename=/oracle/flash_recovery_area/oradb/archivelog/2012_0 5_23/o1_mf_1_9_7vtjxlwq_.arc thread=1 sequence=9 channel default: deleting archive log(s) archive log filename=/oracle/flash_recovery_area/oradb/archivelog/2012_0 5_23/o1_mf_1_9_7vtjxlwq_.arc recid=5260 stamp= media recovery complete, elapsed time: 00:00:02 Finished recover at May :08:21

19 sql statement: alter database open resetlogs released channel: ch1 released channel: ch2 Recovery Manager complete. ] Additional Info Product Version(s) 9.0 Subject(s): Oracle idataagent Restore to Point in Time (PIT) Language(s): ALL Operating System Version(s): All OS's that Support Oracle ida restore Acknowledgement(s): N/A