EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC ...

More documents

Recommendations

Info

Chapter 3: Storage Design The LUNs used for the clone copies were configured in a similar fashion to the source copy to maintain the required throughput during the backup process. The image below shows the clone relationship for two of the metaLUNs. EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC CLARiiON, EMC Data Domain, EMC NetWorker, and Oracle Recovery Manager using NFS Proven Solution Guide 22
Chapter 3: Storage Design Data Domain Overview The following sections describe how Data Domain systems ensure data integrity and provide multiple levels of data compression, reliable restorations and multipath configurations. The Data Domain operating system (DD OS) Data Invulnerability Architecture protects against data loss from hardware and software failures. Data integrity When writing to disk, the DD OS creates and stores checksums and self-describing metadata for all data received. After writing the data to disk, the DD OS then recomputes and verifies the checksums and metadata. An append-only write policy guards against overwriting valid data. Data compression After a backup completes, a validation process looks at what was written to disk to see that all file segments are logically correct within the file system and that the data is the same on the disk as it was before being written to disk. In the background, the Online Verify operation continuously checks that data on the disks is correct and unchanged since the earlier validation process. The back-end storage is set up in a double parity RAID 6 configuration (two parity drives). Additionally, hot spares are configured within the system. Each parity stripe has block checksums to ensure that data is correct. The checksums are constantly used during the online verify operation and when data is read from the Data Domain system. With double parity, the system can fix simultaneous errors on up to two disks. To keep data synchronized during a hardware or power failure, the Data Domain system uses NVRAM (non-volatile RAM) to track outstanding I/O operations. An NVRAM card with fully-charged batteries (the typical state) can retain data for a minimum of 48 hours. When reading data back on a restore operation, the DD OS uses multiple layers of consistency checks to verify that restored data is correct. DD OS stores only unique data. Through Global Compression, a Data Domain system pools redundant data from each backup image. Any duplicate data is stored only once. The storage of unique data is invisible to backup software, which sees the entire virtual file system. DD OS data compression is independent of data format. This can be structured, for example, databases, or unstructured, for example, text files. Data can be from file systems or raw volumes. Typical compression ratios are 20:1 on average over many weeks. This assumes weekly full and daily incremental backups. A backup that includes many duplicate or similar files (files copied several times with minor changes) benefits the most from compression. Depending on backup volume, size, retention period, and rate of change, the amount of compression can vary. Data Domain performs inline deduplication only. Inline deduplication ensures: • Smaller footprint • Longer retention • Faster restore • Faster time to disaster recovery EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC CLARiiON, EMC Data Domain, EMC NetWorker, and Oracle Recovery Manager using NFS Proven Solution Guide 23
Page 1 and 2: EMC Backup and Recovery for Oracle
Page 3 and 4: Table of Contents Table of Contents
Page 5 and 6: Chapter 1: About this Document Audi
Page 7 and 8: Chapter 1: About this Document Obje
Page 9 and 10: Chapter 1: About this Document Vali
Page 11 and 12: Chapter 1: About this Document Prer
Page 13 and 14: Chapter 2: Use Case Components Chap
Page 15 and 16: Chapter 2: Use Case Components EMC
Page 17 and 18: Chapter 3: Storage Design Chapter 3
Page 19 and 20: Chapter 3: Storage Design The follo
Page 21: Chapter 3: Storage Design EMC SnapV
Page 25 and 26: Chapter 3: Storage Design SAN topol
Page 27 and 28: Chapter 3: Storage Design 10 GbE ne
Page 29 and 30: Chapter 4: Oracle Database Design C
Page 31 and 32: Chapter 4: Oracle Database Design S
Page 33 and 34: Chapter 5: Installation and Configu
Page 63 and 64: Chapter 6: Testing and Validation C
Page 65 and 66: Chapter 6: Testing and Validation O
Page 67 and 68: Chapter 6: Testing and Validation M
Page 69 and 70: Chapter 6: Testing and Validation T
Page 71 and 72: Chapter 6: Testing and Validation T
Page 73 and 74:
Chapter 6: Testing and Validation L
Page 75 and 76:
Chapter 6: Testing and Validation Y
Page 77 and 78:
Chapter 7: Conclusion • Efficient
Page 79 and 80:
Appendix A: Scripts NetWorker RMAN
show all

EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC ...

Create successful ePaper yourself

Delete template?

Save as template?