Oracle Backup Solutions Overview August 2018

Oracle Backup Solutions Overview
St. Louis Oracle Users Group
August 9, 2018
Dan Glasscock
North American Sales
Strategy Lead, Oracle Database Cloud

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
2

Agenda
• Solution Overview
• Recovery Manager
• Flash Recovery Area
• Oracle Database Backup Cloud Service
• Oracle Recovery Appliance
• ZFS Storage Appliance for Backup
3

Backup and Recovery Solution Portfolio
4
Oracle Cloud
Protected Files
ExaCS
DBCS
Instantiate
into
DBCS/ExaCS
DB Backup Cloud Service
Secure Backup
On-Premises
Oracle Cloud
Storage
Compression
& Encryption
Backup to and Recover from On-Premises or Oracle Cloud
Protected Databases
Cloud @ Customer
Filesystem
RMAN: Built-in backup &
recovery engine for the Oracle
database which provides
performant, efficient
and dependable protection.
Recovery Appliance:
Engineered System purpose-
built for data center-wide Oracle
database protection which
ensures zero data loss, verifies
backup integrity, and reduces
data protection overhead by
eliminating repeated full
backups.
DB Backup Cloud Service:
Secure & scalable Oracle Cloud
Service providing cost effective
storage for long-term retention
& compliance of RMAN
backups.
Secure Backup: Centralized
disk, tape and cloud backup
management which provides
heterogeneous filesystem
protection for the entire data
center.
1
1
2
2
3
3
4
4

Common RMAN Configuration Settings
Description Benefits Cons
Archived log
mode
•Ability to recover to any point in time
•Enables online backup operations
Requires more storage
space to accommodate
both online redo and
archived logs
Block Change
Tracking (BCT)
Enables fast incremental backups. Without BCT, RMAN
would have to scan the entire database to determine which
blocks are changed during incremental backups.
MINIMAL overhead on
the database server
Control file
automatic
backup
•Database recoverability even if current control file, recovery
catalog is inaccessible.
•When in archived log mode, it is backed up automatically
when database structural changes are updated.
None
….Not Set By Default

Backup Retention Period
• RMAN retention policy options applicable to disk AND tape:
1. Redundancy ( how many copies ; default is REDUNDANCY 1)
2. Recovery window ( for example, 7 days)
• Long-term RMAN backups (outside of set retention policies) may be created
with KEEP FOREVER or with an UNTIL clause
• Issue RMAN DELETE OBSOLETE command regularly which
– DISK : Deletes backup related files which are no longer needed
– SBT : Updates media manager to which backup pieces are no longer needed
to meet user-configured RMAN retention settings
Recoverability

Recovery Catalog
• By default, RMAN’s metadata stored in the control file
• Having a separate Recovery catalog provides the following
advantages:
– Central RMAN metadata repository for one or more databases
– Enables use of RMAN stored scripts instead of just command line
– Enables creation of customized reports for all registered targets
– Centralizes management and storage of multiple databases (mixed database
versions and/or platforms)
– Enables use of the KEEP FOREVER clause
• No licensing fee for an RMAN catalog database
• Common strategy is to co-locate the RMAN, OSB and EM catalogs on
the same server
RMAN’s Schema

RMAN Good to Know Stuff
True or False
You can restart RMAN backups from an approximate point of failure?
• RMAN backups are restart-able from an approximate point of failure
–Smallest size of restartability is a backup set
–BACKUP DATABASE NOT BACKED UP SINCE TIME 'SYSDATE-1';

RMAN Good to Know RMAN – Cont’d
• RMAN command BACKUP RECOVERY AREA;
– RMAN disk or sbt destination (D2D2T)
– Optimized backup by default
– Always a backup set backup type
• RMAN backup encryption has license restrictions:
– Directly to disk requires Oracle Advanced Security Option (ASO)
– Directly to tape requires Oracle Secure Backup (OSB)
– RMAN compression
– BASIC is free
– HIGH, MEDIUM, LOW require Advanced Compression Option (ACO)

Agenda
10

What is Fast Recovery Area (FRA) ?
• Unified near-line storage location for all recovery files and recovery related activities in
an Oracle Database
– Centralized location for control file copies, multiplexed online redo logs, archived logs, flashback logs,
backups (image copy or backup set)
– FRA can be defined as a directory, file system, or ASM disk group
– A single recovery area can be shared by more than one database
– Initialization parameters db_recovery_file_dest & db_recovery_file_dest_size
• FRA may be on tier 2+ storage although not necessarily recommended
– Slower storage could effect production database performance
• Online redo logs, archived logs, Flashback logs and controlfile
RMAN Managed Disk Storage Location
NAME TYPE VALUE
------------------------------------ ----------- --------------------------
db_recovery_file_dest string /oradata/prod/fra
db_recovery_file_dest_size big integer 500G

Fast Recovery Area Sizing
• Archived logs - Estimate total size of all archived logs generated between
successive backups on the busiest days x 2 (in case of unexpected redo spikes)
• Flashback logs - Add in {Redo rate x Flashback retention target time x 2}
• Incremental backups - Add in their estimated sizes
• On-disk image copy - Add in size of the database minus size of temporary files
– When using an incrementally updated backup strategy (incremental forever after initial full)
• Full backup set backup(s)
– When using a full / incremental backup strategy
• Further details:
– http://docs.oracle.com/cd/E16655_01/backup.121/e17630/rcmconfb.htm#BRADV8183
Exercise in Math – Depends on What You Want to Keep

FRA – Instant Recovery
How do you recover a Tablespace with a corrupt Data file?
Without an FRA
1. Take the tablespace offline
2. Restore the Datafile from a
backup
3. Recover the Datafile
4. Place the tablespace back online
With FRA
1. Take the tablespace offline.
2. Switch to FRA Copy
3. Recover Datafile
4. Place the tablespace online.

Agenda
14

Oracle Database Backup Cloud Service (PaaS)
15
Low-Cost Offsite Cloud Storage for Oracle Database Backups
Firewall
On-Premises
Databases 10.2 and
above
Instant Offsite Storage
Cost Effective ($33/TB/Month)
On-demand Scalability
End-to-End Security
RMAN Encryption
RMAN Compression
3-Way Protection for HA
Geo-Replication for DR
24x7 Data Availability
Platform as a Service
Oracle Database Backup Cloud Service
Oracle DBaaS / Exadata Cloud Service
RMAN driven Backup
& Recovery

Backup Service: For your On-Premises Database Backups
16
Simple 4-Step Process
Cloud
Subscription
• Metered / Non-Metered
• Storage Capacity
• Identity Domain
• Service Name
• User ID/Password
• Geo-Replication
1 2 3 4
Install RMAN
Module
• Download
Installer from
OTN
• Run Installer
on the DB
Server
Configure
RMAN
• Tape (SBT)
Interface
• Encryption
• Compression
• Parallelism
Perform Backup &
Recovery
• Schedule full &
Incremental backups
• Restore & Recovery
on-demand

End-To-End Flow
Recovery
Manager
RMAN
Cloud
Module*
Oracle
Wallet*
OPC
Config File
Oracle
Database Backup
Cloud Service
Database, FRA
opc_host=https://odbs_dom.
storage.oraclecloud.com/odbs_svc-odbs_dom
opc_wallet='location=file:/abc/opcwlt‘
opc_container=‘myContainer’
$ rman target /
RMAN> CONFIGURE CHANNEL DEVICE TYPE SBT PARMS='SBT_LIBRARY=
/opc/libopc.so’ , SBT_PARMS=(OPC_PFILE=/opc/opcSID.ora)';
RMAN> CONFIGURE DEVICE TYPE SBT PARALLELISM 8;
RMAN> SET ENCRYPTION ON IDENTIFIED BY “mypwd” ONLY;
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
On-Premises
HTTPS over WAN
17
https://odbs_dom.storage.ora
clecloud.com/v1/odbs_svc-
odbs_dom/myContainer/H8djkj8
6/BA387934/0000001

Agenda
18

Traditional B&R Solutions Are Not Designed for Database
Treat Databases as Just Files to Periodically Copy
Daily Backup Window
Large performance impact on
production
Data Loss Exposure
Lose all data since last
backup – no validation
Many Systems to Manage
Scale by deploying more
backup appliances
Poor Database Recoverability
Many files are copied but
protection state of database
is unknown

Recovery Appliance – World’s Best Database Protection
✓Eliminate Data Loss
• Zero to Sub-second RPO
✓Shrink Backup Windows
•Reduce Backup Size by 10X or more
•Reduce Backup times by 10X or more
✓Be Ready for Recovery
• Continuous Restore Validation
• End-to-End Recovery Status
✓Scale Out Compute & Storage
• Resilient Hardware Platform

Traditional Weekly Full, Daily Incremental
Last Backup
Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat
Transactions NOT Backed Up!
Potential Data Loss!
ARCHIVED REDO LOG BACKUPS
+
RMAN
Catalog
Media
Catalog
PROD REDO
RMAN> crosscheck backup
RMAN> restore validate
Full Full Full
Incrementals Incrementals Incrementals
Un-Changed Data
Changed Data
Long Backup Windows, Data Loss Exposure
UNKNOWN Recoverability Status..
Until It’s Time to Restore!

Recovery Appliance – Superior Approach
Incremental Forever + Real-Time Transaction Protection
Latest Incremental
Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat
DB Level
Restore
Validation
+
Real-Time
Transaction
Protection
Integrated
Catalog within
Recovery Appliance
PROD
REDO
One Time
Full
Daily Incrementals
Day 1
Full
Day 2+
Incremental
Latest
Incremental
Latest VALIDATED Virtual Full Backup
Day 2+ VALIDATED Virtual Full Backup
Current Time
Real-Time
Protection!
REDO
TO
RA
Sun
Single Source of Truth
KNOWN Recoverability Status!

Recovery Appliance vs. Data Domain Comparison
• Core DB Daily Backup Size : 39TB → 1.4 TB
• Average backup size reduced by 30X
•
• Core DB Backup Window : 10 Hr → 50 Min
• Backup window reduced by 13X
Confidential – Oracle Internal
Backup Size Backup Window
0:00
1:12
2:24
3:36
4:48
6:00
7:12
8:24
9:36
10:48
12:00
A B C D E F G H I J K L M N
Hr(hh:mm)
DB
Backup Window
DataDomain
ZDLRA
0
500
1,000
1,500
2,000
2,500
3,000
3,500
4,000
A B C D E F G H I J K L M N
GB
DB
Backup Size
DataDomain
ZDLRA

Agenda
24

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 25
Oracle ZFS Storage Appliance for Backup
Introducing The Backup Appliance
Architected for Modern IT
High Capacity
Lower Cost
High Performance
High Availability
Database Co-Engineering

High-Throughput Design Speeds
Backup And Restore
• Up to 144 CPU cores deliver more
bandwidth
• Up to 3TB DRAM absorbs more backup
jobs at memory speeds
• Up to 460TB flash cache accelerates
reads and writes
• High-performance integration with
Oracle Engineered Systems
• Built-in tuning & reporting
further enhance Oracle Database
backup and restore performance
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 9

ZFS Storage Appliance
for Backup
Multiple File Types
Flat files,
Database blocks
2727Oracle Confidential--Internal/Restricted/Highly Restricted 2727
Any Database Any Application
Any Virtual
Machine
Multiple Backup
Software Options
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

Resources
• Monthly Technical Webcasts
– https://asktom.oracle.com
– https://www.oracle.com/technetwork/database/database-technologies/rman/overview/index.html
– Fast Recovery FAQ – Oracle Doc ID 833663.1
– https://support.oracle.com/epmos/faces/DocumentDisplay?id=833663.1&displayIndex=1#aref_section21
– https://cloud.oracle.com/database_backup
– https://www.oracle.com/engineered-systems/zero-data-loss-recovery-appliance/index.html
– https://www.oracle.com/storage/nas/zs-backup/
28

Oracle Backup Solutions Overview August 2018

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Oracle Backup Solutions Overview August 2018

Similaire à Oracle Backup Solutions Overview August 2018 (20)

Dernier

Dernier (20)

Oracle Backup Solutions Overview August 2018