VERITAS Database Edition 2.1 for Oracle - Storage Management & High Availability

1. Presentation Instructions • For a more high level presentation, please remove the following slides in addition to this one: • 24 to 26 , 28 to 30, 37 to 41, 45 to 48

2. VERITAS Database Edition 2.1for Oracle Storage Management & High Availability for Oracle Database Servers May 2000

3. Agenda • VERITAS Product Overview • DBA’s Challenges • VERITAS Database Edition for Oracle • Enhanced Performance • High Availability • Faster Recoverability • Improved Manageability • Summary

4. Database Administrator’s Challenges • Optimal database performance • 24x7 availability of mission-critical databases • Continuous database access • Fast recovery • Restore from consistent backups • Increasing management complexity • High growth in data volume • Complex data types (e.g., video, sound) • Increasing number of users • Diverse database server configurations (e.g. replication servers)

5. Database Edition for Oracle • VERITAS Database Edition 2.1 for Oracle enables database administrators to manage Oracle7.3 or later environments with the flexibility of file systems at raw disk performance. • Its data redundancy techniques, online administration features, and unique backup and recovery options increase data reliability and availability. Database Edition for Oracle enables DBAs to meet their top priorities: optimal performance, recoverability, availability, and manageability of databases

6. Oracle Database Edition for Oracle VCS Agent for Oracle VxDBA Utility NetBackup Block-Level Incremental Backup Extension VERITAS File System w/ Storage Checkpoints and Quick I/O VERITAS Volume Manager VERITAS Database Edition 2.1 • Integration of online and offline storage management HA Edition Building Blocks

7. Feature Overview • Quick I/O • Raw device performance with file system manageability • Cached Quick I/O for up to 150% performance improvement over raw devices • Protection from disk failures with fault-tolerant storage options • Online administration of database storage • Automatic monitoring and recovery of Oracle(HA Edition)

8. Feature Overview • Storage Checkpoints • Enables Block-Level Incremental Backup • Enables Storage Rollback for immediate “point-in-time” recovery from on-disk images • Enables off-host processing through Database Replication Option • Java-based Storage Administrator GUI • Visual configuration from a single console

9. Database Edition for Oracle Enhanced Performance

10. Database Edition for OraclePerformance • Increased performance increased productivity • Equal to raw device performance using Quick I/O • Greater than raw performance using Cached Quick I/O for read intensive workloads • Large I/O optimization • Accelerated I/O performance for large files (e.g., video, images)

11. Database Performance Issues with Conventional File Systems • Redundant data buffering • System buffer cache Database buffer cache • Redundant buffer copying • Inefficient use of memory • Single writer lock per file at UNIX file system level • UNIX file-level lock RDBMS row- or page-level lock • Serialized write operations • Impact on performance in multi-user client/server environments • Kernelized asynchronous I/O (KAIO) • Supported only on raw devices, not on regular files

12. Building Oracle Databases onRaw Disks vs. File Systems • Unique, total storage foundation solution to deliver the best of both worlds Database Editionfor Oracle Raw Disks Conventional File Systems Advantages Disadvantages Advantages Disadvantages • Manageability • Tablespace • organization • System-wide • backup and • restore • policies • Easy to create • and expand • files for Oracle • Manageability • “Invisible” • locations for • tablespaces • Difficult to • grow • tablespaces • Performance • Lower database • throughput • (30-90% of • raw disk) • Higher CPU • overhead • Data Reliability • Potential data loss • Performance • Best OLTP performance • Data • Reliability • No potential for data loss with data written to • disks directly

13. Quick I/O raw device regular file Raw Device PerformanceQuick I/O for Databases • Breakthrough VERITAS File System interface technology • Presents regular VERITAS File System files to Oracle as raw character devices • Allows parallel updates to database files for increased throughput • Takes advantage of kernel async I/O (Solaris’ KAIO) • Oracle handles locking for data integrity • Eliminates traditional UNIX file system overhead RDBMS Server

14. VERITAS Cached Quick I/O • Why Cached Quick I/O? • 4 GB maximum limit on Oracle buffer cache size for systems (32-bit) • Very large, enterprise class machines with several GB of memory (e.g., 64 GB on Sun E10000) • Current solution: Traditional buffered file systems • Goal: Retain Quick I/O reliability advantages over traditional buffered I/O systems, yet improve performance

15. Cached Quick I/O Overview • Implemented as a buffered read, direct write solution • Retains data reliability advantage of direct write • Gains read-ahead at the File System and memory-to-memory copy performance advantage • Easy online management to turn Cache on/off for Quick I/O files • Like Quick I/O, enabled on a per-file basis • Multiple database instances can co-exist with selective caching for specific datafiles • Little change to existing configuration • Does not require changes to OS or database version levels (to 64-bit architecture)

16. Cached Quick I/O Outperforms Raw on 32-bit Solaris 7 Database Edition 2.1 with Cached Quick I/O delivers up to259% of raw device OLTP performance • Tested configurationincluded: • Sun UE 10000 (16 CPUs and 6 GB of RAM) • Solaris 7 (32-bit) • DB Edition 2.1 for Oracle • Oracle 8.1.5 (32-bit) • TPC-C scale factor of 200 warehouses

17. OLTP Performance ina 64-bit Environment Quick I/O delivers equal to raw performance, while Cached Quick I/Odelivers better performance until SGA = 80% of total system memory 12000 10000 • Tested configurationincluded: • Sun UE 10000 (16 CPUs and 10 GB of RAM) • Solaris 7 (64-bit) • DB Edition 2.1 for Oracle • Oracle 8.1.5 (64-bit) • TPC-C scale factor of 200 warehouses 8000 Raw I/O Quick I/O 6000 Transactions per Minute Cached Quick I/O 4000 2000 0 10% 25% 50% 80% Oracle Buffer Cache Size (% of 10 GB memory)

18. Large I/O Optimization • VERITAS File System allocates disk space in groups of contiguous blocks or “extents” • Extent-based allocation can accelerate I/O by increasing the I/O transfer size in the file system • Optimal for large files • Large Oracle tablespaces • Binary Large Objects (BLOBs) (e.g., images, sounds)

19. Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block Disk Block VERITAS File System Inode Disk Block Disk Block Extent Addresses Disk Block Disk Block Direct Address 0 / Length Direct Address 1 / Length Direct Address 2 / Length Direct Address 3 / Length Direct Address 4 / Length Direct Address 5 / Length Direct Address 6 / Length Direct Address 7 / Length Direct Address 8 / Length Direct Address 9 / Length Single Indirect Block Double Indirect Block VERITAS File SystemExtent-based Allocation

20. Database Edition for Oracle Faster Recoverability

21. Database Edition for OracleRecoverability • Fast database recovery from system crash • Fast file system recovery through journaling • Database recovery from consistent, stable backups • File system snapshots for system and database backups • Virtually eliminate database backup window • Enables Block-Level Incremental Backup to back up only changed data blocks • Faster database recovery from logical error • Enables point-in-time recovery from on-disk image

22. Database Recovery • Database recovery begins only after file system recovery • Journaling file system minimizes database downtime • File system recovery only requires replaying the intent log • File system recovery time does not depend on file system size • Large file system (over 100 GB) usually takes only seconds to verify / recover

23. Consistent Database Backups • VERITAS File System’s snapshot mechanism • Enables system-wide backups for database and non-database files • Reduces backup time for cold database backups to a couple of seconds • Simplifies recovery process for hot database backups • Supports UNIX utilities like tar and cpio, and off-the-shelf UNIX third party solutions

24. VERITAS File System Snapshot Take a snapshot at 9 AM on Monday /oradata_snapshot /oradata • “Original” data blocks • A consistent “view” of • the file system at 9 AM • by keeping track of • changed data blocks • (“copy on write”) • Only 5-20% of original • storage required Data blocks continue to be updated

25. Shut down the database A couple of seconds of downtime Snapshot Start the database Mount snapshot file systems Perform backup Resume operation Unmount snapshot file systems Full Database Backups withFile System Snapshot • Cold database backup (or off-line backup) • Enables database access and backups in parallel • Small storage requirement (approx. 15% additional disk space)

26. Begin tablespace backup A couple of seconds of changes to apply at recovery Snapshot End tablespace backup Mount snapshot file system(s) Perform backup Hot Database Backups withFile System Snapshot • Hot database backup (or online backup) • Reduces recovery window with fewer changes to apply

27. Key Differentiator:VERITAS Storage Checkpoints • Point-in-time snapshot of database • Storage Checkpoints maintain changed data blocks as database is being updated • Uses efficient copy-on-write technique • No post-processing needed to scan forchanged data blocks

28. A B C D E Create a Storage Checkpoint Simplified illustration of creating a Storage Checkpoint Primary File System Storage Checkpoint (empty) The Storage Checkpoint presents an exact image of the primary file system.

29. A B C D E File System is Updated... Simplified illustration of a Storage Checkpoint Primary File System Storage Checkpoint Update E1 E As the primary file system is updated, the original data is copied to the Storage Checkpoint before the new data is written. As the primary file system continues to change, the Storage Checkpoint accumulates the original data blocks.

30. A B C D E and updated again.. Simplified illustration of a Storage Checkpoint Primary File System Storage Checkpoint Update C C1 E1 E And so the process continues until the next Storage Checkpoint is created.

31. Uses of Storage Checkpoints • Block-Level Incremental Backup: • NetBackup manages Storage Checkpoints and extracts only the changed blocks • Storage Rollback: • Faster database recoverability from on-disk backup image managed through VxDBA utility • Database Replication Option (available separately): • Storage Checkpoints allow for database replication to secondary system to offload primary server of maintenance tasks

32. Traditional Backup Approaches • Full backups • Shrinking backup windows • Approaches to minimize downtime • Hot database backups • Third mirror break-off • Rolling backups (full + tables) • File-level incremental backups • Poor fit for database environments • Other (block-level) incremental backups • SQL-BackTrack • Oracle8.0’s Recovery Manager (RMAN) • Our advantage: Storage Checkpoints

33. Database Edition:Block-Level Incremental Backups • Back up only changed data blocks! • Higher data availability • Virtually eliminates backup windows • Allows more frequent backup schedules • Backups contain up-to-date data • Enhanced performance • Significantly lowers CPU and network resource drain during backups • Faster recovery from backups (less redo logs to apply) • Requires NetBackup Server engine and database server to be a NetBackup client

34. Block-Level Incremental Backup NetBackup Server Changed BlocksSince LastBackup VERITAS File System with Storage Checkpoints NetBackup BLI BackupExtension Minimize Your Database Backup Window BlockLevelIncrementals PreviousFull Backup FullRestore +

35. Cold Database Backupswith Storage Checkpoints • Enables database access and backup in parallel with minimal interruption • Cold database backup (or offline backup) with a couple of seconds of downtime Shut down database A couple of seconds of downtime Storage Checkpoint Perform backup Start the database Resume operation Managed by NetBackup

36. Hot Database Backupswith Storage Checkpoints • Hot database backup (or online backup) • Reduces recovery window with fewer changes to apply Begin tablespace backup A couple of seconds of changes to apply at recovery Storage Checkpoint Perform backup End tablespace backup Managed by NetBackup

37. Storage Checkpoint at 1:00 AM /oradata • Bring the database into a consistent state A • Take a Storage Checkpoint • Resume database operation • Back up from the Storage Checkpoint • The Storage Checkpoint presents a “frozen” image of the file system B C D E F G H Full Backup withStorage Checkpoint A B C

38. /oradata A B C D E F G H A B C During Full Backup Storage Checkpoint at 1:00 AM • During backup, the database is accessible and being updated • The Storage Checkpoint continues to present a “frozen” image of the file system A’ A G’ G D E F G H

39. Storage Checkpoint at 1:00 AM /oradata A B C D E F G D’ G’ H’ A’ H After Full Backup • After the full backup, the database continues to be updated A’ A D’ D So… Which blocks have changed since the full backup? What are the changes? G’ G H’ H

40. Second Storage Checkpoint at 12:00 PM First Storage Checkpoint at 1:00 AM /oradata A’ A B C D’ D E F G’ G H’ H Block-Level Incremental Backup • Bring the database into a consistent state • Take a second Storage Chkpt • Resume database operation • Back up using the Storage Checkpoints • Before-images saved on the first Storage Checkpoint indicate which blocks have changed since the full backup • Changed data is read from /oradata D’ A’

41. Second Storage Checkpoint at 12:00 PM First Storage Checkpoint at 1:00 AM /oradata A’ A B C D’ D E F G’ G H’ H D’ A’ During Block-Level Incremental Backup • During backup, the database is being updated • Changes after 12:00 PM are saved on the second Storage Checkpoint • The second Storage Checkpoint presents a “frozen” image of /oradata at 12:00 PM • Changed data is read from the second Storage Checkpoint or /oradata C C’ D* D’ H’ H* G’ H’

42. Restore from BLI Backup • Restoring incremental image requires restoring full backup plus all incrementals to get to desired point in time. • Benefit: BLI Backup enables more frequent backups • More up-to-date backup images • Less logs to apply upon restore • Faster database recovery BlockLevelIncrementals PreviousFull Backup FullRestore +

43. Storage Rollback • Storage Checkpoints are on-disk backup images • Consistent, stable images of a file system at a particular point in time • Storage Rollback is a “restore” from the on-disk backup images or Storage Checkpoints • Copies before-images of data blocks back to the live file system • Restores without going to tapes for logical errors

44. Storage Rollback Rollback from Storage Checkpoints = Simply write back changed (blue) blocks to previous state and then apply redo logs to bring database to desired point in time Managed by VxDBA utility

45. Storage Rollback Example Second Storage Checkpoint at 12:00 PM First Storage Checkpoint at 1:00 AM /oradata Images of /oradata and its Storage Checkpoints A’ A B C’ C D* D’ D E F G’ G H* H’ H

46. Storage Rollback Example /oradata at 1:00 AM /oradata at 12:00 PM A A’ B B C C D D’ E E F F G G’ H H’

47. C D’ H’ Storage Rollback to 12:00 PM Second Storage Checkpoint at 12:00 PM /oradata /oradata at 12:00 PM A’ A’ Before-images on the 12:00 PM Storage Checkpoint are copied back to the live file system, /oradata B B C C’ C D’ D* D’ E E F F G’ G’ H’ H* H’

48. Storage Rollback to 1:00 AM Second Storage Checkpoint at 12:00 PM First Storage Checkpoint at 1:00 AM /oradata at 1:00 AM /oradata A A’ A A Before-images from 1:00 AM and 12:00 PM Storage Checkpoints are copied. B B C C C’ C D D D* D’ D E E F F G G’ G G H H H* H’ H

49. File System Snapshot Full only Transient Unaware Separate storage pool Mount empty disk Storage Checkpoint Block-level Persistent Aware of each other Shared storage pool Coordinate with Oracle states NetBackup for BLI Backup VxDBA utility for Storage Rollback Snapshot/Checkpoint Comparison

50. Database Edition for Oracle High Availability