1 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

Transcription

1 1 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

2 Recovery Manager (RMAN): Not Just for Backups Anymore Steven Wertheimer, Oracle, Senior Director Jeff Branan, TDS Telecom, Database Architect 2 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Presenting with

3 Program Agenda MAA / RMAN Overview RMAN: Beyond Backups Data Block Integrity Checking Database Duplication Cross-Platform Transport Storage Migration Upgrade 3 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

4 Focusing on Oracle Data Protection RMAN + Secure Backup + Flashback + Data Guard Integrated backup & recovery, continuous data protection, disaster recovery Primary Database Data Guard Redo Shipping Active Standby Database RMAN, Flashback RMAN, Flashback Oracle Secure Backup Tape Drive Database Area Fast Recovery Area (Flashback logs Archived logs) Database Area Fast Recovery Area (Backups, Flashback logs Archived logs) 4 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

5 Oracle Recovery Manager (RMAN) Essential for Oracle Backup and Recovery Database Oracle Enterprise Manager RMAN Fast Recovery Area Oracle Secure Backup* Tape Drive Cloud Intrinsic knowledge of database file formats and recovery procedures Block validation Online block-level recovery Tablespace/data file recovery Online, multi-streamed backup Unused block compression Native encryption Integrated disk, tape & cloud backup leveraging the Fast Recovery Area (FRA) and Oracle Secure Backup *RMAN also supports leading 3 rd party media managers 5 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

6 Data Block Integrity Checking RMAN Integrated Capability What is integrity checking? Physical checking Detects fractured blocks and block checksum failures Works best when DB_BLOCK_CHECKSUM = TRUE Logical checking Detects blocks that are physically correct but logically inconsistent Index row out of place Missing row piece many more Why is integrity it checking important? t? Proactively detect database corruption Have confidence that your database is healthy With very little extra cost on top of your daily backups 6 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

7 Data Block Integrity Checking When is integrity checking performed? Physical checking is enabled by default during all RMAN data processing operations. Logical checking is done on request with BACKUP CHECK LOGICAL option. More expensive, so not done by default Standalone checking BACKUP VALIDATE RESTORE VALIDATE VALIDATE <object> DATABASE DATAFILE ARCHIVELOG RECOVERY AREA many more 7 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

8 Data Block Integrity Checking How do you view corrupt block information? V$DATABASE_BLOCK_CORRUPTIONBLOCK CORRUPTION Contains information about every corrupt block in the database. Can be used to drive Block Media Recovery. V$BACKUP_CORRUPTION, CORRUPTION V$COPY_CORRUPTION CORRUPTION Contain information about corrupt blocks in RMAN backups. 8 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

9 Data Block Integrity Checking Repairing Corrupt Blocks Block Media Recovery RMAN RECOVER BLOCK command Automatic Block Repair Corrupt blocks in the primary database are automatically repaired from the physical standby database, as soon as they are detected. Also repairs physical standby blocks from the primary. No setup needed. In-line and transparent User s query halts for a moment while the block is being repaired. User never sees a corrupt block message. Requires Active Data Guard Physical standby must be open read-only Very fast no redo-based recovery needed 9 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

10 Database Duplication For Migration to Same Platform Copies a whole database to a new machine or location Fully automated Generally cannot be used across platforms Exceptions are listed in support note Serves a wide variety of DBA tasks DB/Application upgrade testing Create standby DB Migration Reporting Backup/Recovery integrity testing 10 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

11 Backup-based Duplication Production DB Clone DB Backup Restore Restores existing backups to create new database Can use any kind of RMAN backup Flexibility of using disk or tape Save bandwidth and space by using compression Gain security by using encryption Clone can be created at any point in time Clone can be the entire production DB, or just a subset Duplicating to a temporary system is a great way to test backup integrity. 11 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

12 Backup-based Duplication Scenarios: Duplication Using Already-Existing Backups Prerequisites Auxiliary instance can access existing backups and archived logs RMAN can access recovery catalog Steps 1. Establish auxiliary instance 2. Start RMAN, connect to recovery catalog and auxiliary instance 3. Run command: DUPLICATE DATABASE prod TO dupdb SPFILE NOFILENAMECHECK; 12 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

13 Backup-based Duplication Scenarios: Duplication to an Isolated Location Useful when new system has no access to existing backups or recovery catalog Steps 1. Place all backups and logs in a single directory Datafile, archivelog, and controlfile backups Any kind of backups image copies or backup sets 2. Establish auxiliary instance 3. Start RMAN, connect only to auxiliary instance 4. Run command: DUPLICATE DATABASE prod TO dupdb BACKUP LOCATION /backup/directory SPFILE NOFILENAMECHECK; 13 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

14 Active Duplication Production DB Clone DB Oracle Net Copies directly from the production database Does not require any pre-existing existing backups No intermediate storage needed, even for ASM transfers Copy contains most current data 14 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

15 Active Duplication Production DB Physical Standby Clone DB Can also perform Active Duplicate directly from physical standby database, to offload DB cloning work 15 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

16 Active Duplication Scenarios Prerequisites Oracle Net connection between target and auxiliary database Identical SYS password at both target and auxiliary database Steps 1. Establish auxiliary instance 2. Start RMAN, connect to target, catalog, and auxiliary instance Target instance is your production / standby database Auxiliary instance is the new clone DB 3. Run command: DUPLICATE DATABASE prod TO dupdb FROM ACTIVE DATABASE SPFILE NOFILENAMECHECK; 16 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

17

18 Building and Maintaining Non-Production Databases using Oracle Recovery Manager Presented By: Jeff Branan - Database Architect

19 Agenda Who is TDS? Why we use Recovery Manager (RMAN) TDS Non-Production Database Refresh Process Future Plans Questions

20 More than million lines in service nationwide id TDS i th 7 th l t t l id i U S TDS is the 7 th largest telecom provider in U.S. Connects business and residential customers with phone, Internet and TV services in 30 states.

21 Production Oracle Database Infrastructure 2 High performance Database Machine quarter racks Went live January TDS designed d 11g RAC until 2014 Supports primary 10g databases Will be replaced by high performance quarter rack 1 Standalone Linux server Used for databases that don t support RAC 3-node Solaris non-rac cluster Used for application that required non-rac clustering Databases are Data Guarded between RACs 10g Standby s run on Database Machine 8 TB of data 66 Databases

22 Non-Production Oracle Database Infrastructure Non-Production 1 High capacity Database Machine quarter rack 1 TDS designed 11g RAC in until 2014 Will be replaced by high capacity quarter rack 1 Standalone Linux server Used for databases that don t support RAC 3-node Solaris(VERITAS) non-rac cluster Used for application that required VERITAS clustering 21 TB of data We average, 3 TB of data refreshed from production each week 130 Databases

23 Why we use Recovery Manger Minimizes Production Risk for Refresh Process Using our process, DBAs are unable to reverse the direction of the refresh If process is not properly followed, Oracle RMAN returns an error when you try to connect to the production database as auxiliary No Additional Load on Production for Refresh Process Executed on non-production hardware Uses nightly production backups to disk Integrated with Automatic Storage Management (ASM) Provides Verification of our Backups

24 TDS Refresh Process New Non-Production Database 1. Use documented process to create database using dbca 2. Follow process for refreshing existing non-production database Refresh Existing Non-Production Database 1. Prepare database for refresh 2. Refresh the database 3. Post refresh tasks

25 TDS Refresh Process Prepare Non-Production Database for Refresh 1. Save the SQL to recreate all database links 2. Save any other objects that are required 3. Verify that Fast Recovery Area is large enough 4. Verify init.ora settings for your environment For example db_file_name_convert should not be set log_file_name_convert should not be set 5. Set cluster_database to false 6. Stop database 7. Use asmcmd to remove old data files 8. Start database in no mount mode

26 TDS Refresh Process Refresh Non-Production Database 1. Setup environment for database being refreshed 2. Run RMAN on non-production database server 3. Connect to production database connect target 4. Connect to the non-production database (DevDB) DB) connect auxiliary / 5. Connect to the RMAN catalog connect catalog rman/rman@catdb 6. Refresh the database duplicate target database to DevDB until time <Current Time - 4 hours>

27 TDS Refresh Process Post Refresh Tasks 1. Set cluster_database to true 2. Reset all passwords to non-production values 3. Use saved SQL to recreate all database links 4. Use saved objects to recreate all required objects 5. Execute data masking scripts

28 TDS Refresh Process How long does it take 1 hour of DBA time per refresh 4 hours elapsed for 750 GB database Currently network bandwidth to the NAS, where the backups are stored, is the bottleneck

29 Future Plans Automate Refresh Process using Grid Control Job Reduce DBA time required for a refresh Implement the Oracle Grid Control Data Masking Pack Improve the manageability of the data masking process Move backup location to InfiniBand connected NAS Reduce the elapsed time for a refresh

30

31 Cross-Platform Transport For Migration to Different Platform Copy databases or tablespaces to a different platform Not as fully automated as DUPLICATE Requires a read-only copy of the data Cannot choose any point in time Same-endian endian transport Database or tablespace transport Cross-endian transport Tablespace transport only Conversion work can be done on source or destination database Destination is preferred to offload work from production 31 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

32 Cross-Platform Transport Supported Platforms V$TRANSPORTABLE_PLATFORMPLATFORM Big-Endian Platforms AIX-Based Systems (64-bit) Apple Mac OS HP-UX (64-bit) HP-UX IA (64-bit) IBM Power Based Linux IBM zseries Based Linux Solaris[tm] OE (32-bit) Solaris[tm] OE (64-bit) Little-Endian Platforms Apple Mac OS (x86-64) HP IA Open VMS HP Open VMS HP Tru64 UNIX Linux IA (32-bit) Linux IA (64-bit) Linux x86 64-bit Microsoft Windows IA (32-bit) Microsoft Windows IA (64-bit) Microsoft Windows x86 64-bit Solaris Operating System (x86) Solaris Operating System (x86-64) 64) 32 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

33 Cross-Platform Transport Scenarios: Transport Entire Database For moving to a system with same endian-ness Database must be open read-only before beginning Steps 1. Start RMAN, connect to target database and recovery catalog 2. Run command: CONVERT DATABASE or CONVERT DATABASE ON TARGET PLATFORM 33 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

34 Cross-Platform Transport Scenarios: Transport Individual Tablespaces For moving to a system with same or different endian-ness Transportable Tablespace restrictions apply Tablespace(s) must be self-contained Cannot transport SYSTEM tablespaces or SYS-owned objects Tbl Tablespace(s) () must tbe made read only bf before the transportt see documentation for complete list 34 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

35 Cross-Platform Transport Transportable Tablespace Review Copy Tablespace data2 to new system Source Database system Export Meta Data Destination Database Import system data1 data2 Read-only CONVERT TABLESPACE Data data2 CONVERT DATAFILE 35 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

36 Cross-Platform Transport Scenarios: Transport Tablespace Using Existing Backups Creates a transportable set without affecting production availability Uses same technology as RMAN automated TSPITR Steps 1. Start t RMAN, connect to target t database and recovery catalog 2. Run command: TRANSPORT TABLESPACE 36 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

37 Storage Migration Low-Downtime Storage Upgrades Best Method Best way is to set up a physical standby then switch over Use DUPLICATE FOR STANDBY to instantiate the standby Down time is restricted to the switchover time Alternate t Method 1. Create image-copy backup on new storage 2. Perform incremental refresh, repeating as necessary 3. SWITCH DATABASE TO COPY 4. Recover and open database Down time is restricted to steps Copyright 2011, Oracle and/or its affiliates. All rights reserved.

38 Upgrade Use RESTORE or DUPLICATE to help with Oracle Version Upgrade RMAN can always restore from prior version backups. Restoring old backups does not automatically upgrade them. Upgrade procedures must still be followed. Ordinary backup strategy may be continued after upgrade. For databases that use archive logging. Special pre- or post-upgrade backup is not needed. If pre-upgrade backups are restored, media recovery will re-apply the upgrade. 38 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

39 Summary RMAN has extensive capabilities that go beyond everyday backups. Every feature we ve shown works seamlessly with Oracle s storage and MAA technologies. Data Block Integrity Checking Database Duplication Cross-Platform Transport Storage Migration Upgrade 39 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

40 Resources OTN HA Portal: Maximum Availability Architecture (MAA): MAA Blogs: com/maa Exadata on OTN: Oracle HA Customer Success Stories on OTN: html 40 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

41 Key HA Sessions, Demos, Labs by Oracle Development Monday, 3 Oct Moscone South * Wednesday, 5 Oct Moscone South * 11:00a Auto Detect, Prevent and Repair Data Corruptions, Rm :15a Oracle Active Data Guard - Lessons Learned, Rm :30p Future of Oracle Exadata, Rm 104 1:15p Data Guard for Planned Maintenance, Rm :30p RMAN: Not Just for Backups Anymore, Rm 304 1:15p Understanding Oracle RAC Internals, Rm 103 2:00p Extreme Data Management, Moscone North Hall D 1:15p Clone Oracle with CloneDB and Direct NFS, Rm :00p Oracle High-Availability il System Overview, Rm 104 5:00p GoldenGate Product Update and Strategy, Intercontinental-Sutter Thursday, 6 Oct Moscone South * Tuesday, 4 Oct Moscone South * 10:15a Oracle Secure Backup - Best practices, Rm :45a Oracle Exadata Technical Deep Dive, Rm 104 3:30p RMAN & Data Guard: Seven Cool Tips from Oracle, Rm 304 3:30p Consolidation on Oracle Exadata, Rm 103 9:00a Exadata Backup and Recovery, Rm :30a Deduplication and Compression for Backups, Rm :00p Data Guard Switchover / Failover, Rm 103 3:00p Configure, Size, Monitor Fast Recovery Area, Rm 304 3:00p PeopleSoft with Active Data Guard, Moscone West 2022 Demos Moscone South DEMOGrounds Hands-on Labs Marriott Marquis, Salon 14 / 15 Mon 10:00a - 5:30p Tue 9:45a - 6:00p Wed 9:45a - 4:00p Monday, Oct 3, 5:00 pm - 6:00 pm Oracle Active Data Guard Maximum Availability Architecture (MAA) Exadata Tuesday, Oct 4, 10:15 am - 11:15 am Oracle Active Data Guard Active Data Guard Oracle Secure Backup Recovery Manager & Flashback GoldenGate *All session rooms at Moscone South unless otherwise noted Real Application Clusters ASM *After Oracle OpenWorld, ref Copyright 2011, Oracle and/or its affiliates. All rights reserved.

42 42 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Q&A

43 43 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

44 44 Copyright 2011, Oracle and/or its affiliates. All rights reserved.