Chapter 14: Backing up the Oracle Database Tapies covered in this section. Backup Overview. How often should backups be performed?

Transcription

1 Chapter 14: Backing up the Oracle Database Tapies covered in this section Backup Overview + Planning Database Backup + Causes of System Failure Backup Considerations Types of Backup + Hot Backup + Cold Backup Backup Overview How often should backups be performed? + How much data can you afford to be lose? Why plan backups? + Disaster Recovery Procedures Document it Try it befare you need it + There is also recovery + Media lifespan + Your data is worth more than your hardware..,..., e,....;,...,..".. ~ \,.,..'-JI 11 1 '-...11'-JI 1~ 1

2 Disaster Preparedness Cycle Dcvclop/tcst Disaster Preparedness plan plan Backup Overview What causes systems to fail? + Hardware or Media Failure + Software bugs or design outages + Operations Human error + Environment Temperature, power, tornado, fire, earthquakes, tsunami + Any combination of the abo ve.....,.e,-~.;_..,,.. """ '-'JI 11 1 \-11\.JI 1"" 2

3 What Can Go Wrong o Hardware or System Malfunction Human Error o Software Corruption or Program Malfunction 32% o Computer\flruses 14% Natural Disasters Ontrack Data lnternational lnc. Common Causes For System Failure: 32 /o Human Error! The Administrator's Lament Apologies to the Beatles, and thanks to Geoff Robb.. _,...,... -e,-~.:,....., \,.,.' \,.,.IIV I I..:J 3

4 Backup Overview Database archivelog vs. noarchivelog mode + One of the most important decisions in a Empower environment + Speed vs. protection + By default NoArchivelog mode This is the default mode on Empower Personal workstations. Archivelog mode Enterprise/Workgroup systems running Empower software should always be in ARCHIVELOG mode; which is enabled during installation. You take a slight performance hit but it is well worth it. What to Backup Empower 2 Files + Database files Tablespaces Control Files initialization Para meter file + Transaction Log files (ARC) + DBA Password file + "O-Files" System Files Registry 4

5 Database (.dbf) Files Datafiles: One set for each instance of Empower + \EmpowerDatabase\oradata\WAT6\systemOn.dbf + \EmpowerDatabase\oradata\WAT6\sysaux0n.dbf + \EmpowerDatabase\oradata\WAT6\users0n.dbf + \EmpowerDatabase\oradata\WAT6\undoTBSOn.dbf + \EmpowerDatabase\oradata\WAT6\index0n.dbf Temp Files: + \EmpowerDatabase\oradata\WAT6\tempOn.dbf Transaction Logs Each database has corresponding transaction log files On-line and off-line transaction logs 11 Redo02. Redo03. Redo04. LOG LOG LOG On-line Logs.Are 5

6 Other Files Controlfiles: + \EmpowerDatabase\oradata\WAT6\controlfiles*. * Control01.ctl Control02.ctl Control03.ctl Trace file Other Files: + \EmpowerDatabase\oradata\WAT6\ Server Backup Waters Recommendation for the backup : a daily Hot backup (the database is sti/1 online but in a specific mode) Weekly Co/d backup (the database is shutdown) Scripts are provide for these two operations. + For Cold Backup: 0:\Empower\Script\cs_cold_gen.bat + For Hot Backup: 0:\Empower\Script\cs_hot_gen.bat A complete backup must contain the Oracle part and the Raw data files. 6

7 Exporting and Deleting the Empower Databa se Think on recovery plan and training Example of Timetable for backup: HOTBACKUP OOAM & fj12/2004 6/14/2004 HOTBACKUP HOTBACKUP HOTBACKUP 6l9t'2004 4:00AM &'llf2004 4:00AM &'l l'2004 4:00AM HOTBACKUP HOTBACKUP HOTBACKUP 4:00AM &may ~~ Th~sday -sday) -OOay) Fnday -) ~urnay) Sundayk~~ l 4:00AM! 6/&2004 i Coldbackup / V <'2004 J 6/1(;'2004 lnlefva Oescri~ Week Time Table for Database Backup Backup Overview Basic database safety tips + Do not put the archive lag files on the same physical drive as the database. 110 Single failure point + Do not put the backup on the same physical drive as the database. Single failure point + Keep the control file and its mirrors as well as redo logs and their mirrors on separate physical disks. Single failure point..,...,...,..,.,...e,.-4:,...,...r._,'-'-ji 11 1 \o...i IVI I..:J 7

8 Backup Considerations Befare ya u back up the data base, cansider the fallawing: + Be aware of the different disk space storage requirements for ea eh of the scripts. ls there sufficient room in your destination (or temporary destination) for the backup? + When executing backup scripts, do not use a storagedirectory that contains spaces in its na me. + lf you manually relocate or add any Oracle files (control files, data files, and so on), scripts are dynamically modified to reflect the new locations. Backup Considerations Befare yau back up the database, cansider the fallawing: + lf Empower software is running, and a file is in use, it cannot be backed up. + You can back up raw data (*.dat) files while Empower is running, but if a file is open or in use, it cannot be backed u p. This is one reason to perform periodic cold backups + You can back up the archive lag (*.are) files while Oracle is running 8

9 Backup Considerations Befare you back up the data base, consider the following: + Choose a reliable final destination (e.g., optical media rather than magnetic media) + The backup script batch files included with Empower can be run from either the command (MS-DOS) prompt or by using a scheduling program such as WINAT so that they can be run at regular times. The Dynamic Backup Scripts Backup ScriptDescription cs_hot_gen.bat Backs up database files, archive log files, and raw data toa drive - Allows the database to be running - Requires the most disk space cs_cold_gen.bat Backs up database and raw data toa drive - Requires that the data base be shut down 9

10 Hot Backups Hot backups are backups of the Oracle database while the database is live. + lt is a snapshot in time. Warm backups are technically hot backups but they are performed at times of (relatively) little activity. + Waters recommends warm backups. Script usage for Empower 2 Hot Backup %1 Backup Location %2 Oracle dba account name %3 Password for dba account %4 Oracle Home %5 Oracle SID %6 Omit Raw Data g:\backup SYS ORACLE d:\empower\oracle\oracle1 Og WAT6 YES //Optional - Leave blank There should be no spaces in any of the parameters. cs_hot_gen J \ Jr sys oracle d:\empower\oracle\oracle10g WAT6....,..._.._e.-+:,..._... / 'A' '-'' "' '-"'-'''"' vva.ers 10

11 Hot Backup Methodology Step 1 : ldentifies parameters %1 %2 %3 %4 %5 %6 Step 2: Assigns the directory destination Step 3: Creates scripts Step 4: Run scripts + EmpowerHBU.sql- Creates EmpowerHBU.bat file dynamically + ArcDir.sql - Creates ArcDir.bat file + Arc.sql - Creates Copy_Arc.bat file + Copy_DF.sql- Creates Copy_DF.bat file + StoreDumpDest.sql- Creates OldDumpDest.sql to store old user_dump_dest + Copies spfile%5.ora + Spfilepfile.sql - Creates a pfile from the binary spfile + Copies pwd%5.ora + Beginbackup.sql - Set tablespaces into backup mode. Alter database begin backup; This stops the System Change Number (SCN) updates to the datafiles. Hot Backup Methodology + EmpowerHBU.bat- Copy database files to backup directory Tablespaces are copied using OCOPY which allows the copying of open files. + NewDumpDest.sql - Sets new user_dump_dest to backup directory + DumpControl.sql- Copies latest control file to trace + OldDumpDest.sql- Sets old user_dump_dest to original directory + ArcDir.bat - Creates the archive directories in the backup directory + Copy_Arc.bat - Backs up archive logs, this is done before the datafiles are copied. Alter system switch logfile. M ove all archive log files numbered between the first and last number from each archive directory to the backup drive. + EndBackup.sql - Set tablespaces into normal mode Alter database end backup. This allow SCN changes which have been in redo to be posted to the datafiles + Copy_Arc.bat - Backs up archive logs, this is done after the datafiles are copied. Step 5: Copy_DF.bat- Copies raw datafiles from projects as 11

12 Add-ons to script: run_hot.bat + To indicate the date and time the script starts to deploy as scheduled: Set startbckup= Backup Start %data% %time% + To start the script with corresponding parameters and spool comments to a log: Call d:\empower\script\cs_hot_gen.bat G:\backup sys oracle D:\empower\oracle\oracle10g WAT6 YES»g:\hotbackup.log + To indicate at the end of the script the date and time the script had started and writing it to the end of the log %startbckup% >>g:\hotbackup.log + To indicate at the end of the script the date and time the script had ended and writing it to the end of the log Backup Finished %date% %time% >>g:\hotbackup.log Note: This script is avai/ab/e in the CD provided. Cold Backups All users should log out of Empower befare a cold backup to avoid potential performance issues. The data base is closed. The files are copied directly to the tape or drive and the archive logs are deleted. The data base is restarted..,_,...""""'e,....;,..."",.....,..._'-jiiii '-11~11W 12

13 How are clients and LAC/E32 modules affected? lf the Empower server data base is shut down + Clients will not be able to access their data/results + LAC/E 32 will not be able to upload their data During cold backups, all of the OS services that support Oracle are shut down first putting the LAC/E32 Acquisition Server into a recheck mode The LAC/E32 Acquisition Server checks every 1 O minutes until the Empower server returns. Script usage for Empower 2 Cold Backup %1 Backup Location %2 Oracle dba account name %3 Password for dba account %4 %5 %6 Oracle Home Oracle SID Omit Raw Data g:\backup SYS ORACLE d :\Empower\Oracle\Oracle1 Og WAT6 YES //Optional- Leave blank There should be no spaces in any of the parameters. cs_cold_gen g \b e up sys oracle d:\empower\oracle\oracle10g WAT6.,...,...,,..._,...,.... r"\r- #J._.._,,... e._,.._,,,_,. / Waters 13

14 Cold Backup Methodology Step 1: ldentifies parameters %1 %2 %3 %4 %5 %6 Step 2: Assigns the directory destination Step 3: Creates scripts Step 4: Run scripts + DBVerify.sql - Creates script to build DBVerify.bat + EmpowerCBU.sql - Creates EmpowerCBU.bat file dynamically + ArcDir.sql- Creates ArcDir.bat file which creates list of directories for each active archive log destination (1-1 O) + Arc.sql- Creates Copy_Arc.bat file + Copy_DF.sql- Creates Copy_DF.bat file + StoreDumpDest.sql- Creates OldDumpDest.sql to store old user_dump_dest + NewDumpDest.sql - Sets new user_dump_dest to backup directory + DumpControl.sql- Copies latest control file to trace + OldDumpDest.sql - Sets old user_dump_dest to original directory + Shutdown.sql - Performs a Shutdown lmmediate on the database Cold Backup Methodology + DBVerify.bat- Runs database verification (cold logical database block analysis) of database and control files + Copies spfile%5.ora + Spfilepfile.sql - Creates a pfile from the binary spfile + Copies pwd%5.ora + EmpowerHBU.bat- Copy database files to backup directory Tablespaces are copied using COPY which allows the copying of closed files. + ArcDir.bat- Creates the archive directories in the backup directory + Arc.bat- Backs up archive logs, this is done befare the datafiles are copied. Move all archive lag files numbered between the first and last number from each archive directory to the backup drive. Step 5: Copy_DF.bat- Copies raw datafiles from projects as specified in the Empower Database Step 6: Startup.sql - Restarts the database.. ~,..."'""'e,-.a.:,......,u......_viiii '--11VI I...:J Waters 14

15 Add-ons to script: run_cold.bat + To indicate the date and time the script starts to deploy as scheduled: Set startbckup= Backup Start %data% %time% + To start the script with corresponding parameters and spool comments toa log: Call d:\empower\script\cs_cold_gen.bat G:\backup sys oracle D:\empower\oracle\oracle1 Og WAT6 YES»g:\coldbackup.log + To indicate at the end of the script the date and time the script had started and writing it to the end of the log %startbckup% >>g:\coldbackup.log + To indicate at the end of the script the date and time the script had ended and writing it to the end of the log Backup Finished %date% %time% >>g:\coldbackup.log Note: This script is avai/able in the CD provided. Recommendations Develop a regular schedule of backups. + lf yo u include cold backups as part of your backup strategy, ensure that your users are aware that the database connection will be lost and any devices currently acquiring data will go into buffering mode. Test your capability to recover using your backups befare it is necessary. 15

16