Beruflich Dokumente
Kultur Dokumente
5 Reference Architecture
5 Reference Architecture
8-day
Global Specialty Retailer outage
Disk failure, followed by mirrored disk failure. Restore from local
backup failed. Restore using copy at DR site also failed.
Copyright 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal Use Only
Program Agenda
5 Reference Architecture
Data
Days/Hours
Oracle Secure Backup Physical Hours/Days
(from last backup)
Hours
Recovery Manager (RMAN) Physical Hours/Days
(from last backup)
Minutes/Hours
Flashback Technologies Logical Minutes/Hours
(from point-in-time)
Flashback
Human error
correction
Platinum-Ready Apps
PLATINUM Clusters and Replication
Clusters
GOLD Replication
Clusters
SILVER
Backups
Single Instance
BRONZE
Backups
Backups and DR without validation is enormous risk Validation is helpful everywhere: I/O, memory, storage,
Do not guarantee working or meeting recovery SLAs Oracle data block, inter-block, database and application
Deduplication type Source sends changed data only Target Inline dedup
save network bandwidth
Oracle database-aware Yes - HCC No no HCC awareness
Backup performance Faster than full backup depending on the Full backup time + deduplication
database change rate processing time
Restore performance Similar to that of backup operation with Restore is longer due to rehydration
merged full backup process
5 Reference Architecture
We can do a much better job preventing and Id like to know that my backups are validated when
repairing corruptions in real time. they are created, and on a regular basis to make
sure they are good. I want to be alerted whenever a
database can NOT meet my recovery SLAs.
Database side:
Network packet Errors in file
containing /u01/app/oracle/diag/rdbms/qs/qs1/trace/qs1_dbwf_41262.trc:
database write ORA-27603: Cell storage I/O error, I/O failed on disk
is corrupted o/192.168.10.29;192.168.10.30/DATAC1_CD_02_CELL7 at offset
151396352
Cell prevents for data length 8192
write of corrupt ORA-27626: Exadata error: 205 (HARD check failed)
block and ASM WARNING: Write Failed, will retry. group:1 disk:74 AU:36
retries write offset:401408
size:8192
We can do a much better job preventing and Id like to know that my backups are validated when
repairing corruptions in real time. they are created, and on a regular basis to make
sure they are good. I want to be alerted whenever a
database can NOT meet my recovery SLAs.
Delta Push
Access and send only changes
Minimal impact on production
Data Guard-like real-time redo ship
instantly protects new transactions
Recovery
Appliance Tape Archive
Data validated when copied
Data validated on receive to and restored from tape
Data periodically revalidated
Data validated on restore
Built using MAA practices Remote Replica
ASM auto repair
Exadata HARD checks and Data validated on receive,
automatic disk scrub/repair restore, and periodically
ASM and Exadata checks
and repair
Copyright 2014, Oracle and/or its affiliates. All rights reserved. |
Policy-Based Database Protection as a Service
MAA parameters
ASM redundancy
RMAN Backups
ZDLRA so we can count on
successful restore when
required
Exadata-unique capabilities for
the best database protection
and availability
5 Reference Architecture
0 0
0 0
0 0
Exadata HARD checks on write, automatic disk scrub and repair HARD checks on write
Automatic
Automatic block
block media
media recovery
recovery
Database Files requested
successfulfor
for(file#6,
(file#6,block
block#8738)
#8738)
SYNC ASYNC
Limited distance any distance
transport compression over WAN
5 Reference Architecture
Online Online
Tape or Disk Storage Tape or Disk
Backup Storage Backup