Copilot Deeper Dive - Veritasvox.veritas.com/legacyfs/online/veritasdata/Copilot... ·...

Copilot – Deeper Dive

Rasmus Rask Eilersen

2 © 2016 Veritas Technologies LLC. All rights reserved.

Contents

5

2

1

4

3

Video Demo of the process

Architecture and Process – Dump and Sweep

Terminology

Quick Overview of Copilot

Architecture and Process – Whole Database and Incremental Merge

What is Copilot for Oracle?

• DBA’s may not want to give up control of the backups

• DBA’s and Backup Admins do not always communicate

• Copilot strikes a balance – DBA’s back up to the NFS share on the Appliance

– NetBackup Admin gets them into NetBackup

– Or we can use Oracle Agent to back up DB and also perform Incremental Merge

• Benefits – Incremental Merge using a DBA familiar process

– DBA can check status of backups using familiar RMAN tools

– No performance overhead on Oracle server after initial backup

• Subsequent copies use resources of the Appliance

• Incremental Merge means less data transfer


Copilot Overview – Why Did We Develop It?

• NFS Share on an Appliance

• DBA can point a Dump to the NFS Share

– DBA’s have been doing this for ages

• Oracle Agent can be used with OIP if the DBA is willing

– DBA’s should be in the business of being a DBA, not data protection

• Once data is on NFS share, NBU can interact with it

• Enhancements to NBU Policy and code


Copilot Overview – What Makes It Work?

• Works on all supported master server platforms

• 5230 or later Appliance

• All supported Oracle client platforms

• NBU 7.7.1 or later

• NBU 2.7.1 on Appliance

• DB Pack License


Copilot Requirements

Terminology

• Some terms are “ours” and the DBA may not understand them

• Dump and Sweep also called Database Backup Share – Dump and Sweep is what Veritas calls this action

– Process where DBA backs up data using RMAN to an NFS share on the Appliance

– After the data is on the NFS share, NBU picks it up for additional protection options

– DBA initiates the process

• Whole Database with Incremental Merge (Accelerator) – Uses OIP or traditional RMAN Agent to call the backup from the Oracle server and send it to the

NFS share

– Not to be confused with NBU Accelerator, this is the Oracle process for sending only changed blocks

– Incremental Merge is understood by the DBA, Accelerator is not (but we check the Accelerator button on the NBU Policy)

– May or may not directly involve the DBA


Terminology

Architecture and Process

Dump and Sweep

• Takeaways – after the Dump process:

– NBU “talks” to the RMAN Catalog

– RMAN “knows” what NetBackup has done

– NetBackup creates an RMAN script on the fly

– Script is passed to Oracle Agent

• New options for this are in Policy


Process Flow – What Talks To What?

BPDBSBORA

1Queries DB for backups

on appliance share DB

2Writes a file in

/usr/openv/netbackup/logs/user_ops/dbext/logscontaining the backup sets to backed up

3Creates and executes a RMAN script

that passes the NB_ORA_BKUPSETSFILE name

to Oracle agent

BPHDB

BPCD

NB_ORA_BKUPSETSFILE

RMAN script

11

What Does It Look Like – Oracle Dump Process

12

What Does It Look Like – Oracle Dump Process

– After the DBA has Dumped the database

– There is one copy and it resides on disk

– After NetBackup has secured the data.

– There are now 2 copies of the data plus a controlfile backup (933), job ID 40 in activity monitor in subsequent slide.

13

What Does It Look Like – NetBackup Sweep Process

• Full schedule backs up everything on the share by default for the Oracle SID

• Differential and Cumulative Incremental schedules backup what has not already been backed up.

• The Archive Redo Log schedule behaves the same as other backup selection types.

14


• Database Backup Shares will protect any disk based RMAN backups DBA’s have placed on the shares

• Default “ALL_DATABASE_BACKUP_SHARES”. This keyword will protect all shares found for that instance

– Browsing for Oracle SID is possible, but a backup must already exist on the share

15


• New - Database Backup Share Options to delete backup sets or backup copies

– Traditionally the DBA would remove the dump after NBU had secured it

– NBU can do this automatically now

• The agent verifies that there is a copy in NetBackup before issue the RMAN delete command

16


• Job Id 31 backs up the RMAN files

• Job Id 32-39 updates the RMAN catalog

• Job Id 40 backs up the control file direct from the database to ensure we have the latest catalog entries.

• Typically would want to create a single NFS share for all Dumps

Architecture and Process

Whole Database with Incremental Merge

• Takeaways

– Same process as existing OIP or RMAN Agent Backup

– Data written to the NFS share

– Standard Oracle type backup (nothing really new here)


Process Flow – What Talks To What?

BPDBSBORA

1Queries DB

DB

4Writes a file in

/usr/openv/netbackup/logs/user_ops/dbext/logscontaining the backup sets to backed up

5Creates and executes a RMAN script

that passes the NB_ORA_BKUPSETSFILE name

to Oracle agent

BPHDB

BPCD

NB_ORA_BKUPSETSFILE

RMAN script

RMAN script

2Create and executes a RMAN script

that backups the databaseto the appliance NFS share

3Queries DB for backups

on appliance share

19

What Does It Look Like – NetBackup Oracle Backup

– Control file, Archive log and SPFILE backups

– Datafile backups

20


– Rman ‘list backup’ will show the proxy copies

– This will show the checkpoint time of each datafile copy, datafile name and location

21


• List of the Copilot share (NFS mount) will show the updated proxy copy that can be used for restore

• Size of the files on the NFS share is exactly the same as the size on the Oracle disk

22

What Does It Look Like – Incremental Merge Process

• The “Use Accelerator” checkbox triggers Oracle Incremental Merge

– This is a Oracle process that the DBA should be familiar with

– Important to note this is not “NBU Accelerator”

• Example – Child sent 514MB of data shown below (Job 90 on slide 24)

– Oracle would see this as a Full

23

What Does It Look Like – Whole DB Backup

• Whole Database – Datafile Copy Share will create a copy of the data files on the share and then protect them. This option is accelerator enabled

• Only accepts a single directory location. There is no default

• Browsing for a share is available

24

What Does It Look Like – Whole DB Backup

• 2 separate NetBackup jobs run

• Jobs 81 – 88 are the initial backup and update of the Oracle RMAN catalog

• Jobs 89 – 90 is the backup of the snapshot

• Typically would want to create a NFS share for each DB due to snapshots being done at the share level

25

How Do You Talk To The DBA and Backup Team?

• Both methods still require the DB to be registered with NBU

• Dump and Sweep

– DBA can maintain control over backups if desired

– NetBackup can use the DB dump and protect it still under Oracle control

• Tape/Disk/Dedupe

• DBA can restore from original dump (Oracle disk) if it hasn’t been removed, or restore can be initiated from NetBackup (SBT_TAPE)

• All being done via RMAN

• Whole DB with Incremental Merge

– NBU Admin has control

– Only moving Incremental data but Oracle considers it a Full backup


Q&A

Thank you!

Copyright © 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice.

Rasmus Rask Eilersen

[email protected] +4526128166

mailto:[email protected]

Copilot Deeper Dive - Veritasvox.veritas.com/legacyfs/online/veritasdata/Copilot... ·...

Documents

Transcript of Copilot Deeper Dive - Veritasvox.veritas.com/legacyfs/online/veritasdata/Copilot... ·...