Storage Edition for Oracle Storage Management Software Suite

Storage Edition for Oracle Storage Management Software Suite for Oracle Databases on HP Servers Melissa Stein Product Management October 1999

Agenda VERITAS Product Overview DBA’s Challenges VERITAS Storage Edition for Oracle t Enhanced Performance t High Availability t Faster Recoverability t Improved Manageability Summary 2

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

Storage Edition for Oracle VERITAS Storage Edition for Oracle enables database administrators to manage Oracle 7 and Oracle 8 environments with the flexibility of file systems at raw disk performance. Its data redundancy techniques and online administration features increase data reliability and availability. Storage Edition for Oracle enables DBAs to meet their top priorities: optimal performance, availability, recoverability, and manageability of databases 4

Storage Edition 2. 0 Architecture Integration of online and offline storage management Oracle Storage Edition for Oracle Vx. DBA Utility Net. Backup Block-level Incremental Backup Extension VERITAS File System with Quick I/O & Storage Checkpoints 5

Feature Overview Quick I/O t Raw device performance with File System manageability Asynchronous I/O support Online administration of database storage Storage Checkpoints t Enable Block-level Incremental Backup t Enable Storage Rollback for immediate “point -in-time” recovery from on-disk images HP-UX 11. 0 support 6

Storage Edition for Oracle Enhanced Performance

Storage Edition for Oracle Performance Increased performance t increased productivity Equal to raw device performance using Quick I/O Large I/O optimization t Accelerated I/O performance for large files (e. g. , video, images) 8

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

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

Raw Disk Performance Quick I/O Database Accelerator Break-through VERITAS File System interface technology Presents regular VERITAS File System files to Oracle as raw character devices Quick I/O regular raw file device Oracle Server t Allows parallel updates to database files for increased throughput t Oracle handles locking for data integrity Eliminates traditional UNIX file system overhead t Removes single-writer lock at file level t Bypasses redundant data buffering 11

Quick I/O Performance Comparison to Raw I/O Storage Edition has equal to raw performance t 160% performance improvement over traditional file systems Tested configuration included: • HP K 570 (4 CPUs and 1 GB of RAM) • HP-UX 11. 0 (64 -bit) • Storage Edition 2. 0 for Oracle • Oracle 8. 0. 5 (64 -bit) • TPC-C scale factor of 100 warehouses 12

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 t Large Oracle tablespaces t Binary Large Objects (BLOBs) (e. g. , images, sounds) 13

VERITAS File System Extent-based Allocation Disk Block Disk Block Disk Block Disk Block Veritas File Systm Inode Extent Addresses 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 14

Storage Edition for Oracle High Availability

The Need for High Availability Many factors contribute to potential downtime t Software t Hardware t People t Planned downtime (for maintenance tasks) Downtime impacts business operations Revenue, customer service, and productivity at risk 16

Financial Impact of System Failure Application Industry Average Hourly Cost Brokerage Operations Finance $6. 45 Million Credit Card/Sales Auth. Finance $2. 6 Million Pay-per-View Media $150 Thousand Home Shopping (TV) Retail $113 Thousand Catalog Sales Retail $90 Thousand Airline Reservations Transportation $89. 5 Thousand Tele-Ticket Sales Media $69 Thousand Package Shipping Transporation $28 Thousand ATM Fees Finance $14. 5 Thousand Source: Contingency Planning Research 17

Storage Edition for Oracle Availability Online administration t Storage reconfiguration and maintenance without downtime Automated, proactive monitoring of file system to avoid unexpected “out-of-space” conditions 18

Online Administration Enables DBAs and system administrators to meet changing database storage requirements without database downtime t Supports online tablespace growth • Online resizing of file systems t Allows database storage reconfiguration • Defragmenting mounted file systems 19

Online Administration Example Extend a file system t t t Locate new disk space Create a new file system Stop work Copy files to the file system Resume work Select “resize a file system” from a menu t Enter the new file system size è No interruption to users or applications t 20

Intelligent File System Control Policy driven File Management t Why ? • Lack of file system free space can cause REACTIVE widespread application failure t How ? • Included Agent monitors average available free space of VERITAS File System • If average free space falls below threshold set by the administrator, the agent will automatically grow PROACTIVE the File System and underlying volume if need be to enforce free space policy t Configured via Vx. DBA utility 21

Storage Edition for Oracle Faster Recoverability

Storage Edition for Oracle Recoverability Fast database recovery from system crash t Fast file system recovery through journaling Database recovery from consistent, stable backups t File System snapshots for system and database backups Virtually eliminate database backup window t Enables block-level incremental backup to back up only changed data blocks Faster database Recovery from logical error t Enables point-in-time recovery from on-disk image 23

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

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

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

Full Database Backups with File System Snapshot Cold database backup (or off-line backup) A couple of seconds of downtime Shutdown the database Snapshot Start the database Mount snapshot file system(s) Resume operation Perform backup Unmount snapshot file system(s) t Enables database access and backups in parallel t Small storage requirement (approx. 15% additional disk space) 27

Hot Database Backups with File System Snapshot Hot database backup (or on-line backup) t Reduces recovery window with fewer changes to apply A couple of seconds of changes to apply at recovery Begin tablespace backup End tablespace backup Snapshot Mount snapshot file system(s) Perform backup 28

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

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

and update the filesystem Simplified illustration of initializing a storage checkpoint Primary File System Storage Checkpoint A B C D E 1 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 31

and again. . Simplified illustration of initializing a storage checkpoint Primary File System Storage Checkpoint A B C 1 C D E 1 E And so the process continues until the next checkpoint is created 32

Benefits of Storage Checkpoints Block-Level Incremental Backup: t Net. Backup manages Storage Checkpoints and extracts only the changed blocks Storage Rollback: t Vx. DBA utility manages Storage Checkpoints for faster database recoverability from on-disk backup image 33

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

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

Block-Level Incremental Backup Changed Blocks Since Last Backup VERITAS File System with Storage Checkpoints Net. Backup Server Net. Backup BLI Extension Minimize Your Database Backup Window Previous Full Backup + Block Level Incrementals Full Restore 36

Cold Database Backups with Storage Checkpoints Enables database access and backup in parallel with minimal interruption Cold database backup (or off-line backup) with a couple of seconds of downtime A couple of seconds of downtime Shutdown database Storage Checkpoint Start the database Perform backup Resume operation Managed by Net. Backup 37

Hot Database Backups with Storage Checkpoints Hot database backup (or on-line backup) t Reduces recovery window with fewer changes to apply Begin tablespace backup A couple of seconds of changes to apply at Storage Checkpoint recovery End tablespace backup Perform backup Managed by Net. Backup 38

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

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

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

Block-Level Incremental Backup /oradata A’ Second First storage checkpoint at 1: 00 AM 12: 00 PM A B C D’ D E F G’ G H’ H • 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 A’ D ’ 42

During Block-Level Incremental Backup /oradata A’ Second First storage checkpoint at 1: 00 AM 12: 00 PM A B C C’ D* D’ C D’ D E F G’ H’ H* G H’ H • 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 A’ D G’ H ’ ’ 43

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 Previous Full Backup + Block Level Incrementals Full Restore 44

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

Storage Rollback Recovery 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 46

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

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’ 48

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

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

The Time Line Difference Between Storage Rollback and BLIB Restore 6: 00 am 9: 00 am Storage Checkpoint BLIB 11: 00 am 1: 00 pm OOPS! File Lost 3: 00 pm Storage Rollback 51

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

Storage Edition for Oracle Improved Manageability

Storage Edition for Oracle Manageability Familiar file system administration for Oracle database files t Combines raw I/O performance and ease of file system management Large database configuration support t Supports large file systems to simplify management Guide to simplify administration of database storage Integration with familiar System Administration Manager (SAM) interface 54

Ease of File System Management Administrative comforts t Familiar naming conventions and utilities to manage Oracle database files t Datafiles can be grouped together for storage hierarchy t Common backup strategies for database and non-database files 55

Large Database Configuration Support Storage Edition can support file systems up to 2 TB in size File system sizes are not limited to underlying device sizes t No longer need to manage multiple file systems per database t Online resizing further simplifies file system management 56

Database Administrator’s Guide Cookbook for setting up and tuning database environments Tailored for DBAs to optimize database storage layouts t Presents various storage configuration options t Recommends optimal configurations specific to database application workloads 57

Storage Edition 2. 0 for Oracle Summary Enhanced Performance t Raw disk performance with ease of file system management t Increased throughput for OLTP applications High Availability t Proactive, automated file system monitoring agent t Increased data reliability and availability for missioncritical databases t Online administration t Fast database backup and recovery Improved Management t Simplified administration for large databases t Simplified management through SAM integration 58

Supported Platforms HP-UX 11. 0 support Passed MC/Service. Guard compatibility testing Oracle 7 and Oracle 8 t Support for Oracle 8 i planned t ORACLE CERTIFIED 59

Storage Edition for Oracle Performance Availability Users Recoverability Network Manageability End-User Applications VERITAS Storage Edition for Oracle HP SAM GUI FS Agent Net. Backup BLIB Ext. Applications Oracle Server VERITAS File System + Quick I/O Operating System HP Logical Volume Manager Disks 60

Business Without Interruption 61