Oracle Secure Backup is centralized tape backup management software protecting the Oracle database and file systems in distributed UNIX, Linux, Windows and Network Attached Storage (NAS) environments.
From one central console, you can easy manage the distributed servers and tape devices within the backup domain.
As Oracle is no longer just a database company, Oracle Secure Backup provides tape backup for application files as well as the database. Integrated with Recovery Manager (RMAN), Oracle Secure Backup provides the media management layer for RMAN backups to tape.
While tightly integrated with the Oracle database, Oracle Secure Backup is a standalone product offering with an independent release schedule and versioning from the database. OSB 10.1 was released in April 2006 and OSB 10.2 was released in Nov 2007.
3rd Party Media Management Software can be EXPENSIVE, and cost thousands per database server for RMAN integration!
Oracle – Single vendor solution with RMAN+OSB reduces complexity
Oracle Secure Backup delivers the fastest Oracle database backup to tape! As part of the “Oracle product family”, Oracle Secure Backup has intimate access and integration with Recovery Manager (RMAN) not available outside of Oracle. Two key performance optimizations using Oracle Secure Backup 10.2 and Oracle Database 11g are:
Eliminates backup of committed undo increasing backup performance and reducing tape consumption. Only non-committed undo will be backed up.
Optimizes SBT buffer allocation using a shared buffer between SBT and tape (OSB). In past versions, RMAN writes data to the SBT buffer then the media manager copies data from the SBT buffer to the tape buffer. Using a shared buffer (OSB and RMAN only) reduces CPU overhead by up to 30% in internal tests.
Please note: These Oracle Secure Backup 10.2 and Recovery Manager 11g performance optimizations are not available with 3rd party media management utilities.
In addition to Oracle database backup performance enhancements, Oracle Secure Backup 10.2 has strengthened the data transfer architecture achieving faster performance over that of OSB 10.1 for file system and networked backups. Users are now able to explicitly define TCP/IP buffer size sending larger packet sizes over the network (as desired) further increasing remote backup performance.
Defining what data to backup is conceptually similar for file system and database data. For the database, RMAN backup sets are created. For file system data, the user defines “datasets” which describes the list of files to be backed up. A dataset is a textual description employing a lightweight language to communicate how to build and organize files to be protected.
The Oracle Secure Backup dataset language provides a simple, text-based means to define file system data that you want Oracle Secure Backup to back up. The language has the following characteristics:
Comments can appear anywhere following a pound sign (#).
Dataset statements use the following syntax:
statement-name [ statement-argument ] The statement-name placeholder represents a dataset statement. These statements are described in “Dataset Statements”.
Some statements can begin a nested block. Statements within the block apply only to the statement that began the block. Nested block statements have the following form:
statement-name [ statement-argument ] { statement-name [ statement-argument ] … }
An escape character, which is represented by a backslash (\), can appear anywhere to remove the special meaning of the character following it.
Blank lines are ignored.
OSB employs a client / server architecture:
One Admin. Server per domain – houses OSB catalog
Client host – Any host backed up by OSB
Media server – Any host direct attached to tape device
OSB domain – all hosts that are managed by admin server….graphic above would represent one OSB domain.
Oracle database may reside on any host within the OSB domain.
Local backups generally faster than network ed since backup doesn’t have to contend with other network traffic. OSB supports both….generally when possible if a high amount of data make that a local backup (on media server)…..not OSB requirement just general guidance.
RAC — Can be backed up over network or direct attached to tape drives…For local backups, one or mode nodes of RAC may be direct attached. For example, GIT has an 8 node RAC and they leverage only two of those nodes for the backup which those two nodes are direct attached to tape drives (OSB media servers).
© 2010, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- RMAN Performance Tuning Using Buffer Memory Parameters
- Oracle Secure Enterprise Search DB11g Web Seminar
- How to Minimise the impact of an Online RMAN Backup on an OLTP system
- undo backup optimization does not work on 11.2.0.1?
- RMAN 11G : Data Recovery Advisor – RMAN command line example
- A Complete Understanding of RMAN Compression
- CLOUD JUST GOT CLEARER LEVERAGING AN ALL ORACLE STACK TO RAPIDLY DEPLOY A SECURE,VIRTUAL ENVIRONMENT
- How to Make Use of Oracle's Data Compression with Materialized Views.
- Oracle Database 11g Transparent Data Encryption
- Storage Portfolio:Oracle is a Storage Company
最新评论