1. EMC Next-Generation Backup and Recovery for Oracle
Apollo Aguilan
EMC Backup Recovery Systems

2. Agenda Problems many database administrators face
Title
Month Year
Agenda
Problems many database administrators face
Overview of Oracle Recovery Manager (RMAN) functional components
Key features of EMC Data Domain deduplication storage systems
Impact of Data Domain deduplication in an Oracle environment
Customer Experience
Summary
Questions

3. Problems Many Database Administrators Face
Title
Month Year
Problems Many Database Administrators Face
Too many for this talk so we’ll focus on just backup and recovery
Non-stop growth and proliferation
Backup windows remain approximately the same
Recovery is just as important and often overlooked
Limited online retention
Increased frequency of recovery for audits, troubleshooting, updates, etc.
Archive (aka, ILM) becoming increasingly important
Some data must be retained for 5 years, 7 years, forever….
Ask how many in the audience are DBA’s or work closely with their DBA?
Start into the list
Non-stop growth and proliferation
New applications often call for new supporting databases
Nearly all databases have multiple copies for development, testing, standby, etc.
Existing databases are getting larger
Terabyte databases used to be rare, now increasingly common
Oracle (and other vendors) have made this easier to deploy and manage but
Backup windows remain approximately the same
Need to complete nightly backups quickly
Weekly backups have to complete in a weekend
Recovery is just as important and often overlooked
Test recoveries should be performed regularly but stress available resources
Pressure to make recovery quick and simple to reduce steps and limit errors
Archive becoming increasingly important
Information Lifecycle Management
Retain and recover data from years ago, not just days ago

4. Deduplication Enables Next-Generation Storage Architectures
When did you implement this?
What made you evolve?
Primary Disk
Tape
Storage 2.0
Why did you add SATA?
What did you learn?
Primary Disk
SATA
Tape
Note to Presenter: View in Slide Show mode for animation.
EMC Backup and Recovery solutions are leading the way in next generation backup by delivering disk based deduplication solutions to speed backups, reduce storage and recover more reliably. Using EMC backup solutions can reduce network bandwidth by up to 90% and storage by 10-30x.  Data on disk is available online for longer retention periods making restores faster and more reliable, plus deduplicated data can be efficiently replicated to remote sites for improved disaster recovery.
As IT infrastructure shifts from physical servers to virtual, an evolution is taking place in the backup and recovery market. EMC Data Domain is helping customers transition for their journey into the future.
Storage 3.0
Backup/recover plus archive from disk (shrink primary)
Tape: monthly
Primary
Tape
Deduplicate SATA
Before
After
Storage 4.0
Flash for primary
Everything else to deduplicate
Flash
Deduplicate SATA
Before
After

5. Next Generation Backup Disrupts Market
Emergence of Protection Storage
$6.8B
$9.7B
Purpose Built Backup Appliances*
Emphasis on end to end solutions – Software and Storage
Tape continues to decline and use cases narrow
CAGR: 5.2%
In April of this year, IDC released a report on the Purpose-Built Backup Appliance market, a market that has been the biggest result of the emergence of deduplication. It’s the green band on this chart. This market didn’t really exist 10 years ago. EMC entered it with our VTL, the Disk Library, in This chart compares the forecast to backup software and tape automation. Together, we’re talking about a $9B market over time.
You can see a couple critical things happening:
Tape continues to go down
Backup appliances, what we have called Protection Storage, grows at 3x the rate of backup software
Over time, this market will be led by end-to-end design thinking
Storage and software are both playing powerful roles.
We believe the storage will matter even more than the backup framework, because it can consolidate more data to protect, as Stephen will discuss later.
Lets break it out a little bit…
CAGR:16.6%
CAGR: – 7.9%
*IDC: Purpose-Built Backup Appliances (PBBAs) are typically tightly coupled with application software and utilize technologies such as data deduplication and replication.
Source: IDC

6. Purpose Built Backup Appliances
Fastest Growing Market Segment
This is a $1.7B market that hasn’t really been tracked until now.
EMC is in a clear leadership position with over 64% market share.
Of all the backup market segments, that’s a great place to be, since it’s growing the fastest – and it will be a $3.6B market in just a few years.
EMC: 64.2%
2010 Total Market
$1.69B
Source: IDC Purpose Built Backup Appliances, April Above: Worldwide Supplier Revenue, Total PBBA Market

7. RMAN – What Is It? Oracle’s included backup / recovery utility
For those in the audience that don’t already know:
Oracle’s included backup / recovery utility
Supports full, incremental, and image backups
Retains backup information in the control file and (optionally) a separate database catalog
Many configuration options to tailor to users’ requirements
Automatically eliminates unused data blocks from most backups

8. Overview of RMAN Functional Components
RMAN Client
Recovery Catalog
Flash Recovery Area
(FRA)
Target Database
At a minimum, RMAN must include the following:
Start with the target database to be backed up
The RMAN client
Provides either a command line, script or GUI interface via OEM interprets backup and recovery commands directs server sessions to execute those commands records your backup and recovery activity in the target database control file.
Backup can be either to DISK or
Via an Enterprise backup application which can direct it either to disk or tape
Optional RMAN components:
A recovery catalog database is a separate database schema used to record RMAN activity for one or more target databases Can retain backup / recovery data for longer periods than would normally be kept in controlfile
A flash recovery area
a disk location which the database stores and manages files related to backup and recovery
example: archived redo logs, other recovery related files…
RMAN Repository
(Control File)
Disk
Backup
Third Party Media Managers
Media Management Layer (MML) API
Backup
Tape

9. Overview of RMAN Functional Components
RMAN Client
Recovery Catalog
FRA
Target Database
At a minimum, RMAN must include the following:
Start with the target database to be backed up
The RMAN client
Provides either a command line, script or GUI interface via OEM interprets backup and recovery commands directs server sessions to execute those commands records your backup and recovery activity in the target database control file.
Backup can be either to DISK or
Via an Enterprise backup application which can direct it either to disk or tape
Optional RMAN components:
A recovery catalog database is a separate database schema used to record RMAN activity for one or more target databases Can retain backup / recovery data for longer periods than would normally be kept in controlfile
A flash recovery area
a disk location which the database stores and manages files related to backup and recovery
RMAN Repository
(Control File)
Disk
Backup
Third Party Media Managers
MML API
Backup

10. Data Domain Deduplication Storage Systems

11. Transforming Your Oracle Backup Environment
Retain longer Keep backups onsite longer with less disk for fast, reliable restores, and eliminate the use of tape for operational recovery.
Replicate smarter Move only deduplicated and compressed data over existing networks for up to 99% bandwidth efficiency and cost-effective DR.
Recover reliably Continuous fault-detection and self-healing ensure data recoverability to meet SLAs.
Retain onside backups longer with 10-30x data deduplication on Data Domain systems
Replicate smarter with network-efficient, cost effective disaster recovery
Recover reliably with Data Domain ultra-safe storage for predictable data recovery, continuously verifying backup images with fault detection and healing on top of dual disk parity RAID 6
WAN

12. Performance: CPU-Centric versus Spindle-Bound
Throughput MB/s 50
6,000
Number of Disk Spindles
100
150
200
Data Domain
Fibre Channel
SATA
Most
deduplication
vendors
This slide shows another way to look at the virtues of being CPU-centric.
As mentioned before, most of the deduplication competitors for backup targets are spindle-bound or disk-bound. It takes so many disk seeks to look up the information to tell whether data has been stored before or not, and to sort out and then minimize the data, that it takes a lot of disk drives or faster disk drives to get the job done.
This slide shows what’s happened in our competitive environment as a result. If they’re using SATA disk drives, most deduplication storage vendors tend to need three or four times as many drives as a Data Domain system to store the same amount of deduplicated data.
In some cases, for example, IBM’s ProtecTIER, storage systems use Fibre Channel drives instead of SATA. This can decrease the seek time, but it comes at a significantly higher cost. Data Domain systems, by being CPU-centric and minimizing disk usage to only what is required to store the actual data, end up having a smaller footprint. This can look like a weakness, but it’s actually a strength.
By keeping the costs down, the Data Domain system is much better structured to compete on a comparison, for example, with a tape library, and its cost per gigabyte.

13. Deduplication at Backup / Recovery Speeds
102,400 lookups/sec.: is it already in the multi-TB store?
800 MB/sec, for 8KB segment: >100K lookups per second
If random lookups: very slow
Each disk: 1 MB/sec
E.g. for a 7.2KB RPM Seagate 1TB SATA drive: <120 seeks/second
8KB segment: 0.96 MB/sec/disk
Would need 830 disks to go 800 MB/sec (like most dedupers today)
This is 4 full height racks of nothing but SATA disks (16 drives / 3U rack)
Same performance, in less than half a full height rack 13

14. SISL Scaling Architecture
Data Domain answer: SISL™
Stream-informed Segment Layout includes:
Summary Vector in RAM says if segment is new
Segment Localities minimize seeks if answer is on disk
Check uniqueness with Summary Vector
Check in-memory fingerprint cache
Key results
Check uniqueness with Summary vector
If unique, then store with local compression
Summary Vector cannot conclude redundancy
It can have false positives
If SV test says segment may not be unique, move to next step
Check in-memory fingerprint cache
Prefetch Localities of fingerprints for good hit ratio
Key results
System capacity is very scalable
No RAM constraint on index
Good performance with few spindles
Very few disk accesses during write
Inline deduplication is enabled by Streams Informed Segment Layout (SISL). SISL identifies 99 percent of duplicate segments in RAM and ensures that all related segments are stored in close proximity on disk for optimal reads.
See: 14

15. Data Domain Basics Easy integration with existing environment
Control Tier
Target Tier
Disaster Recovery Tier
Backup and archive applications
CIFS, NFS,
NDMP, DD Boost
Ethernet
Virtual Tape
Library (VTL) over
Fibre Channel
EMC
Symantec
CommVault
Tivoli Software
BakBone Software
Quest
Replication
A Data Domain appliance is a deduplication storage system with a controller and disk shelves. It is optimized for backup as well as archiving applications, and supports industry-leading commercial backup software, like EMC NetWorker, Symantec NetBackup, IBM Tivoli Storage Manager, and CommVault, in addition to boutique applications such as Quest vRangerPro for VMware.
Data Domain systems integrate with Ethernet via NFS or CIFS; and optimized protocols, such as Data Domain Boost. Fibre Channel is also supported with optional Virtual Tape Library software.
After data has been deduplicated and stored on disk, it can be replicated for disaster recovery, transferring only the compressed, deduplicated, unique, data segments; enabling faster “time-to-DR”
Data Domain systems sustain unrivaled aggregate inline deduplication throughput.
DD890 appliance
DD890 appliance 2U
2 to 10 ports
10 and 1 Gigabit Ethernet; 8 Gb/s Fibre Channel
RAID 6
Up to 285 TB usable capacity with shelves
2 TB or 1 TB 7.2K rpm SATA hard disk drives in shelf
File system
NVRAM
N+1 fans and redundant, hot-plug power supplies

16. Applying Deduplication to Oracle
Deduplication enables weeks or months of full backups to be stored in about the same space required for a single backup on traditional disk
Without deduplication
Week 2
Week 3
Deduplication enables weeks or months of full backups to be stored in about the same space required for a single backup on traditional disk
1 TB +
1 TB +
1 TB +
Week 1
With deduplication
Enables full restores
500 GB
Initial Full
Changed Data

17. EMC Data Domain RMAN disk-only backup and recovery strategies
Simplifies the backup process
RMAN disk-only backup and recovery strategies are more straightforward
Leverages Oracle Enterprise Manager
GUI for managing backups, restore points, creating backup reports, etc
Supports other Oracle backup capabilities
Incremental merge
Flash Recovery
Production Database
Dev/Test Databases
DR Databases
Data Domain systems integrate with RMAN and commercial backup software for Fibre Channel based Virtual Tape Library connectivity. Additionally RMAN and Oracle Enterprise Manager can be leveraged to backup directly to the Data Domain system via NFS or CIFS protocols, without the use of commercial backup software.
Operational Restores can be leveraged for Dev/Test environment refresh
RMAN backups are performed natively via NFS/CIFS
Data Domain Deduplication Storage
DR Restores can be performed manually or automated via scripts
RMAN backups are replicated automatically using minimal bandwidth
Data Domain Deduplication Storage

18. “This is the format for a quote slide.”
Attribute

19. Data Deduplication: Technology Overview
Store more backups in a smaller footprint
Friday Full Backup A B C D E F G
Backup Estimated
Data Logical Reduction Physical
FRIDAY FULL 1 TB 2–4x 250 GB
Mon Incremental A B H
Monday Incremental 100 GB 7–10x 10 GB
A technology overview of data deduplication will help illustrate how you can store more backups in a smaller footprint with Data Domain.
Note to Presenter: Click now in Slide Show mode for animation.
On Friday, the backup application initiates the first full backup of 1 TB, but only 250 GB is stored on Data Domain. This occurs because as the data stream is coming into Data Domain, the system is deduplicating before storing data to disk. On average this results in a two- to four-times reduction in data on a first full backup.
Over the course of the week, 100 GB daily incremental backups result in a seven- to 10-times reduction and only require 10 GB to be stored. As the graphic on the left shows, during the week incremental backups contain data that was already protected from the first full backup.
Finally, on the second Friday, the second full backup contains almost all redundant data. Therefore of the 1 TB backup dataset, only 18 GB needed to be stored.
In total, over the course of a week, 2.4 TB of data was backed up to Data Domain, but the system only required 308 GB of capacity to protect this dataset. Overall, this resulted in a 7.8-times reduction in one week.
Tues Incremental C B I
Tuesday Incremental 100 GB 7–10x 10 GB
Weds Incremental E G J
Wednesday Incremental 100 GB 7–10x 10 GB
Thurs Incremental A C K
Thursday Incremental 100 GB 7–10x 10 GB
Second Friday Full Backup B C D E F L G H
Second FRIDAY FULL 1 TB 50–60x 18 GB
TOTAL 2.4 TB 7.8x 308 GB A B C D E F G H I J K L

20. Data Integrity: Data Invulnerability Architecture
End-to-end data verification
Checksum
Deduplication, write to disk
Verify
Deduplication
Local Compression
RAID
File System
Generate
Checksum
Verify
Data
Verify the file system metadata integrity
Verify user data integrity
Verify stripe integrity
Re-Checksum and Compare
Self-healing file system
Cleaning
Expired data
Defrag
Verify
Another important differentiator for Data Domain systems is the Data Invulnerability Architecture.
Data Domain Data Invulnerability Architecture lays out the industry's best defense against data integrity issues by providing unprecedented levels of data protection, data verification, and self-healing capabilities that are unavailable in conventional disk or tape systems.
There are three key areas of data integrity protection described on this slide:
First is end-to-end data verification at backup time. As illustrated by the graphic at the right, end-to-end verification means reading data after it is written and comparing it to what was sent to disk, proving that it is reachable through the file system to disk and that the data is not corrupted. Specifically, when the Data Domain Operating System receives a write request from backup software, it computes a checksum over the data. After analyzing the data for redundancy, it stores the new data segments and all of the checksums.
After all the data has been written to disk, Data Domain Operating System verifies that it can read the entire file from the disk platter and through the Data Domain file system, and that the checksums of the data read back match the checksums of the written data. This confirms the data is correct and recoverable from every level of the system. If there are problems anywhere along the way—for example, if a bit has flipped on a disk drive—it will be caught. Since most restores happen within a day or two of backups, systems that verify/correct data integrity slowly over time will be too late for most recoveries.
Second is a self-healing file system. Data Domain systems actively re-verify the integrity of all data every week in an ongoing background process. This scrub process will find and repair defects on the disk before they can become a problem. In addition, real-time error detection ensures that all data returned to the user during a restore is correct. On every read from disk, the system first verifies that the block read from disk is the block expected. It then uses the checksum to verify the integrity of the data. If any issue is found, the Data Domain Operating System will self-heal and correct the data error.
In addition to data verification and self-healing, there are a collection of other capabilities. Data Domain with RAID 6 provides double disk failure protection; NVRAM enables fast, safe restart; and snapshots provide point-in-time file system recoverability.
Backups are the data store of last resort. Data Domain Data Invulnerability Architecture provides extra levels of data integrity protection to detect faults and repair them to ensure backup data or recovery is not at risk.
Other
RAID 6
NVRAM
Snapshots
End-to-end data verification

21. Weekly Full Backup – With Deduplication
Title
Month Year
Weekly Full Backup – With Deduplication
Weekly: Full image backups
RMAN> ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> BACKUP AS COPY TAG ‘MAY9’ DATABASE INCLUDE CURRENT CONTROLFILE; RMAN> BACKUP ARCHIVELOGS TAG ‘MAY9’ ALL NOT BACKED UP DELETE ALL INPUT;
Before: Without deduplication
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
The target database to be backed up;
The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Oracle Protection Techniques
RMAN to mml of 3rd Party BU application (tape or disk)
RMAN from primary or standby db direct to tier 1 disk or tape (no 3rd party backup application involved)
Split Mirror Backup: Mirrored volumes are sync’d, split and mounted to an alternate server and swept as flat files by 3rd party backup application. RMAN can participate in a split mirror backup.
Disk
1 TB
Target DB
1 TB

22. Weekly Full Backup – With Deduplication
Title
Month Year
Weekly Full Backup – With Deduplication
Weekly: Full image backups
RMAN> ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> BACKUP AS COPY TAG ‘MAY9’ DATABASE INCLUDE CURRENT CONTROLFILE; RMAN> BACKUP ARCHIVELOGS TAG ‘MAY9’ ALL NOT BACKED UP DELETE ALL INPUT;
After: With deduplication
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
The target database to be backed up;
The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Oracle Protection Techniques
RMAN to mml of 3rd Party BU application (tape or disk)
RMAN from primary or standby db direct to tier 1 disk or tape (no 3rd party backup application involved)
Split Mirror Backup: Mirrored volumes are sync’d, split and mounted to an alternate server and swept as flat files by 3rd party backup application. RMAN can participate in a split mirror backup.
Full
500 GB
500 GB
Target DB
1 TB

23. Weekly Full Backup – With Deduplication
Title
Month Year
Weekly Full Backup – With Deduplication
Weekly: Full image backups
RMAN> ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’; RMAN> BACKUP AS COPY TAG ‘MAY9’ DATABASE INCLUDE CURRENT CONTROLFILE; RMAN> BACKUP ARCHIVELOGS TAG ‘MAY9’ ALL NOT BACKED UP DELETE ALL INPUT;
After: With deduplication
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
The target database to be backed up;
The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Oracle Protection Techniques
RMAN to mml of 3rd Party BU application (tape or disk)
RMAN from primary or standby db direct to tier 1 disk or tape (no 3rd party backup application involved)
Split Mirror Backup: Mirrored volumes are sync’d, split and mounted to an alternate server and swept as flat files by 3rd party backup application. RMAN can participate in a split mirror backup.
Full
Deduplication applied to fulls requiring much less disk
500 GB
500 GB
Target DB
1 TB

24. Daily Incremental Backup – With Deduplication
Title
Month Year
Daily Incremental Backup – With Deduplication
Daily: Incremental backup with update
RMAN> ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’;
RMAN> ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’;
Run {
RECOVER COPY …
BACKUP INCREMENTAL … }
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
The target database to be backed up;
The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Oracle Protection Techniques
RMAN to mml of 3rd Party BU application (tape or disk)
RMAN from primary or standby db direct to tier 1 disk or tape (no 3rd party backup application involved)
Split Mirror Backup: Mirrored volumes are sync’d, split and mounted to an alternate server and swept as flat files by 3rd party backup application. RMAN can participate in a split mirror backup.
Incrementals after deduplication
500 GB
Weekly Fulls
Target DB
1 TB

25. Daily Incremental Backup – With Deduplication
Title
Month Year
Daily Incremental Backup – With Deduplication
Daily: Incremental backup with update
RMAN> ALLOCATE CHANNEL CH1 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’;
RMAN> ALLOCATE CHANNEL CH2 DEVICE TYPE DISK FORMAT ‘/dd/backup/ora.weekly/%U’;
Run {
RECOVER COPY …
BACKUP INCREMENTAL … }
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
The target database to be backed up;
The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Oracle Protection Techniques
RMAN to mml of 3rd Party BU application (tape or disk)
RMAN from primary or standby db direct to tier 1 disk or tape (no 3rd party backup application involved)
Split Mirror Backup: Mirrored volumes are sync’d, split and mounted to an alternate server and swept as flat files by 3rd party backup application. RMAN can participate in a split mirror backup.
Incrementals after deduplication
500 GB
Weekly Fulls
Daily Incrementals
Target DB
1 TB

26. Benefits of Using Inline Deduplication
Title
Month Year
Benefits of Using Inline Deduplication
Daily fulls instead of incrementals
Longer online retention of full backup images
No requirement for other backup software plug-ins
Non disruptive introduction into RMAN process
Simplified replication using EMC Data Domain Replicator Software
Ideal location for Flashback Recovery Area
Incrementally updated backups
Daily fulls instead of incrementals
Faster recoveries and cloning
Space management / compression performed by DDR, not Oracle server thus saving on valuable Oracle CPU cycles
No requirement for other Backup software plugins
Simplifies environment, saves $€£¥
Storage location on DDR can be used as source for Enterprise backup if necessary
DBA / RMAN in control without other products involvement
Non disruptive introduction into RMAN process
Presents as just another Disk-type storage location
Simplified replication using Data Domain replication
Easy for DBA to implement, validate, and test remote backup data
Provides an alternate means for shipping logs to the remote site or using Data Guard
Ideal location for Flashback Recovery Area
FRA usually requires at least 2X storage space of original database
One DDR used for both FRA and backup will eliminate most duplicate segments
RMAN maintains a full in FRA automatically anyway
Archivelogs written to FRA normally
Speeds up archivelog backup because they will be present already
Incrementally Updated Backups
Allows recovery from full backup images but only requires the taken of incremental backups (much faster)
Periodic full image backup is easily cloned with snapshots / fastcopy
Incremental backups optionally applied to clone of image backup
Minimal additional storage space required
Minimal time required since cloning is logical; no resynching afterwards required

27. Title
Month Year
Incremental Merge
EMC Data Domain combines rapid cloning and deduplication
Nightly take cumulative incremental; apply to snapshot of weekly full
First image backup 2X storage savings
Results in up-to-date nightly full images available for rapid recovery DB
Full
Snap
Snap
Snap
Snap
Snap
Incremental
Snap
Sun
Mon
Tue
Wed
Thu
Fri
Sat

28. Alternatives Oracle Backup Options
Title
Month Year
Alternatives Oracle Backup Options
RMAN to 3rd Party Backup Media Management Layer (MML)/ Serial Backup Tape (SBT)
Makes random access disk look like streaming tape for VTL support
Limits the options available to the DBA for backing up, cloning, merging, etc.
RMAN communicates through MML to agent on 3rd party backup application media server
Can front a Data Domain system as either disk-based backup or VTL
All RMAN I/O is via MML which presents only a DEVICE TYPE TAPE
Data Domain Systems can work with an enterprise backup application but does not require it.

29. Data Domain Boost + RMAN = Next-Generation Backup and Recovery for Oracle
Oracle Database Administrator self-reliance
Superior Backup and Recovery Performance
Replication Policy Management
Takes advantage of SBT integration using standard RMAN scripting tools for simple setup
Data Domain

30. DD Boost for RMAN Distributed Segment Processing
Distributed Segment Processing Enabled
Distributes parts of deduplication workflow to SBT plug-in on Oracle database server
Anchors and fingerprints segments
Checks with Data Domain system to find which segments are new/unique
Compresses and sends new segments only
Avoids sending duplicate data to Data Domain system
Provides load balancing and link failover
Supported with single controller Data Domain systems, Global Deduplication Array and DD Archiver

31. DD Boost for RMAN – Optimized Replication
Managed, bandwidth optimized replication
Oracle server directs replication of individual backups using RMAN
Data Domain system replicates only unique compressed segments
Reduces workload on the Oracle server
Multiple topologies – one-to-one, bi-directional, one-to-many, many-to-one, hierarchical
Encrypted optimized replication for security over WAN transparent to Oracle servers
Oracle Database
Catalog
Local Data Domain system
DR site Data Domain system
Start Replication 1
Copy 1
Update Catalog 4
Copy 1
Copy 2
Copy 2 3
Done 2
Secure Data Transfer

32. Advanced Load Balancing and Link Failover
Advanced Load Balancing & Link Failover
DD Boost level aggregation of multiple 1GbE or 10GbE links on Data Domain system
Backup/restore job load automatically distributed on multiple ports on DD system
Dynamic load balancing
DD Boost library negotiates with the Data Domain system for an interface
Load distribution based on number of jobs on the interfaces
Transparent failover of jobs
In-flight jobs on failed ports on DD system are transparently moved over to healthy links
Can be used in conjunction with network level / switch assisted aggregation 32

33. DD Boost Plug In
Install….. 33

34. Data Domain Boost for RMAN - Demonstration

35. Summary How deduplication benefits Oracle/RMAN backups Simplification
Title
Month Year
Summary
How deduplication benefits Oracle/RMAN backups
More online retention
Less data to replicate
Allows the benefits of incremental update/merge backups using less disk space
Simplification
Minimal changes to the environment
DBA’s familiarity with NAS storage
Savings
Less disk-based storage for longer retention
Reduce the cost of tape consumptions
Administrative cost
Less floor space
How deduplication benefits Oracle/RMAN backups
Less space consumed == more online rentention
Deduplication plus compression of data results in less data to replicate
Allows benefits of incremental backups while providing full backups for recovery
Simplification
NAS access to deduplication appliance allows DBA more backup/recovery options
Not as dependent on backup admins, backup application, or tape
DBA can use same storage for both backup, cloning, and archive
Multiple database instances can be saved to the same deduplication appliance
Savings
Less disk-based storage for longer online backup retention
Supports RMAN direct backups (DEVICE TYPE DISK) , eliminating reliance on enterprise backup application
Deduplicated storage requires less power and air conditioning

36. Title
Month Year
More Information…
For more information on EMC Data Domain deduplication storage systems and Oracle, contact your EMC sales representative or visit

37. Q&A