Oracle 10g R2 Data Guard. Neue Funktionalitäten

Transcription

1

2 Oracle 10g R2 Data Guard Neue Funktionalitäten

3 Claudia Hüffer Principal Sales Consultant Server Technologies Competence Center Nord ORACLE Deutschland GmbH

4 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

5 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

6 Einleitung einige Begriffe HA = high availability = bringing a system up after a failure DR = disaster recovery = prevent data loss HA DR Data Guard (vor allem physical standby) ist für DR, d.h. schützt die Daten gegen Verlust. Data Guard Funktionalitäten wie Switchover,... für HA Szenarien sind Bonus.

7 Disaster-Recovery Why? Whether by human error, hardware failure, electrical disruptions, or natural disaster, system failures simply WILL happen. The most effective way to lessen the impact and recover from them quickly is careful preparation--done today--so your recovery plan is in place when you'll need it. DON'T BE CAUGHT UNPREPARED

8 Data Guard Überblick Ausfallgründe Ungeplante Ausfallzeit Systemfehler Datenfehler & Desaster Applikations / Menschliche Fehler Stromausfall Failover zur Standby-DB Systemabsturz Datenkorruption 100% Datenschutz Flut, Feuer, usw. Löschen Delay beim von Log-Apply Flashback Tabellen Database (System-)Tabellen Geplante Ausfallzeit Routine Operationen System Wartung Produktiv-DB entlasten Aufgabenübernahmebernahme Schema-Anpassungen Backup, Reporting Hardware & Graceful Switchover O/S Upgrades

9 Data Guard Überblick Was ist Oracle Data Guard? Seit Oracle 9i neuer Name für Standby Datenbank Oracle s Disaster Recovery Lösung für Oracle DBs Feature der Oracle Database Enterprise Edition Automatisiert das Anlegen und den Betrieb einer oder mehrerer transaktionskonsistenter Kopien (Standby- DBs) der Produktiv-Instanz (Primary) Wenn die Produktiv-Instanz ausfällt, kann eine Standby- Datenbank aktiviert werden und die Rolle der Produktiv- Datenbank übernehmen

10 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

11 Architektur

12 Data Guard Architektur Einsatzgebiete? Physical Standby DR-Lösung mit HA-Funktionalitäten Reporting-Option Protection Modes Logical Standby Echt-Zeit-Reporting durch Real Time Apply durch Zusatz-Indizes und MVs gute Performance logische Kopie Vorschlag: Physical Standby für Failover/DR Logical Standby für Reporting, Upgrades, Tests, Entwicklung etc.

13 Data Guard Architektur Data Guard Manager - GUI

14 Data Guard Architektur Data Guard Manager - CLI

15 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

16 Data Guard New Features New Features Common to Redo Apply and SQL Apply New Features Specific to Redo Apply and Physical Standby Databases New Features Specific to SQL Apply and Logical Standby Databases

17 Common DG New Features Fast Start Failover (FSFO) Flashback Database across Data Guard switchovers (larger flashback window) Improvements with LGWR ASYNC Archiver-based redo transport optimizations Data Guard enhancements in Enterprise Manager

18 LGWR ASYNC improvement During asynchronous redo transmission, the network server (LNSn) process transmits redo data out of the online redo log files on the primary database and no longer interacts directly with the logwriter process. This change in behavior allows the logwriter process to write redo data to the current online redo log file and continue processing the next request without waiting for interprocess communication or network I/O to complete.

19 Archiver-based redo transport optimizations Intra-file parallel streaming using new max_connections attribute of log_archive_dest_n parameter More Archiver processes to archive redo logs log_archive_max_processes: max value increased from 10 to 30 Faster transfer of redo generated from batch loads, faster resolution of archive gaps in all protection modes

20 EM: Fine-grained Monitoring

21 Examples of Metrics Through EM Primary Data Guard Status Redo Generation Rate Last Redo Generated Time Standby Remaining Apply Time Lag Time Redo Not Available Redo Apply Rate Last Redo Applied Time Common Fast-Start Failover metrics Historical trend analyses available for various metrics!

22 Physical Standby Database New Features Easy conversion to reporting database (with read/write access) ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE for faster (immediate) failover RMAN automatically re-creates tempfiles after recovery Faster Redo Apply Failover (only, if not been opened read-only after last restart!)

23 Logical Standby Database New features Faster SQL Apply Failover Additional datatype support (IOT mit LOB und overflow) Automatic deletion of applied archived redo logs Optimized creation of logical standby database

24 Supported data/storage types CHAR, NCHAR VARCHAR2, VARCHAR,NVARCHAR2 NUMBER DATE TIMESTAMP,...WITH TIMEZONE,...WITH LOCAL TIMEZONE INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND RAW CLOB, NCLOB, BLOB LONG, LONG RAW BINARY_FLOAT,BINARY_DOUBLE Heap-organized tables (partitioned and nonpartitioned) Index-organized tables (partitioned and nonpartitioned, including overflow segments) Cluster tables (including index clusters and heap clusters)

25 Unsupported data/storage types BFILE ROWID, UROWID User-defined types Collections (including VARRAYS and nested tables) XML type Encrypted columns Multimedia datatypes (including Spatial, Image, and Context) Logical standby databases do not support the segment compression storage type.

26 Automatic Archivelog Deletion in Logical Standby Automatically deletes archivelog files that have been applied Reader process periodically checks if archivelog files available for deletion, and if so, deletes them Metadata updated to reflect the current status Improves space management in logical standby Enable (default): execute dbms_logstdby.apply_set( LOG_AUTO_DELETE, TRUE ); Disable: execute dbms_logstdby.apply_set( LOG_AUTO_DELETE, FALSE ); DBA can query DBA_LOGMNR_PURGED_LOG view to see which logfiles will be deleted automatically in the future

27 Creation of logical standby database (1) Check data and storage type support Create physical standby database Stop recovery SQL> RECOVER MANAGED STANDBY DATABASE CANCEL; Execute dictionary build procedure on primary SQL> EXECUTE DBMS_LOGSTDBY.BUILD; Restart Recovery with additional option: SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY <dbname>; Create new password file

28 Creation of logical standby database (2) Startup mount the standby database SQL> STARTUP MOUNT Adjust log_archive_dest_n parameters Open resetlogs (only once, no dbnid) SQL> ALTER DATABASE OPEN RESETLOGS; Start apply SQL> ALTER DATABASE START LOGICAL STANDBY APPLY; Zero downtime, fewer steps

29 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

30 Fast-Start Failover Bei Ausfall der Primary findet ein automatisches Failover auf eine zuvor bestimmte Standby Datenbank statt erfordert kein manuelles Eingreifen Voraussetzungen sind eine bestehende Broker- Konfiguration, Maximum Availability Protection Mode und eingeschaltete Flashback Database Funktionalität auf beiden Seiten. Falls die alte Primary DB wieder verfügbar ist, nimmt der Broker diese automatisch als standby database in die Konfiguration auf

31

32 Fast Start Failover am Beispiel (1) Setzen des Protection Modes SQL> alter database set standby database to maximize availability; Einschalten flashback database SQL> alter database flashback on; Starten des Broker-Prozesses SQL> alter system set dg_broker_start=true scope=both;

33 Fast Start Failover am Beispiel (2) Definition der Broker-Konfiguration DGMGRL> create configuration airbus_fsfo as > primary database is elcaro02_fsfop > connect identifier is fsfop.world; DGMGRL> add database elcaro03_fsfos as > connect identifier is fsfos.world > maintained as physical ;

34 Fast Start Failover am Beispiel (3) Einstellen LGWR SYNC Transport Mode DGMGRL> edit database elcaro02_fsfop set property LogXptMode='SYNC'; DGMGRL> edit database elcaro03_fsfos set property LogXptMode='SYNC'; Einschalten der Broker-Konfiguration DGMGRL> enable configuration;

35 Fast Start Failover am Beispiel (4) Definition der Failover-Targets DGMGRL> edit database elcaro02_fsfop set property FastStartFailoverTarget='elcaro03_fsfos'; DGMGRL> edit database elcaro03_fsfos set property FastStartFailoverTarget='elcaro02_fsfop'; Starten des Observers DGMGRL> start observer

36 Fast Start Failover am Beispiel (5) Einstellen der Wartezeit DGMGRL> edit configuration set property FastStartFailoverThreshold='45'; Einschalten von Fast Start Failover DGMGRL> enable fast_start failover;

37 Fast Start Failover am Beispiel (6) DGMGRL> show configuration verbose Configuration Name: airbus_fsfo Enabled: YES Protection Mode: MaxAvailability Fast-Start Failover: ENABLED Databases: elcaro02_fsfop - Primary database elcaro03_fsfos - Physical standby database - Fast-Start Failover target Fast-Start Failover Threshold: 45 seconds Observer: elcaro03 Current status for "airbus_fsfo": SUCCESS

38 Fast Start Failover am Beispiel (7) Failover ausgelöst durch Crash der Primary tritt auf (kill 9 <pmon>, Thu May 26 13:39:41 MEST 2005) Observer-Konsole: 13:40:28.24 Thursday, May 26, 2005 Initiating fast-start failover to database "elcaro03_fsfos"... Performing failover NOW, please wait... Failover succeeded, new primary is "elcaro03_fsfos" 13:40:51.22 Thursday, May 26, 2005 ; Automatisches Failover in weniger als 1 Minute!

39 Fast Start Failover am Beispiel (8) Manueller Neustart der alten Primary SQL> startup ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. ORA-16649: database must be opened by Data Guard broker when Fast-Start Failover is enabled

40 Fast Start Failover am Beispiel (9) Broker nimmt alte Primary als standby db auf 13:44:28.54 Thursday, May 26, 2005 Initiating reinstatement for database "elcaro02_fsfop"... Reinstating database "elcaro02_fsfop", please wait... Operation requires shutdown of instance "FSFOP" on database "elcaro02_fsfop" Shutting down instance "FSFOP"... ORA-01109: database not open Database dismounted. ORACLE instance shut down.

41 Fast Start Failover am Beispiel (10) Fortsetzung... Operation requires startup of instance "FSFOP" on database "elcaro02_fsfop" Starting instance "FSFOP"... ORACLE instance started. Database mounted. Continuing to reinstate database "elcaro02_fsfop"... Reinstatement of database "elcaro02_fsfop" succeeded 13:45:43.61 Thursday, May 26, 2005

42 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

43 Physical standby as reporting database (read/write) A physical standby database can be activated as a primary database, opened read/write for reporting purposes, and then flashed back to a point in the past to be easily converted back to a physical standby database. At this point, Data Guard automatically synchronizes the standby database with the primary database. This allows the physical standby database to be utilized for reporting and read/write cloning activities. No logshipping during that time no disaster protection!! Second standby required

44 Physical Standby read/write (1) Definition eines Restore Point SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; SQL> CREATE RESTORE POINT before_read_write GUARANTEE FLASHBACK DATABASE; Letzter Logswitch und Ausschalten vom Logshipping SQL> ALTER SYSTEM ARCHIVE LOG CURRENT; SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER;

45 Physical Standby read/write (2) Aktivieren der Standby Datenbank SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE; SQL> STARTUP MOUNT FORCE; SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE; SQL> ALTER DATABASE OPEN; Durchführen der read/write Operationen für Reporting, Applikations-Tests,...

46 Physical Standby read/write (3) Zurücksetzen der Standby Datenbank SQL> STARTUP MOUNT FORCE; SQL> FLASHBACK DATABASE TO RESTORE POINT before_read_write; SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY; SQL> STARTUP MOUNT FORCE; Starten des REDO-Apply SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;

47 Physical Standby read/write (4) Einschalten des Logshipping SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2=ENABLE; SQL> ALTER SYSTEM ARCHIVE LOG CURRENT; Das entstandene Gap wird automatisch geschlossen.

48 Agenda Data Guard - Überblick Data Guard - Architektur Data Guard Features in Oracle Database 10g Release 2 Allgemein Fast Start Failover Read/Write-Nutzung der Physical Standby Database Zusammenfassung & Q/A

49 Zusammenfassung Data Guard ist DIE Desaster-Recovery Lösung von Oracle Zusätzliche Funktionen tragen zur Entlastung des Produktionssystem bei (Reporting, Backup,...) und erhöhen die Gesamtverfügbarkeit des Systems In 10gR2 weitere Performance-Vebesserungen beim Apply und LogTransport Erweitere Funktionalitäten im GUI Fast Start Failover (FSFO) = automatisches Failover Einfache Umwandlung der physical standby db für Read/write-Aktionen

50 Weiterführende Informationen Oracle Data Guard Produkt-Dokumentation Oracle Technet ( Zahlreiche White-Paper und Best-Practices- Paper Metalink Top Tech Docs Data Guard Tab all articles, find in page index Physical standby database master index page Logical standby database master index page

51 Q U E S T I O N S A N S W E R S

52