Oracle Exadata Storage Server Architecture: Impossible To Back Up?

Too Large To Back Up?
If it is possible to back up a large data warehouse at rates of over 11 TB/h for full backup and more than 100 TB/h for incremental backups, maybe not!

The Maximum Availability Architecture (MAA) team has just published a paper covering tape backup of the HP Oracle Database Machine. The conclusion reads:

With the Exadata Storage Server, Oracle provides an architecture that allows customers with large databases to scale their tape backup to any desired peformance level. The number and connectivity of media servers, and the number and speed of tape drives will define the performance limit of backup, not the Database Machine. With two media servers, effective full backup rates from 11.2 TB/hour and effective incremental backup rate of over 104 TB/hour were achieved.

The title of the paper is Tape Backup Performance and Best Practices for Exadata Storage and the HP Oracle Database Machine and the paper can be accessed at the following link:

Tape Backup Performance and Best Practices for Exadata Storage and the HP Oracle Database Machine

2 Responses to “Oracle Exadata Storage Server Architecture: Impossible To Back Up?”


  1. 1 Harel July 8, 2009 at 2:19 am

    Though impressive, how fast can you back up to real drives?

    “…Instead of using physical tapes, virtual tapes were configured to backup to /dev/null…”

    • 2 kevinclosson July 8, 2009 at 5:21 pm

      I don’t know…I wasn’t on the project. The point of the paper is to show that as long as you have enough tape device bandwidth, you’ll be able to feed it. At least that is how I interpret the message.


Leave a Reply




Disclaimer

The views expressed on this blog are my own and do not reflect the views of Oracle Corporation. The views and opinions expressed by visitors on this blog are theirs, not mine.
All information and materials provided here are provided "as-is"; Oracle disclaims all express and implied warranties, including, the implied warranties of merchantability or fitness for a particular use. Oracle shall not be liable for any damages, including, direct, indirect, incidental, special or consequential damages for loss of profits, revenue, data or data use, incurred by you or any third party in connection with the use of this information or these materials.
website metrics