NetApp und Oracle Effizientes Backup. September 2011 Klaus Wagner Solution Architekt NetApp Deutschland GmbH

Transkript

1 NetApp und Oracle Effizientes Backup September 2011 Klaus Wagner Solution Architekt NetApp Deutschland GmbH

2 Herausforderungen für zukünftiges Backup und Recovery HEUTE Traditionelles Backup Full Backup D2D Server Stunden LTO Tape Drive Sicherungszeiten Recovery Time Objective (Dauer für die Wiederherstellung eines Geschäftsprozesses) Recovery Point Objective (Menge an verlorenen Daten / Transaktionen) Kosten 8 bis 10 Stunden Stunden bis Tage ~ 12 Stunden [(x*vollsicherung)+(y*inkrementell)] mal /GigaByte 2

3 Herausforderungen für zukünftiges Backup und Recovery HEUTE Daten- Wachstum Extremes Datenwachstum Anzahl der Datenkopien steigen RTO Data Produktion Storage Database Kopien Test & Dev Storage Clone TB Die Folge: Datenwachstum führt zu längeren Backup/Recovery Zeiten Erstellung einer Datenkopie dauert länger - Time to Market 3

4 Herausforderungen für zukünftiges Backup und Recovery HEUTE Daten- Wachstum Festplatten Festplatten - Kapazitäten verdoppeln sich p.a. - aber die Geschwindigkeit kaum Kapazität FC Speicherarchitekturen ändern sich FC/ SAS Flash IOPS optimized Speed SATA SATA / SAS SAS SAS Capacityoptimized Disk Typ 4GB 72GB 600GB 2 TB??? Avg. transfer rate (MB/s) Transfer rate pro Stunde (GB/hr) Sicherungszeit pro Disk ~6 min ~19 min ~85min 4.2hr Die Folge: Tägliche Sicherungen scheitern bereits an der Quelle Traditionelle D2D Lösungen (VTL) werden keine Lösung bringen 4

5 Herausforderungen für zukünftiges Backup und Recovery HEUTE Daten- Wachstum Festplatten Storage-Effizienz Technologien Speichereffizienz Technologien senken signifikant die Kosten für Online Storage. ~75% mehr Daten pro Disk durch DeDuplizierung und Komprimierung sind möglich. Data Growth $ SATA Drives / PAM II ThinProvisioning DeDuplikation Kompression Daten pro physikalischer Festplatte 3.5 TB Daten 2TB Daten bei Deduplizierung & Komprimierung TB Die Folge: signifikanter Anstieg der Sicherungsdauer (z.b. o.g. Beispiel ~7.5 Stunden pro 2TB Disk) 5

6 Herausforderungen für zukünftiges Backup und Recovery HEUTE Daten- Wachstum Festplatten Storage-Effizienz Technologien Server- Virtualisierung Vor der Server-Virtualisierung: - Dedizierter SLA pro Dienst - Dedizierte Ressourcen für Backup Durch Server-Virtualisierung - Gemeinsame Ressourcen bestimmen gesamt SLA - Ausfall einer Ressource beeinflusst gesamt SLA Backup Agent Application Die Folge: Server Virtualisierung passt nicht für traditionelle Backup Ansätze oder traditionelles Backup passt nicht für Server Virtualisierung 6

7 Der Paradigmenwechsel von Backup & Recovery DR DP market Prim. DP HA Prim & HA & DR & DP & Test/Dev DP DP Old century DP regular fullbackups, separate techniques for DP, DR and HA Backup2Disk & VTLs (some target Dedupe) offers only limited improvements to oldcentury DP & DR Old century DP result in very poor DP SLAs (too much data & files have to be transferred) Client Dedupe & Blocklevel-Increm.- Forever DP minimizes backup transferrates, but slows down Restore & Tapecopy Snapshot-based DP (with Mirroring / Replication) avoids transfers for backups and restores, combines DP, DR, HA and Test/Dev-functions Dedupe & compression benefits start at Primary Data and are kept (great DP SLAs & reduced costs) 7

8 Effizienz steigern NetApp Unified Architecture Protokolle FC FCoE iscsi NFS CIFS Object Breites System Portfolio NetApp FAS und V-Series rmitdata ONTAP Performance SSD FlexCache Unified Management Integrierte Datensicherung für Applikationen Eine Architektur für alle Workloads und Protokolle $ Storage Effizienz TB Datenwachstum SATA / Flash Cache RAID-DP Thin Provisioning Snapshot Tech. Deduplizierung Thin Replication Virtual Copies Kompression 8

9 Backup und Restore SLAs einhalten Backup Fenster einhalten durch Snapshots Backup Dauer entkoppeln von der Datenbankgröße Keine negativen Performance Einflüsse während des Backups und während des Betriebs Ermöglicht Backups wann Sie wollen und so oft Sie wollen Snapshot Kopie Komplette Restores in Minuten Restore Dauer unabhängig von der Datenbankgröße Stündliche Sicherungen ermöglichen schnelles Recovery (Roll Forward) Ermöglicht niedrige Recovery Time Objectives (RTO) Integration in die Applikation Stellt Konsistenz sicher minimiert das Risiko beim Restore- Vorgang 9

10 Backup und Restore SLAs einhalten Backup to Disk Applikationskonsistente SnapShots übertragen Nur geänderte Blöcke Geringe infrastrukturelle Voraussetzungen Wechsel auf eine neidrigeres Storage Tier möglich Optimierung der Prozesse Nutzung des Backups auch für weiteren Desaster Schutz Nutzung des Backups für Test- und Entwicklungs Datenbanken 10

11 Klonen: Zero-Space Virtuelle Kopien Production Storage Test & Dev Storage ohne FlexClone 6TB Datenbank 30TB Speicher 5 Vollkopien NetApp FlexClone 6TB Datenbank 8TB Speicher 1 Kopie, 4 Klone 11

12 Effizientes Desaster Recovery Enabling Technologien: MetroCluster, SnapMirror, ThinCloning, SnapManager App Dev Test BI Backup Produktionsdaten DR Kopie Virtualisierter Speicherbereich Unified Storage Skalierbarkeit Leistungsfähigkeit Einheitliches Management 12

13 Integration in die Applikation 13

14 1995 First filer for Oracle DB sold 1997 Oracle certifies NetApp NetApp and Oracle Partnership 2001 NetApp runs its core business on Oracle E-Business Suite 1999 NetApp and Oracle NetApp helps Blueprints from establish Oracle Consulting Oracle Storage Compatibility Program (OSCP) Oracle B2B Exchange selects NetApp NetApp is Certified Solution Partner Oracle on NetApp customers in production Linux competency center NetApp deployment at Oracle: 500TB Oracle NetApp Joint Escalation Team ONJET Joint Center of Excellence (CoE) and professional services 2005 NetApp at Oracle: - over 3200 TB - 14,000 Servers ONTAP 7G FlexVol & FlexClone deployed NetApp runs Oracle SnapValidator announced EM Grid Control Integration 2004 NetApp at Oracle: - over 2000 TB - 9,500 Servers at Oracle Austin Data Center Enterprise Grid Alliance Oracle builds next Apps on NetApp storage 2007/08 NetApp at Oracle: - over 12 PB - 25,000+ servers Oracle Enterprise Linux 4 Support SnapLock Integration SMB Bundle D-NFS development Oracle VM DR for OFM NetApp ILM for Oracle Security 2006 NetApp at Oracle: - over 5500 TB - 20,000 servers SnapManager for Oracle joint customers NetApp Confidential -- Limited Use 14

15 SnapManager für Oracle 9i, 10g, und 11g SnapManager für Oracle FCP, iscsi und NFS NetApp Storage Systeme Automatisiert Klonen sowie Backup und Recovery Nutzt NetApp SnapShot und FlexClone Funktionalität Enge Integration mit Oracle Technologien RMAN Automated Storage Manager (ASM) Direct NFS 15

16 Backup Automated, instantaneous and space-efficient backups using Snapshot Backup: Entire database Tablespaces Datafiles Policy-driven data protection via integration with Protection Manager Automates replicating backups from Primary to Secondary/DR storage Verifies backups using the Oracle Database Verify utility (optional) Provides a built-in scheduler Catalogs backups with RMAN (optional) 16

17 RMAN Integration Supports RMAN catalog located in seperate database (recommended) control files of target database Registering SMO backups in the RMAN catalog Backups taken with SMO can be managed, restored and recoverd with RMAN after SMO backup mount (e.g. block level recovery, recovery advisor) SMO backups are un-catalogued from the RMAN recovery catalog when they are pruned by the SMO retention expiration process Steps to enable 1. Setup RMAN and its recovery catalog 2. Create profile with RMAN connection clause 17

18 Restore & Recover Automated, rapid and granular restore & recovery using SnapRestore Restores datafiles (any size) in seconds More frequent backups Less logs to replay Faster recovery Automated restores from backups on: Primary storage Secondary storage (UNIX only) Restore options: Complete Selective Recovery options include recovering the database to: The last transaction that occurred in the database A specific date and time A specific Oracle SCN The time of the backup Preview option to review a file-by-file analysis of a restore operation 18

19 Clone Fast, automated, and space-efficient clones using FlexClone Clone to the same or alternate host Clone protected backups on: Primary storage Secondary/DR storage (UNIX only) Oracle parameters on clone can be changed Automates running pre-clone and post-clone scripts Automates running post-clone SQL statements Ideal for development and test environments 19

20 ASM Integration ASM file system is backed up even if it spans multiple storage volumes by taking a consistency group Snapshot copy of all LUNs Ability to restore just the required data within an ASM disk group using Partial File SnapRestore (PFSR) Clones an ASM disk group by re-stamping the LUNs and renaming the disk group 20

21 ASM Integration: Restore Complete Restore Volume-based SnapRestore or Single-File SnapRestore Selective Restore ASM extent map unchanged: PFSR each file that we want to restore (faster than copy from clone) ASM extend map changed: Clone the LUN and use RMAN to copy from the LUN clone the files that we want to restore 21

22 ASM Integration: Cloning ASM Diskgroup cloning via restamping of LUNs New ASM disk header for cloned LUNs ASM thinks that these are new ASM disks even though they are thin provisioned 22

23 Einfach und Flexibel Neu verfügbar NetApp SnapProtect Management Software Advanced FAS Backup Management Bietet ein zentrales Interface Erzeugt und managed - Lokale Snapshot Kopien - Replikation für FAS-to-FAS oder V-Series - Tape Backup Policies Zentralisiertes Auditing und Reporting Vereinfacht Suchen und Finden Katalogisiert alle Snapshot Kopien Verfolgt Snapshot Kopien von Disk-to-Disk-to- Tape Ermöglicht schnellere Antwortzeiten für E- Discovery Anfragen 23

24 What Is SnapProtect Software? Content Indexing SnapProtect Server DataFabric Manager Server Secondary Storage Provisioning LUN data SnapVault SnapMirror NAS data App Consistent Snapshot copies Replicated Snapshot copies Tape Copy Management Virtualization Tape Library 24

25 What Is Snap Creator Framework? A software framework that: Integrates NetApp data protection technologies into a single interface for multiple applications Runs on multiple operating systems Windows, RedHat, AIX, SUSE, Solaris Is extensible and flexible for new applications with plug-ins (supported and unsupported options) Benefits Ease of management Reduce data protection complexity Flexible architecture 25

26 Snap Creator 3.x Server Architecture NetApp Confidential - Internal Use Only 26

27 Snap Creator Plug-ins Existing plug-ins (3.3.0 and earlier) - Oracle - DB2 - MySQL New plug-ins with Sybase - Lotus Domino - VMware (vsphere and vcloud) - SnapManager for Exchange (SME) - SnapManager for SQL Server (SMSQL) NetApp Confidential - Internal Use Only 27

28 RMAN Proxy: Integration with Oracle RMAN RMAN is the Oracle client for Oracle Database backup. RMAN proxy copy is the interface for the partner/vendor to integrate their products with Oracle in an oracle way. RMAN proxy copy talk to NetApp Media Management Library(MML) NetApp MML integrated with Oracle API headers as per the backup/restore/clone flow NetApp takes the control from Oracle API headers with NetApp technologies and dependent operations using Ontap APIs 28

29 Crash Consistent Backups If you put the redo logs and the datafiles all in the same flexvol and take a snapshot, you ve got a perfectly synchronized set of redo logs and datafiles. That should be a recoverable snapshot, so long as nothing with nologging was running when the snapshot was taken. You could use CG snapshots across all volumes containing datafiles and redo logs and get a valid backup. This would be a crash-consistent backup.

30 The Simplest Method Backup: 1. Just take a snapshot Recovery: 1. Recover the whole snapshot

31 *Almost* No Data Loss Backup: 1. Start hot backup mode 2. Snap Flexvol 2 3. End hot backup mode 4. Switch the logs 5. Snap Flexvol 1 Recovery: 1. Restore snapshot on Flexvol 2 2. Apply archive log data.

32 No Data Loss, Short of a Triple-disk Failure Backup: 1. Start hot backup mode 2. Snap Flexvol 3 3. End hot backup mode 4. Switch the logs 5. Snap Flexvol 1 Recovery: 1. Restore snapshot on Flexvol 3 2. Apply archive log data. 3. Apply redo log data.

33 33