HP Data Protector Software HP Data Protector and Oracle 10g RAC configuration best practices Table of contents Executive summary............................................................................................................................... 3 Overview ............................................................................................................................................ 3 Target audience .....................................................................................
Restore Recommendations Summary ................................................................................................. 25 Recovery Considerations ................................................................................................................. 25 Summary .......................................................................................................................................... 27 Appendix A. Reference documentation ....................................................
Executive summary This white paper provides guidance and best practices for performing backup and restore of Oracle 10g Real Application Clusters using HP Data Protector Software. Since the release of Oracle 9i Real Application Clusters, there has always been uncertainty about what needs to be backed up and how to backup the RAC database. We will try to address these questions throughout this paper.
The following figure shows the environment described above: Figure 1. Hardware architecture The database had a size of 300GB and was created using the AXWORK suite. This suite created a new tablespace called POOL, with 66 datafiles, each 4095MB in size. The following representation shows the distribution of the datafiles. Note that they are all of equal size: FILE_NAME MB -------------------------------------------------- ---------+DG_DB/rac/datafile/tbs_pool_001.dbf 4095 +DG_DB/rac/datafile/tbs_pool_002.
The following screenshot shows the graphical display shown by the Oracle Enterprise Manager (Database Console): Figure 2. Oracle Enterprise Manager: POOL datafiles view Two extra LUN were allocated on the shared storage for the Oracle Cluster Registry (OCR) and Oracle voting disks. Below, a list of CRS resources defined in our cluster and their status: oracle@ita018[RAC1]:/opt/oracle/product/CRS/bin$ ./crsstat.sh HA Resource Target State -------------------ora.RAC.BACKUP.RAC1.srv ONLINE ONLINE ora.RAC.
10gRAC configurations on hp-ux Starting with Oracle10g RAC, there are different configurations possible for HP-UX; essentially, the customer needs to decide about which clustering solution will be deployed: • Service Guard Extension for RAC + Oracle Clusterware • Oracle Clusterware only Based on the storage volume manager choice, there are three main alternatives: • Oracle Automatic Storage Management (ASM) • HP Cluster File system (CFS) • RAW devices Important Note: RAW devices do NOT provide a shared loca
Oracle Virtual IP Address Since Oracle 10g, clients use a Virtual IP Address (VIP) to connect to the database. The VIP is a static IP which is defined in the Oracle Clusterware installation. When a RAC node fails, its associated VIP will failover automatically to one of the remaining nodes. The new node hosting the failed VIP will associate a new MAC address for this VIP and will make it known outside.
Figure 4. Database Configuration Assistant: Database Service BACKUP The following figure is a graphical representation of the BACKUP service, which expands over all available instances: Figure 5. Oracle Service BACKUP We define also a service called MSL5000, allowed to run on two of the four instances; we set two instances to Preferred and two instances to Not Used.
Figure 6. Database Configuration Assistant: Database Service MSL5000 For the Oracle Service MSL5000, we can see below how only instances RAC1 and RAC2 are available for this service: Figure 7.
The configuration can be verified using the following command: oracle@ita018[RAC1]:/home/oracle$ srvctl status service -d RAC -s BACKUP,MSL5000 Service BACKUP is running on instance(s) RAC1, RAC4, RAC3, RAC2 Service MSL5000 is running on instance(s) RAC1, RAC2 Oracle Online Backup Configuration This section discusses topics such as Backup Session Failover and Backup Load Balancing. In a large customer environment, hundreds of Oracle Databases are backed up daily.
The following screenshot shows a list of the available clients in our cell server: Figure 8. Data Protector Cell Clients At this point, there are 4 main strategies to configure a backup specification of the Oracle RAC database • Configure the backup using the node name and instance, i.e. ita018 and RAC1 • Configure the backup using a VIP and all instances, i.e. ita018-vip and RAC1,RAC2,RAC3,RAC4 • Configure the backup using a VIP and a service name, i.e.
This configuration has the drawback of not providing any failover in case the configured instance is not available. If the session is scheduled and the instance is down, the backup session will fail. In addition, only one node in the cluster is performing the backup. Use a VIP and the Instance names to configure the backup In this case, we need to use a VIP as a client to be able to provide failover. We provide the integration a list with the Instances (RAC1, RAC2, RAC3, and RAC4). Figure 10.
The Oracle integration uses a VIP as a client to guarantee failover. Figure 11. Oracle Integration configuration windows Node Affinity awareness: In a RAC environment, some nodes of the cluster have faster access to specific datafiles. RMAN is aware of the node affinity, and will try to assign specific datafiles to the channels of the nodes which have faster access to these datafiles.
Although the backup specification could also be edited on the cell server, located in $OMNICONFIG/barlists/oracle8, using the GUI is the only supported method to edit a backup script. Figure 12.
Figure 13. Data Protector RMAN script edit window • Connect with RMAN to the instance and recovery catalog and specify the channel parallelism we want to use; in our case parallelism 2 (two tapes devices) RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET; • In the recovery catalog, configure the channels with the connection string. We define two SBT channels, 1 connecting to instance RAC1 and 2 connecting to RAC2.
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET; CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE T
When performing an Oracle restore, RMAN will only read with concurrency ONE from tape (just one channel at a time), independent from the concurrency used during the backup. The recommendation is to use always concurrency of 1 (one RMAN channel per tape drive) Set Maxopenfiles to 1 RMAN channel parameter MAXOPENFILES should be set to 1 in case you are using a Disk Array such as XP or EVA where the data is stripped over different physical disks.
SAN Backup versus LAN Backup Avoid having data being sent over LAN unnecessarily when working in a SAN environment. In the following two figures, we illustrate two possible scenarios describing SAN backup versus LAN backup in a RAC environment. Note Disk Agent: process which reads data from disk in a backup and writes data to disk in a restore. In an Oracle environment, instead of Disk Agents, Oracle processes are started.
Figure 15. Backup data flow: DA and MA exchange data using memory buffers File System Backup: Oracle Base and Cluster configuration After reviewing the online backup configuration of the RAC database, we need to focus on the backup of the Oracle software directories and the cluster configuration files. As these components are not addressed in the Online backup, we need to define an additional File System backup specification.
Oracle Cluster Registry (OCR) The Oracle Cluster Registry is a binary file which can be mirrored for redundancy. It holds the entire cluster related information, such as instances names, resources, etc. The location of the OCR is /var/opt/oracle/ocr.loc: oracle@ita018[RAC1]:/home/oracle$ cat /var/opt/oracle/ocr.loc ocrconfig_loc=/hpap/rdsk/hpap0 local_only=FALSE Oracle provides an automatic mechanism which performs regular backups of the OCR. The OCR daemons are in charge of these periodic snapshots.
To perform the backup (online), we use the dd Operating System utility (ocopy for Windows): oracle@ita018[RAC1]:/home/oracle$ dd if=/hpap/rdsk/hpap1 \ of=voting_backup.`date +%Y%m%d_%H:%M:%S` bs=4k 262144+0 records in 262144+0 records out oracle@ita018[RAC1]:/home/oracle$ ll -rw-r--r-- 1 oracle oinstall 1073741824 Sep 10 14:44 voting_backup.20070910_14:43:41 In our case, the LUN where the Voting Disk is located is 1GB in size.
Oracle RMAN Restore and Recovery Oracle Restore Enhancements Starting with Oracle 10g Release 2, Data Protector includes a series of enhancements to improve restore performance.
57 59 61 63 65 67 69 71 73 0 0 0 0 0 0 0 0 0 Incr Incr Incr Incr Incr Incr Incr Incr Incr 32918890 32918890 32918890 32918890 32918890 32918890 32918890 32918890 32918890 2007-10-05 2007-10-05 2007-10-05 2007-10-05 2007-10-05 2007-10-05 2007-10-05 2007-10-05 2007-10-05 +DG_DB/rac/datafile/tbs_pool_032.dbf +DG_DB/rac/datafile/tbs_pool_022.dbf +DG_DB/rac/datafile/tbs_pool_021.dbf +DG_DB/rac/datafile/tbs_pool_027.dbf +DG_DB/rac/datafile/tbs_pool_017.dbf +DG_DB/rac/datafile/tbs_pool_026.
When the variable points to a valid location, the restore through the GUI will save the RMAN restore script to the specified location and it will not execute the restore. Once the script has been saved, it can be edited and changed. Afterwards, you can start it from RMAN directly. OB2RMANSAVE=/opt/oracle/ Once the script has been saved, it can be edited and changed. Afterwards, you can start it from RMAN directly as shown below: $ rman target / catalog rman/xxx@RCVCAT cmdfile rman_script.
The restore session report is in the Appendix C under Session 6.
Recovery using archived logs Approximately, 500 archived logs were generated during the table update on all four RAC instances. Media Recovery is performed on the system where the restore/recovery session was started, RAC1 in our case. In our environment, it took 1hour 50 min to apply all 536 archived logs. In total 23GB redo information. Using the dynamic view V$RECOVERY_PROGRESS, we can monitor the status of the running recovery.
To enable this functionality, issue the following command: SQL> select status from v$block_change_tracking; STATUS ---------DISABLED SQL> alter database enable block change tracking; Database altered. SQL> select status from v$block_change_tracking; STATUS ---------ENABLED; SQL> select FILENAME,bytes from v$block_change_tracking; FILENAME BYTES ---------------------------------------------- ---------- +DG_DB/rac/changetracking/ctf.351.
Appendix A. Reference documentation HP • HP Data Protector Software Documentation and White Papers • HP 3TB/hour Oracle Online Backup paper Oracle • Oracle 10g Backup and Recovery Advanced User’s Guide • Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide • Tuning Oracle Recovery Manager • Data Guard Redo Apply and Media Recovery Best Practices • Oracle Backup and Recovery Papers at OTN • Metalink Note 237083.
Appendix B. RMAN helpful Scripts B.1 How to monitor RMAN job progress SELECT SID, SERIAL#, CONTEXT, SOFAR, TOTALWORK, ROUND(SOFAR/TOTALWORK*100,2) "%_COMPLETE" FROM V$SESSION_LONGOPS WHERE OPNAME LIKE 'RMAN%' AND OPNAME NOT LIKE '%aggregate%' AND TOTALWORK != 0 AND SOFAR <> TOTALWORK / SQL> @ RMAN_long_ops.sql SID SERIAL# CONTEXT SOFAR TOTALWORK %_COMPLETE ---------- ---------- ---------- ---------- ---------- ---------2214 214 1 5065599 17297280 29.29 B.
B.3 How to monitor RMAN wait states COLUMN EVENT FORMAT a20 COLUMN SECONDS_IN_WAIT FORMAT 999 COLUMN STATE FORMAT a20 COLUMN CLIENT_INFO FORMAT a30 SELECT p.SPID, sw.EVENT, s.SECONDS_IN_WAIT AS SEC_WAIT, sw.STATE, s.CLIENT_INFO FROM V$SESSION_WAIT sw, V$SESSION s, V$PROCESS p WHERE sw.EVENT LIKE '%sbt%' AND s.SID=sw.SID AND s.PADDR=p.ADDR ; SQL> @RMAN_MML_monitor.
Appendix C. Session Reports Session 1: Backup using ita018 and RAC1 • Connection to Instance RAC1 • Allocation of two channels on RAC1 (one for each tape drive) [Normal] From: BSM@ita017 "RAC_POOL_RAC1" Time: 11.10.2007 17:40:40 OB2BAR application on "ita018" successfully started. [Normal] From: ob2rman@ita018 "RAC" Time: 10/11/07 17:40:46 Starting backup of target database. Net service name: RAC1. Instance status: OPEN. Instance name: RAC1. Database DBID = 2216826430.
input datafile fno=00017 name=+DG_DB/rac/datafile/tbs_pool_004.dbf input datafile fno=00019 name=+DG_DB/rac/datafile/tbs_pool_006.dbf input datafile fno=00021 name=+DG_DB/rac/datafile/tbs_pool_008.dbf input datafile fno=00023 name=+DG_DB/rac/datafile/tbs_pool_005.dbf input datafile fno=00025 name=+DG_DB/rac/datafile/tbs_pool_007.dbf input datafile fno=00027 name=+DG_DB/rac/datafile/tbs_pool_014.dbf input datafile fno=00029 name=+DG_DB/rac/datafile/tbs_pool_011.
STARTING Media Agent "COMPAQ:SDLT320_1" input datafile fno=00074 name=+DG_DB/rac/datafile/tbs_pool_046.dbf channel dev_1: starting piece 1 at 11-OCT-07 [Normal] From: BMA@ita018 "COMPAQ:SDLT320_2" Time: 11.10.2007 17:41:12 STARTING Media Agent "COMPAQ:SDLT320_2" [Normal] From: BMA@ita018 "COMPAQ:SDLT320_1" Time: 11.10.2007 17:41:12 By: UMA@ita018@/dev/rac/c20t0d0 Loading medium from slot 15 to device /dev/rmt/0mn [Normal] From: BMA@ita018 "COMPAQ:SDLT320_2" Time: 11.10.
released channel: dev_1 Recovery Manager complete. [Normal] From: ob2rman@ita018 "RAC" Time: 10/11/07 18:30:34 Oracle Recovery Manager completed. [Normal] From: ob2rman@ita018 "RAC" Time: 10/11/07 18:30:35 Backup of target database completed. [Normal] From: BSM@ita017 "RAC_POOL_RAC1" Time: 11.10.2007 18:30:31 OB2BAR application on "ita018" disconnected. [Normal] From: BMA@ita018 "COMPAQ:SDLT320_2" Time: 11.10.
Session 2: Backup using ita018-vip and RAC1, RAC2, RAC3, RAC4 • Connectivity to all configured instances is verified • All channels are allocated on instance RAC1 [Normal] From: BSM@ita017 "RAC_POOL_RAC1..4" Time: 11.10.2007 18:41:52 OB2BAR application on "ita018-vip" successfully started. [Normal] From: ob2rman@ita018 "RAC" Time: 10/11/07 18:41:58 Starting backup of target database. Net service name: RAC1. Instance status: OPEN. Instance name: RAC1. Database DBID = 2216826430.
11> } 12> EXIT connected to target database: RAC (DBID=2216826430) connected to recovery catalog database allocated channel: dev_0 channel dev_0: sid=2230 instance=RAC1 devtype=SBT_TAPE channel dev_0: Data Protector A.06.00/PHSS_35908/PHSS_35909/DPSOL_00261/DPLNX_ allocated channel: dev_1 channel dev_1: sid=2204 instance=RAC1 devtype=SBT_TAPE channel dev_1: Data Protector A.06.
input datafile fno=00034 name=+DG_DB/rac/datafile/tbs_pool_053.dbf input datafile fno=00036 name=+DG_DB/rac/datafile/tbs_pool_050.dbf input datafile fno=00038 name=+DG_DB/rac/datafile/tbs_pool_056.dbf input datafile fno=00040 name=+DG_DB/rac/datafile/tbs_pool_049.dbf input datafile fno=00042 name=+DG_DB/rac/datafile/tbs_pool_055.dbf input datafile fno=00044 name=+DG_DB/rac/datafile/tbs_pool_034.dbf input datafile fno=00046 name=+DG_DB/rac/datafile/tbs_pool_045.
piece handle=RAC_POOL_RAC1..4.dbf tag=TAG20071011T184224 comment=API Version 2.0,MMS Version 65.6.0.0 channel dev_1: backup set complete, elapsed time: 00:47:42 Finished backup at 11-OCT-07 Starting Control File and SPFILE Autobackup at 11-OCT-07 [Normal] From: OB2BAR_Oracle8@ita018 "RAC" Time: 11.10.2007 19:30:56 Starting OB2BAR Backup: ita018-vip:c-2216826430-20071011-03 "Oracle8" [Normal] From: OB2BAR_Oracle8@ita018 "RAC" Time: 11.10.2007 19:30:58 Backup Profile: Run Time .......
Disk Agents Total ........... 3 ======================================== Completed Media Agents ....... 2 Failed Media Agents .......... 0 Aborted Media Agents ......... 0 ---------------------------------------Media Agents Total .......... 2 ======================================== Mbytes Total ................. 233898 MB Used Media Total ............. 2 Disk Agent Errors Total ......
Session 3: Backup using ita018-vip and service BACKUP • Two channels are allocated on RAC2 and two on RAC3 [Normal] From: BSM@ita017 "RAC_POOL_BACKUP" Time: 11.10.2007 20:15:57 OB2BAR application on "ita018-vip" successfully started. [Normal] From: ob2rman@ita018 "RAC" Time: 10/11/07 20:16:03 Starting backup of target database. Net service name: BACKUP. Instance status: OPEN. Instance name: RAC3. Database DBID = 2216826430. Database control file type: CURRENT. Database log mode: ARCHIVELOG.
channel dev_3: Data Protector A.06.00/PHSS_35908/PHSS_35909/DPSOL_00261/DPLNX_ Starting backup at 11-OCT-07 channel dev_0: starting incremental level 0 datafile backupset channel dev_0: specifying datafile(s) in backupset input datafile fno=00009 name=+DG_DB/rac/datafile/tbs_pool_001.dbf input datafile fno=00013 name=+DG_DB/rac/datafile/tbs_pool_002.dbf input datafile fno=00017 name=+DG_DB/rac/datafile/tbs_pool_004.dbf input datafile fno=00021 name=+DG_DB/rac/datafile/tbs_pool_008.
input datafile fno=00035 name=+DG_DB/rac/datafile/tbs_pool_015.dbf input datafile fno=00039 name=+DG_DB/rac/datafile/tbs_pool_016.dbf input datafile fno=00043 name=+DG_DB/rac/datafile/tbs_pool_031.dbf input datafile fno=00047 name=+DG_DB/rac/datafile/tbs_pool_018.dbf input datafile fno=00051 name=+DG_DB/rac/datafile/tbs_pool_024.dbf input datafile fno=00055 name=+DG_DB/rac/datafile/tbs_pool_029.dbf input datafile fno=00059 name=+DG_DB/rac/datafile/tbs_pool_022.
piece handle=RAC_POOL_BACKUP.dbf tag=TAG20071011T201615 comment=API Version 2.0,MMS Version 65.6.0.0 channel dev_2: backup set complete, elapsed time: 01:11:16 [Normal] From: OB2BAR_Oracle8@ita021 "RAC" Time: 11.10.2007 21:47:32 Backup Profile: Run Time ........... 1:30:41 Backup Speed ....... 11312,23 (KB/s) [Normal] From: OB2BAR_Oracle8@ita021 "RAC" Time: 11.10.2007 21:47:32 Completed OB2BAR Backup: ita018-vip:RAC_POOL_BACKUP.
By: UMA@ita018@/dev/rac/c20t0d0 Unloading medium to slot 22 from device /dev/rmt/0mn [Normal] From: BMA@ita018 "COMPAQ:SDLT320_1" Time: 11.10.2007 21:52:08 COMPLETED Media Agent "COMPAQ:SDLT320_1" [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 11.10.2007 21:52:45 /dev/rmt/1mn Medium header verification completed, 0 errors found [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 11.10.
Session 4: Backup using ita018-vip and service MSL5000 • Two channels allocated on RAC2 and none on RAC1 [Normal] From: BSM@ita017 "RAC_POOL_MSL5000" Time: 19.10.2007 09:21:34 OB2BAR application on "ita018-vip" successfully started. [Normal] From: ob2rman@ita018 "RAC" Time: 10/19/07 09:21:36 Starting backup of target database. Net service name: MSL5000. Instance status: OPEN. Instance name: RAC1. Database DBID = 2216826430. Database control file type: CURRENT. Database log mode: ARCHIVELOG.
input datafile fno=00027 name=+DG_DB/rac/datafile/tbs_pool_014.dbf input datafile fno=00029 name=+DG_DB/rac/datafile/tbs_pool_011.dbf input datafile fno=00031 name=+DG_DB/rac/datafile/tbs_pool_013.dbf input datafile fno=00033 name=+DG_DB/rac/datafile/tbs_pool_012.dbf input datafile fno=00035 name=+DG_DB/rac/datafile/tbs_pool_015.dbf input datafile fno=00037 name=+DG_DB/rac/datafile/tbs_pool_009.dbf input datafile fno=00039 name=+DG_DB/rac/datafile/tbs_pool_016.
By: UMA@ita018@/dev/rac/c20t0d0 Loading medium from slot 25 to device /dev/rmt/0mn [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 19.10.2007 09:21:57 STARTING Media Agent "COMPAQ:SDLT320_2" [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 19.10.2007 09:22:07 By: UMA@ita018@/dev/rac/c20t0d0 Loading medium from slot 12 to device /dev/rmt/1mn [Normal] From: OB2BAR_Oracle8@ita021 "RAC" Time: 19.10.2007 09:22:26 Starting OB2BAR Backup: ita018-vip:RAC_POOL_MSL5000.
[Normal] From: ob2rman@ita018 "RAC" Time: 10/19/07 10:10:41 Backup of target database completed. [Normal] From: BSM@ita017 "RAC_POOL_MSL5000" Time: 19.10.2007 10:10:41 OB2BAR application on "ita018-vip" disconnected. [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 19.10.2007 10:11:29 /dev/rmt/1mn Medium header verification completed, 0 errors found [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 19.10.
Session 5: Backup allocating channels manually on RAC1 and RAC2 [Normal] From: BSM@ita017 "RAC_POOL_man_ch_1_2" Time: 05.10.2007 17:25:33 OB2BAR application on "ita018-vip" successfully started. [Normal] From: ob2rman@ita018 "RAC" Time: 10/05/07 17:25:39 Starting backup of target database. Net service name: MSL5000. Instance status: OPEN. Instance name: RAC2. Database DBID = 2216826430. Database control file type: CURRENT. Database log mode: ARCHIVELOG.
input datafile fno=00029 name=+DG_DB/rac/datafile/tbs_pool_011.dbf input datafile fno=00031 name=+DG_DB/rac/datafile/tbs_pool_013.dbf input datafile fno=00033 name=+DG_DB/rac/datafile/tbs_pool_012.dbf input datafile fno=00035 name=+DG_DB/rac/datafile/tbs_pool_015.dbf input datafile fno=00037 name=+DG_DB/rac/datafile/tbs_pool_009.dbf input datafile fno=00039 name=+DG_DB/rac/datafile/tbs_pool_016.dbf input datafile fno=00041 name=+DG_DB/rac/datafile/tbs_pool_010.
Loading medium from slot 22 to device /dev/rmt/0mn [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 05.10.2007 17:25:57 STARTING Media Agent "COMPAQ:SDLT320_2" [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 05.10.2007 17:26:07 By: UMA@ita018@/dev/rac/c20t0d0 Loading medium from slot 6 to device /dev/rmt/1mn [Normal] From: OB2BAR_Oracle8@ita018 "RAC" Time: 05.10.2007 17:26:31 Starting OB2BAR Backup: ita018-vip:RAC_POOL_man_ch_1_2.
[Normal] From: ob2rman@ita018 "RAC" Time: 10/05/07 18:12:30 Backup of target database completed. [Normal] From: BSM@ita017 "RAC_POOL_man_ch_1_2" Time: 05.10.2007 18:12:27 OB2BAR application on "ita018-vip" disconnected. [Normal] From: BMA@ita021 "COMPAQ:SDLT320_2" Time: 05.10.2007 18:13:23 /dev/rmt/1mn Medium header verification completed, 0 errors found [Normal] From: BMA@ita018 "COMPAQ:SDLT320_1" Time: 05.10.
Session 6: Restore allocating channels manually on RAC1 and RAC2 • Manually created RMAN script • Channels allocated on RAC1 and RAC2 using the connection string sys/xxx@ • Tablespace POOL offline • Restore • Recovery oracle@ita018[RAC1]:/opt/oracle$ rman target sys/sys@MSL5000 catalog rman/rman@rcvcat cmdfile restore_RAC_POOL_2ch.rcv Recovery Manager: Release 10.2.0.3.0 - Production on Tue Oct 9 13:35:51 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved.
restoring datafile 00042 to +DG_DB/rac/datafile/tbs_pool_055.dbf restoring datafile 00044 to +DG_DB/rac/datafile/tbs_pool_034.dbf restoring datafile 00046 to +DG_DB/rac/datafile/tbs_pool_045.dbf restoring datafile 00048 to +DG_DB/rac/datafile/tbs_pool_047.dbf restoring datafile 00050 to +DG_DB/rac/datafile/tbs_pool_042.dbf restoring datafile 00052 to +DG_DB/rac/datafile/tbs_pool_041.dbf restoring datafile 00054 to +DG_DB/rac/datafile/tbs_pool_035.
archive log thread 1 sequence 1091 is already on disk as file +DG_FRA/rac/1_1091_628844420.dbf archive log thread 1 sequence 1092 is already on disk as file +DG_FRA/rac/1_1092_628844420.dbf archive log thread 1 sequence 1093 is already on disk as file +DG_FRA/rac/1_1093_628844420.dbf archive log thread 1 sequence 1094 is already on disk as file +DG_FRA/rac/1_1094_628844420.dbf archive log thread 1 sequence 1095 is already on disk as file +DG_FRA/rac/1_1095_628844420.
Session 7: Restore and Recovery using an incremental backup RMAN> run { 2> allocate channel 'dev_0' type 'sbt_tape' 3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=RAC,OB2BARLIST=RAC_POOL_man_ch_1_2 )' connect *; 4> allocate channel 'dev_1' type 'sbt_tape' 5> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=RAC,OB2BARLIST=RAC_POOL_man_ch_1_2 )' connect *; 6> SQL " alter tablespace POOL offline immediate"; 7> restore tablespace 'POOL'; 8> recover tablespace 'POOL'; 9> SQL " alter tablespace POOL online"; 10> relea
restoring datafile 00072 to +DG_DB/rac/datafile/tbs_pool_041.dbf restoring datafile 00074 to +DG_DB/rac/datafile/tbs_pool_033.dbf channel dev_0: reading from backup piece RAC_POOL_man_ch_1_2.dbf channel dev_1: starting datafile backupset restore channel dev_1: specifying datafile(s) to restore from backup set restoring datafile 00009 to +DG_DB/rac/datafile/tbs_pool_001.dbf restoring datafile 00011 to +DG_DB/rac/datafile/tbs_pool_065.
destination for restore of datafile 00039: +DG_DB/rac/datafile/tbs_pool_010.dbf destination for restore of datafile 00041: +DG_DB/rac/datafile/tbs_pool_013.dbf destination for restore of datafile 00043: +DG_DB/rac/datafile/tbs_pool_025.dbf destination for restore of datafile 00045: +DG_DB/rac/datafile/tbs_pool_027.dbf destination for restore of datafile 00047: +DG_DB/rac/datafile/tbs_pool_022.dbf destination for restore of datafile 00049: +DG_DB/rac/datafile/tbs_pool_023.
Finished recover at 2007-11-07 sql statement: alter tablespace POOL online released channel: dev_0 released channel: dev_1 Recovery Manager complete.
For more information • HP Data Protector Software http://www.hp.com/go/dataprotector © 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
