Getting Maximum returns on Data Guard Investment...Presented by : Syed Jaffer Hussain AIOUG Sangam 2014 Slide # 1 . Getting Maximum returns on Data Guard Investment

Presented by : Syed Jaffer Hussain AIOUG Sangam 2014 Slide # 1

Getting Maximum returns on Data Guard Investment

Disclaimer


This views/content in this slides are those of the author and do not necessarily reflect that of Oracle Corporation and/or its affiliates/subsidiaries. The material in this document is for informational purposes only and is published with no guarantee or warranty, express or implied.. This material should not be reproduced or used without the authors' written permission.

Agenda


Disaster Recovery– why and when? Data Guard transformation – from its birth Data Guard architecture overview Basic and Advanced configuration Getting maximum returns

Offloading queries - Active Data Guard Short time Application testing - Snapshot standby database Offloading RMAN backups Real-time query capabilities Automatic data block corruption repair Long distance standby with zero data loss - Far Sync


Not a self marketing… A tiny inspiration

Who am I


Over 20 years of IT experience 16+ years as an Oracle DBA Oracle ACE Director Oracle 10g Certified Master(OCM) Oracle 10g RAC Certified Expert OCP v8i,9i,10g & 11g ITIL v3 Foundation Certified Oracle Database 12c beta tester SNC ID: @sjaffarhussain http://jaffardba.blogspot.com

Who am I


Technologist of the Year, DBA 2011

http://www.oracle.com/technetwork/issue-archive/2012/12-jan/o12awards-tech-1403083.html

Who am I


Co-authored …

Who am I


Up coming …

Who am I


Technical Reviewer …

MAA Best Practices


DR Setup

10 Nodes 06 Nodes

10 Nodes 06 Nodes

Same city 50 km away

Production Setup

Disaster Recovery – why and when?


• Floods • Earthquakes • Hurricanes

• Is pre-planned actions that will react to various Disaster scenarios

• A business continuity planning

• Fire • Explosion • Bombing

• Planned/Unplanned extended outages


1. Recovery Time Objective (RTO) 2. Recovery Point Objective (RPO)


Standby Database transformation

Standby (DG) transformation since v7


Oracle 7

• Starts supporting manual standby database

Oracle 8i

• Read-only physical standby db • Managed recovery process

Oracle 9i

• Zero data loss capabilities • Data Guard broker • Role switch (Switchover/Failover) • Automatic Gap resolutions (FAL_CLIENT/SERVER) • Logical standby • Protection (maximum/high availability) • Cascade redo log destinations

Oracle 10g

• Real-time apply • Improved support for RAC • Fast-start Failover • Flashback database across DG switchovers

Oracle 11g

• Active Standby database • Redo compression • BCT on Standby • Real time query capabilities • Heterogeneous platform support • Snapshot database • Integration with RMAN • Supports 30 standby databases • Automatic block recovery

• New role for DG admin • Far sync • Additional sequences on DG • Rolling upgrade using DBMS_ROLLING

Oracle 12c

Data Guard Architecture Overview


Image courtesy Oracle

Configuration – Basic & Advance


• ALTER DATABASE FORCE LOGGING • LOG_ARCHIVE_DEST_n • FAL_SERVER • FAL_CLIENT • LOG_ARCHIVE_CONFIG • DB|LOG_FILE_NAME_CONVERT • STANDBY_FILE_MANAGEMENT

Active Data Guard Overview








Image courtesy : Oracle


Application Testing?

Testing application?


Read-write DG – Snapshot Standby Database


Image courtesy : http://www.dbms-notes.com/2012/03/snapshot-standby-role-transition-cycle.html

Conversion


Physical standby conversion to Snapshot standby

1. Cancel the media recovery • SQL> alter database recover managed standby database cancel;

2. Ensure the physical standby database in MOUNT state, not OPEN • SQL> select open_mode from v$database;

3. Perform the conversion • SQL> ALTER DATABASE CONVERT TO SNAPSHOT DATABASE;

Conversion



Review alert log


Read-write DG – snapshot standby database

Conversion


Snapshot database conversion to Physical standby

1. For RAC database, ensure only one instance is up and running

2. Ensure the physical standby database in MOUNT state, not OPEN • SQL> select open_mode from v$database;

3. Perform the conversion • SQL> ALTER DATABASE CONVERT TO PHYSICAL DATABASE;

4. Restart the media recovery

Alert log




No more block corruption worries

Data Block Corruption


SQL> select eno from emp;

select eno from emp * ERROR at line 1: ORA-01578: ORACLE data block corrupted (file # 3, block # 36) ORA-01110: data file 3: ‘users01.dbf’

Automatic Block Corruption Repair


• Physically corrupted blocks replaced with the uncorrupted blocks between primary and standby, vice-versa

• No need of manual block recovery • Standby database must be in real-time query mode

• Automatic Block Media Recovery (AMBR) bg perform the task

Automatic Block Corruption Repair


ALTER SYSTEM: Flushing buffer cache Corrupt block relative dba: 0x0100008b (file 3, block 36) Completely zero block found during multiblock buffer read Reading datafile ‘users01.dbf’ for corruption at rdba: 0x0100008b (file 3, block 36) Reread (file 3, block 36) found same corrupt data Starting background process ABMR ABMR started with pid=40, OS id=6369 Auto BMR service is active. Requesting Auto BMR for (file# 3, block# 36) Waiting Auto BMR response for (file# 3, block# 36) Auto BMR successful

SQL> select column1 from table1; select column1 from table1 * ERROR at line 1: ORA-01578: ORACLE data block corrupted (file # 3, block # 36) ORA-01110: data file 3: ‘users01.dbf’

Real Time Query


Real-time query

• COMPATIBLE must >= 11.0

• Database must be OPENED in READ ONLY WITH APPLY


Backup nightmares?

Offloading Backups to Standby Database


• Offload workload pressure from the primary database

• Backups are interchangeable between primary and standby

• Require no changes in RMAN backup scripts

Offloading backups to standby database


Advantages

Far Sync


Long distance standby database with zero data loss – Far Sync Concepts

Far Sync


Long distance standby database with zero data loss – Far Sync Overview

• A light-weight/remote standby instance • Receives the redo synchronously from the primary • Forward the same to the remote standby databases asynchronously over WAN • Supports a maximum of 29 remote standby databases • Far sync instance doesn’t have any physical structure • Contains instance, standby controlfile and set of redo logs • Consumes minimal resources over the server (CPU, Memory, I/O etc) • Overcome network latency issues while shipping redo synchronously • Guarantees zero data loss capabilities • Keep it close to the primary site, 30-150 miles • Multiple Far sync instance can be configured for active/passive purpose

Far Sync


Long distance standby database with zero data loss – Far Sync Architecture

A big thank you all for

listening ...


You can write me at [email protected]

Documents

Getting Maximum returns on Data Guard Investment...Presented by : Syed Jaffer Hussain AIOUG Sangam 2014 Slide # 1 . Getting Maximum returns on Data Guard Investment