Disaster Recovery for OracleWhite Paper: Oracle Database AdministrationFebruary 2012
Disaster Recovery for OracleFebruary 2012TABLE OF CONTENTSINTRODUCTION . 3RESTORING THE HARDWARE AND OPERATING SYSTEM . 4INSTALLING THE DATABASE AND SAP SOFTWARE . 4CREATING THE FILE SYSTEMS . 4I. DISASTER RECOVERY WITH BRRECOVER . 5Disaster Recovery Phases with BRRECOVER . 5Performing Disaster Recovery with BRRECOVER . 6II. DISASTER RECOVERY WITH BRRESTORE . 9Restoring the init DBSID .sap File from Tape . 9Restoring Other Profile and Log Files from Tape . 9Using an External Backup Program . 10Resetting the Database to the Last Backup . 11Recovery Procedure . 12ADDITIONAL INFORMATION . 13SAP Library . 13SAP Notes . 132
Disaster Recovery for OracleFebruary 2012INTRODUCTIONIf you lose your entire system (possibly including hardware) and you have not taken any special precautionsagainst this (for example, an Oracle standby configuration), you must restore the system step-by-step. Thisdocument describes how to reinstall your system and how to keep data loss to a minimum by using the SAPtools BRRECOVER and BRRESTORE.You can automatically perform the most important disaster recovery steps, especially therestore of profiles and log files, with BRRECOVER. We strongly recommend you to useBRRECOVER for disaster recovery.The procedures described here explain the interconnections. Only use these procedures in anexceptional situation if definitely required, otherwise you can destroy an existing database.Note the following:Environment variablesOracle SQLPLUS toolProfile file directoryUNIX ORACLE HOME SAPDATA HOMEsqlplus ORACLE HOME/dbsWindows%ORACLE HOME%%SAPDATA HOME%sqlplus%ORACLE HOME%\databaseThe default values for these variables are as follows:UNIX ORACLE HOME /oracle/ DBSID / DB VERS SAPDATA HOME /oracle/ DBSID Windows%ORACLE HOME% x :\oracle\ DBSID \ DB VERS %SAPDATA HOME% y :\oracle\ DBSID Windows: If the SAPARCH, SAPBACKUP, or SAPREORG directories are not located under%SAPDATA HOME%, use the corresponding environment variables %SAPARCH%, %SAPBACKUP%or %SAPREORG%. The separator character used in UNIX “/” must be replaced with “\” forWindows.3
Disaster Recovery for OracleFebruary 2012RESTORING THE HARDWARE AND OPERATING SYSTEMInstall the same version of the operating system you were using before the loss. When replacing the harddisks, make sure the replacement disks can be used to recreate the original structure and size of your diskpartitions. Format the replacement disks according to the procedure described in the SAP installation guide.Keep the reserved memory for the superuser (root) to a minimum as recommended in the installationguide.INSTALLING THE DATABASE AND SAP SOFTWAREThe installation of the SAP software includes the software installation of the database. The initial SAPdatabase should be completely new. However, do not load any data into the empty SAP tables. Alternatively,restore a full backup of your operating system or use the SAP installation CD.CREATING THE FILE SYSTEMSIt is important to take into account the file systems that were mounted at the time of the loss. If necessary,create new SAPDATA directories (mount points). These are usually used to define a disk or logical storagearea (logical volume). Place the tape from the last successful complete BRBACKUP tape into the tape drive.4
Disaster Recovery for OracleFebruary 2012I. DISASTER RECOVERY WITH BRRECOVERWe recommend you to perform disaster recovery with BRRECOVER if possible.If you lose your entire Oracle database system (possibly including hardware) and you have not taken anyspecial security precautions - such as setting up a Standby Database - then you have to recover the systemas much as possible, step by step. This section describes how to begin reinstalling the system in the event ofsuch a disaster, and how to keep data loss to a minimum by using BRRECOVER.You can only restore profiles and log files using this function. This is a preparation step for subsequentdatabase recovery with one of the following: Database point-in-time recovery Whole database resetBefore you start disaster recovery, make sure that: SAP and Oracle software is correctly installed The file systems – that is, sapdata x directories – exist and are configured as before the disaster.Disaster Recovery Phases with BRRECOVERThe following figure shows how disaster recovery works:SelectrestorefromBRBACKUPor edprofilesandlog illogsBRRECOVERProfile and log directoriesDisaster recovery consists of these phases:1. Select restore from BRBACKUP or BRARCHIVE backup.You select the BRBACKUP or BRARCHIVE backup that contains the required profiles and logs.2. Select restore device type phaseYou select the device to be used from the following possibilities: Local tape Remote tape Local disk Remote disk Backup utility5
Disaster Recovery for OracleFebruary 20123. Specify restore parameters phaseDepending on your choice of restore device type, you specify appropriate restore parameters.4. Select profiles and log files phaseYou select the profiles and log files that you want to restore from the following: BR*Tools profile Oracle profile BACKINT utility profile – util par file Detail log from one of the following:o BRARCHIVE detail Logo BRBACKUP detail Log Summary log from one of the followingo BRARCHIVE summary Logo BRBACKUP summary Logo BRSPACE summary Logo BRSPACE structure Change Logo BRSPACE parameter Change Log Control file from a BRARCHIVE backup Oracle wallet fileThe control file must only be reloaded here when the offline redo log files were saved withRMAN after the last run of BRBACKUP was started.5. Restore selected profiles and log files phaseBRRECOVER directly restores the selected profiles and log files without calling BRRESTORE.6. Select detail logs for restore phaseYou select the detail logs that you want to restore. You can only select logs on the selected restoredevice type, such as a disk or external backup tool (BACKINT). For tape device type, the details logs aredetermined by the mounted tape volume.7. Restore selected detail logs phaseBRRECOVER directly restores the selected detail logs from the disk, tape, or external backup tool withoutcalling BRRESTORE.Performing Disaster Recovery with BRRECOVERYou can use BR*Tools for Oracle to recover from a disaster. You use BRRECOVER to restore missing ordamaged profiles and log files. BRRESTORE is not called by disaster recovery, because it might require theBRBACKUP logs or the BRARCHIVE logs, which might not be available in a disaster.You use this process if either of the following is true: You have lost the entire database, including the profiles and the BRBACKUP logs or the BRARCHIVElogs. You have only lost the profiles and the BRBACKUP or BRARCHIVE logs.This process does not actually restore data files or recover redo log files. It only restores the profiles andBRBACKUP or BRARCHIVE logs from copies that you made during previous backups. Therefore, itprepares the database for you to perform one of the following guided BR*Tools options: Database point-in-time (PIT) recovery Whole database reset6
Disaster Recovery for OracleFebruary 2012Complete database recovery and tablespace PIT recovery are not possible after disaster recovery becausethe current control file (required for complete database recovery) is missing and the database cannot beopened (required for tablespace PIT recovery).Only perform this process if you are an expert in Oracle database administration. Even as anexpert, we recommend that you first try other types of recovery supported by BR*Tools.If you are not an expert, you might severely damage the database with this procedure. Youmight lose data and cause downtime to fix the problem.Prerequisites Since this function is designed for experts, the usual safeguards are not present: There is no database status check. You have less guidance than otherwise, since BRRECOVER cannot offer you default choices in allsituations. You can choose individual actions independently. For all procedures, the backup medium with the required backup files must obviously be present. You need to know exactly which file to restore and where it is. You are effectively performing a copy atoperating-system level. BRRECOVER restores the profiles and logs to the standard directory. If you choose device type Backup utility for the restore, note the following: The BACKINT repository with the latest backup must be available because the tapes are administeredusing this repository in the backup utility. The BACKINT parameter file must normally exist, depending on the specific implementation that youare using. If it is required but is unavailable, you must first try and recreate it before performingdisaster recovery. BRRECOVER calls BACKINT to perform the restore. BACKINT performs the restore of the profiles or logs from the latest backup.Process1. You start BRGUI or BRTOOLS.2. You choose Restore and recovery Disaster recovery.3. You choose the required procedure: Restore profiles and logs files from BRBACKUP backup Restore profiles and logs files from BRARCHIVE backupBRRECOVER starts the restore and displays the menu Device Type.4. You choose the device tape where the backups of the profiles or logs are stored.BRRECOVER displays the parameters for restoring the profiles or logs, depending on what kind of devicetype you specified. The default parameters are taken from the current profile, initialization profileinit DBSID .sap, if available.5. For a disk backup or a utility backup, you note the following:For a disk backup, you can specify the backup directory. BRRECOVER looks in the sub-directory DBSID of the specified directory to find the summary log for BRBACKUP or BRARCHIVE. It uses theinformation there for the restore.For a utility backup, check Prerequisites above.6. You choose Continue to continue the restore with the displayed parameters.BRRECOVER warns you that the profiles and logs might be overwritten.7
Disaster Recovery for OracleFebruary 2012BRRECOVER displays the restore menu where you can specify which profiles and logs to restore: If a log or profile already exists on disk, the recommendation is No to avoid overwriting it. If a log or profile does not exist on disk, the recommendation is Yes to let you restore it.7. If required, you change the recommended values for restoring the profiles and logs. You can selectseveral profiles or logs to restore.8. You choose Continue to start restoring the selected profiles or logs.9. You check the results in the BRRECOVER logs: The summary log recov DBSID .log displays the return code. The detail log v encoded timestamp .drv displays the progress.8
Disaster Recovery for OracleFebruary 2012II. DISASTER RECOVERY WITH BRRESTORERestoring the init DBSID .sap File from TapeAt least one valid init DBSID .sap file must exist before you can start BRRESTORE. You can find asample file as follows:/usr/sap/ SID /SYS/exe/run/initSID.sapAdapt this file, for example with respect to the devices and drivers used.For more information, see “Additional Information” [page 13].Check all operating system-dependent parameters and adapt these as required. Configure the same blocksize in the cpio in flags parameter and – if you used the dd command for the backup – thedd in flags parameter as for backups.Then enter the following commands to restore the latest backup of the BR*Tools profile file ORACLE HOME/dbs/init DBSID .sap:OS cd ORACLE HOME/dbsOS brrestore -n init sapAlternatively the init DBSID .sap file can also be read as a third file from a BR*Tools tape using thecpio operating system command:UNIXcd ORACLE HOME/dbsmt -f /dev/ rewindWindowscd %ORACLE HOME%\databasemt -f /dev/ rewindmt -f dev/ fsf 2mt -f /dev/ fsf 2cpio -ivuB /dev/ cpio -ivuB -I /dev/ If you have configured a different block size in the init DBSID .sap parametercpio flags, you must use this same block size when restoring.Restoring Other Profile and Log Files from TapeFirst, restore the files backed up during the last BRBACKUP backup of the database: Profile filesOracle profile file: ORACLE HOME/dbs/init DBSID .oraTo restore the files, enter the following commands:OS cd ORACLE HOME/dbsOS brrestore -n init ora BRSPACE summary and structure log files BRSPACE summary log: SAPDATA HOME/sapreorg/space DBSID .log Structure log: SAPDATA HOME/sapreorg/struc DBSID .logTo restore both log files, enter the following commands:OS cd SAPDATA HOME/sapreorg9
Disaster Recovery for OracleFebruary 2012OS brrestore -n space log BRBACKUP summary log file, SAPDATA HOME/sapbackup/back DBSID .logTo restore the file, enter the following command:OS cd SAPDATA HOME/sapbackupOS brrestore -n sum logThe last entry in the summary log corresponds to the last backup. This is the relevant entry for the detaillog (see next file below). The last entry is usually incomplete – for example, Return Code notcurrent – but this does not affect any subsequent operations. BRBACKUP detail log file, SAPDATA HOME/sapbackup/ coded timestamp . fid OS brrestore -n det logNote the coded timestamp (that is, the filename without extension) and the function ID fid (thatis, the filename extension) from the name of this restored file in the restore directory. These are requiredfor the following steps.Alternatively you can quickly restore all logs from the BRBACKUP tape into the current directoryusing a single BRRESTORE command:brrestore –n all logThen copy the individual logs into the correct directories.Remove the BRBRACKUP tape from the tape drive and replace it with the BRARCHIVE tape of the lastbackup of the offline redo log files.Now restore the BRARCHIVE summary log, SAPDATA HOME/saparch/arch DBSID .log, from theBRARCHIVE tape by entering the following commands:OS OS OS OS cd SAPDATA HOME/saparchbrrestore -n sum logcd SAPDATA HOME/sapreorgbrrestore –n control fileThe last command above, which reloads the control file, is only necessary when the offline redolog files were saved with RMAN after the last run of BRBACKUP was started.If the control file is reloaded, you must copy it to all the original locations defined in the Oracleparameter control files.Remove the BRARCHIVE tape from the tape drive and replace it with the BRBACKUP tape.Using an External Backup ProgramIf you use the BACKINT interface, the procedure is somewhat different. The profiles init DBSID .utl(optional, depending on backup program) and init DBSID .sap must exist before you use BACKINT. Forthe init DBSID .sap profile, you only have to set the backup dev type parameter to util fileand define the profile name of the external backup program in the util par file parameter. You mighthave to reconstruct this profile either by editing or by using the external backup program directly.Then restore the following files one by one: BRBACKUP current summary log: SAPDATA HOME/sapbackup/back DBSID .logOS brrestore -b2 “#NULL” –m SAPDATA HOME/sapbackup/back DBSID .logThe last entry in the summary log corresponds to the last backup. This is the relevant entry for the detaillog (see next file below). The last entry is usually incomplete (for example, Return Code not10
Disaster Recovery for OracleFebruary 2012current), but this does not affect any subsequent operations. Note the coded timestamp (that is,the filename without extension) and the fid (that is, the filename extension) from the name of thisrestored file in the restore directory. These are required for the following steps. BRBACKUP last detail log, SAPDATA HOME/sapbackup/ coded timestamp . fid OS brrestore -b2 “#NULL” -m SAPDATA HOME/sapbackup/ coded timestamp . fid You can restore all other files in the same way with this command:OS brrestore -b2 “#NULL” -m pathname Replace pathname by: ORACLE HOME/dbs/init DBSID .ora ORACLE HOME/dbs/init DBSID .sap ORACLE HOME/dbs/init DBSID .dba ORACLE HOME/dbs/init DBSID .utl SAPDATA HOME/saparch/arch DBSID .log SAPDATA HOME/sapreorg/struct DBSID .log SAPDATA HOME/sapreorg/reorg DBSID .log SAPDATA HOME/sapreorg/cntrl DBSID .dbfThe last item above, for the control file, is only necessary when the offline redo log files weresaved with RMAN after the last run of BRBACKUP was started.If the control file is reloaded, you must copy it to all the original locations defined in the Oracleparameter control files.The procedure described above is complex. Alternatively, you can use the external tool's restore function.Resetting the Database to the Last BackupYou always have to recover an online backup to a point in time after the backup. You can also perform arecovery for an offline backup if you want a more up-to-date status than that of the restored offline backup.Restore control files if not yet restored:OS brrestore -b coded timestamp . fid -m 0Restore online redo log files if an offline backup is used:OS brrestore -b coded timestamp -m 00Mount the database if the backup was done using RMAN:SQL connect / as sysdbaSQL startup mountRestore all database files:OS brrestore -b coded timestamp . fid -m allYou have determined coded timestamp and fid from the summary BRBACKUP log in a previousstep.If you want to perform further recovery, do not open the database at this point. This can happenafter the restore of an offline backup.11
Disaster Recovery for OracleFebruary 2012Recovery ProcedureRemove the BRBRACKUP tape from the tape drive and replace it with the BRARCHIVE tape.Restore the required offline redo log files:OS brrestore -a log seg No A - log seg No B Log Seg No A is the current log sequence number found in the header of the BRBACKUP log. Log Seg No B corresponds to the sequence number of the last offline redo log file backed up(that is, the last entry in the summary BRARCHIVE log: arch DBSID .log).You can perform database recovery using the Oracle SQLPLUS as follows (mount the database only if notyet done):SQL SQL SQL SQL connect / as sysdbaset autorecovery offstartup mountrecover database using backup controlfile until cancelYou must confirm every recovery step with ENTER. After the entire recovery procedure is finished, completethis step with cancel.SQL alter database open resetlogs;12
Disaster Recovery for OracleFebruary 2012ADDITIONAL INFORMATIONSAP LibraryYou can find more information on Oracle database administration and the contents of this document in theSAP Library as follows:All paths refer to SAP NetWeaver 7.3.1. Call up the SAP Help Portal at help.sap.com/nw73 Application Help SAP Library: English.2. Choose SAP NetWeaver Library: Function-Oriented View Database Administration DatabaseAdministration for Oracle SAP Database Guide: Oracle Approach to Oracle DBA Restore andRecovery Disaster Recovery.You can also find this plus selected extracts from the SAP Library at:www.sdn.sap.com/irj/sdn/ora SAP on Oracle Knowledge Center SAP Documentation inHelp PortalSAP NotesYou can find SAP Notes at:service.sap.com/notes13
www.sap.com Copyright 2012 SAP AG. All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components ofother software vendors.Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks ofMicrosoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, Systemz10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,POWER6 , POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV,GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of AdobeSystems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C , World Wide WebConsortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, andXcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerryStorm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registeredtrademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, GoogleMail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAPHANA, and other SAP products and services mentioned herein as well as their respective logos are trademarksor registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects isanSAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.Sybase is an SAP company.Crossgate, m@gic EDDY, B2B 360 , and B2B 360 Services are registered trademarks of Crossgate AG inGermany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disaster Recovery for Oracle February 2012 7 Complete database recovery and tablespace PIT recovery are not possible after disaster recovery because the current control file (required for complete database recovery) is missing and the database cannot be opened
1 Introduction to Oracle Fusion Middleware Disaster Recovery 1.1 Overview of Oracle Fusion Middleware Disaster Recovery 1-1 1.1.1 Problem Description and Common Solutions 1-1 1.1.2 Terminology 1-2 1.2 Setting Up Disaster Recovery for Oracle Fusion Middleware Components 1-5 1.2.1 Oracle Fusion Middleware Disaster Recovery Architecture Overview 1-5
Oracle e-Commerce Gateway, Oracle Business Intelligence System, Oracle Financial Analyzer, Oracle Reports, Oracle Strategic Enterprise Management, Oracle Financials, Oracle Internet Procurement, Oracle Supply Chain, Oracle Call Center, Oracle e-Commerce, Oracle Integration Products & Technologies, Oracle Marketing, Oracle Service,
NetWorker Server disaster recovery roadmap This guide provides an aid to disaster recovery planning an detailed step-by-step disaster recovery instructions. The following figure shows the high-level steps to follow when performing a disaster recovery of the NetWorker Server. Figure 1 Disaster recovery roadmap Bootstrap and indexes
Oracle is a registered trademark and Designer/2000, Developer/2000, Oracle7, Oracle8, Oracle Application Object Library, Oracle Applications, Oracle Alert, Oracle Financials, Oracle Workflow, SQL*Forms, SQL*Plus, SQL*Report, Oracle Data Browser, Oracle Forms, Oracle General Ledger, Oracle Human Resources, Oracle Manufacturing, Oracle Reports,
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
4.2 State Disaster Recovery policy 4.3 County and Municipal Recovery Relationships 4.4 Recovery Plan Description 4.5 Recovery Management Structure and Recovery Operations 4.6 Draft National Disaster recovery Framework (February 5, 2010) 4.6.1 Draft Purpose Statement of the National Disaster Recovery Framework
1. Post-Disaster Recovery and Disaster Risk Reduction require support from community participation in improving the quality and objectives of Disaster Management; 2. Community-based Disaster Risk Reduction is a key factor in participatory disaster management, including in post-disaster recovery, as indicated by best practices in Yogyakarta and .
Araling Panlipunan. Ikalawang Markahan- Modyul 2: Mga Isyu sa Paggawa . II . Paunang Salita Ang Self-Learning Module o SLM na ito ay maingat na inihanda para sa ating mag-aaral sa kanilang pagaaral sa tahanan. Binubuo ito ng iba’t ibang bahagi na gagabay sa - kanila upang maunawaan ang bawat aralin at malinang ang mga kasanayang itinakda ng kurikulum. Ang modyul na ito ay may inilaang Gabay .