Zero Data Loss Recovery Appliance Documentation - Get Started

Looking for:

Oracle zero data loss recovery appliance.Zero Data Loss Recovery Appliance 

Click here to DOWNLOAD

   

 

- Oracle zero data loss recovery appliance

 

Would you like to continue? You will receive an email when your lab is ready. Your lab environment is ready for use, and will be available to you until hrs. Your lab environment is ready for use. All resources for labs are currently in use. Please re-try requesting for the lab later. Your environment will be available to you in the same state as you left when you connect after UTC.

You can extend your lab for another 6 days. Your current lab is active until hrs. Clicking this button before your lab ends will extend it by. Your lab has already been extended twice and is active until hrs today. We will provision a new lab environment that starts at hrs today. Do you want us to proceed? We can provision a new lab environment by UTC.

Request Lab. Not Now, Later Build Lab. Extend Lab. Yes No. Don't need this lab anymore? Release Lab. Planned maintenance outage notification. Facing an issue? Report here. Describes Oracle Database licensing. If you have a question about your licensing needs, contact your Oracle sales representative, or refer to the resources listed in "Related Documents" for more information. Secure Backup Licensing Information. Licensing information for Oracle Secure Backup The Recovery Appliance elastic configuration starts with a "Base Rack" that can be incrementally increased to a "Full Rack" or larger "multi-rack" configurations.

A Base Rack is capable of managing over terabytes of backup data, while a Full Rack can manage over 1. Multi-Rack configurations of up to 18 racks wide can manage more than 22 petabytes of data. From Wikipedia, the free encyclopedia. A major contributor to this article appears to have a close connection with its subject. It may require cleanup to comply with Wikipedia's content policies, particularly neutral point of view.

Please discuss further on the talk page. Licensing Licensing Information. PDF for offline viewing. Database Licensing Information. Describes Oracle Database licensing.

 

Oracle zero data loss recovery appliance.Zero Data Loss Recovery Appliance 21.1

 

In Figure , a protected database sends an incremental backup to the Recovery Appliance, which then queues it for replicating to the downstream Recovery Appliance. When the upstream Recovery Appliance sends the incremental backup to the downstream Recovery Appliance, it creates a virtual full backup as normal.

The downstream Recovery Appliance creates backup records in its recovery catalog. When the upstream Recovery Appliance requests the records, the downstream Recovery Appliance propagates the records back. If the local Recovery Appliance cannot satisfy virtual full backup requests, then it automatically forwards them to the downstream Recovery Appliance, which sends virtual full backups to the protected database.

A robust backup strategy protects data against intentional attacks, unintentional user errors such as file deletions , and software or hardware malfunctions. Tape libraries provide effective protection against these possibilities. Figure show the traditional technique for tape backups, with a media manager installed on each host.

Figure shows the Recovery Appliance technique for tape backups. The fundamental difference in the two approaches is that the Recovery Appliance backs up to tape, not the protected databases. Thus, installation of a media manager is not necessary on the protected database hosts. When Recovery Appliance executes a copy-to-tape job for a virtual full backup, it constructs the physical backup sets, and copies them to tape, and then writes the metadata to the recovery catalog.

If desired, the Recovery Appliance can also copy successive incremental backups and archived redo log file backups to tape. Whereas the backup on the Recovery Appliance is virtual, the backup on tape is a non-virtual, full physical backup. The Recovery Appliance automatically handles requests to restore backups from tape, with no need for administrator intervention. The Recovery Appliance performs all tape copy operations automatically, with no performance load on the protected database host.

Tape backups are optimized. Recovery Appliance intelligently gathers the necessary blocks to create a non-virtual, full backup for tape.

Oracle Secure Backup is preinstalled, eliminating the need for costly third-party media managers. You may deploy tape backup agents from third-party vendors on the Recovery Appliance for integration with existing tape backup software and processes.

In this configuration, the agents must connect to their specialized media servers, which must be deployed externally to the Recovery Appliance. Tape drives and tape libraries function more efficiently because Recovery Appliance is a single large centralized system with complete control over them.

In other tape solutions, hundreds or thousands of databases can contend for tape resources in an uncoordinated manner. Copying Backups to Tape with Recovery Appliance.

Oracle Secure Backup Administrator's Guide. A basic principle of backup and recovery is to ensure that backups can be restored successfully.

To ensure that there are no physical corruptions within the backed-up data blocks, backups require regular validation. Recovery Appliance provides end-to-end block validation, which occurs in the following stages of the workflow:. The Recovery Appliance automatically validates the backup stream during the backup ingest phase, before writing the backups to disk. The Recovery Appliance also validates the backup before sending it back to the original or alternate database server during the restore phase.

In addition, a background task running on the Recovery Appliance periodically validates the integrity of the virtual full backups in the delta pools see " Delta Pools ". The goal of this task is to check each block of each virtual full backup of each protected database and to work behind the scenes when minimal activity is occurring. Just as with data file backups, the Recovery Appliance validates the integrity of redo log blocks during every operation, including receiving redo from the protected database, and storing it in compressed archived log backup sets.

If a corrupted block is read on the primary mirror, the Recovery Appliance automatically repairs the block from the mirrored copy. This mechanism resolves most isolated block corruption cases. Recovery Appliance validates blocks when it copies them to tape, and also when it restores them from tape see " Tape Archival ".

If you configure replication, then the downstream Recovery Appliance validates data during the backup ingest and restore phases see " How a Downstream Recovery Appliance Processes Backups ". None of the preceding backup validation processes occur on the production database hosts, thus freeing production resources for more critical operational workloads. Oracle Maximum Availability Architecture best practices recommend that you still perform periodic full database recovery tests to verify operational practices and to detect issues that might occur only during media recovery.

In " Traditional Database Backup Techniques " , the Oracle database host performs the brunt of the processing. Agents for disk backup, tape backup, and deduplication may all be running on the host. Furthermore, all backup operations—compression, validation, deletion, merging, and so on—occur on the database host. This overhead can greatly degrade database performance.

Recovery Appliance removes almost the entire load from the protected databases. The only backup operations required on the hosts, which could be primary database or standby database hosts, are sending incremental backups to the Recovery Appliance.

The incremental-forever strategy reduces the backup window on the database hosts significantly. Recovery Appliance handles backup processing, tape operations, data integrity checks, and routine maintenance. Recovery Appliance only supports backups of Oracle databases, not file system data or non-Oracle databases.

Recovery Appliance optimizes management of database changes using delta push and delta store , shown in Figure The net result of delta push and delta store is that the problem of lengthening backup windows is eliminated.

The DBA performs only fast incremental backups, and lets the Recovery Appliance manage the backup blocks. This solution consists of two operations that run on each protected database: the incremental-forever backup strategy, and real-time redo transport described in " Elimination of Data Loss ". Both operations involve protected databases pushing changes to the Recovery Appliance. In an incremental-forever strategy, only one incremental level 0 backup to the Recovery Appliance is required in the lifetime of each protected file.

The initial level 0 backup does not contain committed undo blocks or currently unused blocks. The elimination of committed undo and currently unused blocks is only supported for SBT full backups to the Recovery Appliance or Oracle Secure Backup. It is not available for SBT backups to other backup products. In normal operation, the Recovery Appliance automatically performs the following steps for each incremental level 1 backup:. The incremental-forever strategy greatly reduces the backup window and overhead because no full backups are ever required after the initial incremental level 0 backup.

If the strategy includes real-time redo transport, then backup windows are further reduced because traditional archived log backups are not necessary.

Also, Recovery Appliance takes on the burden of validation, deduplication, and compression. The delta store is the key processing engine for Recovery Appliance.

A protected database sends only one incremental level 0 backup of each data file to the Recovery Appliance. Following the initial full backup, all backups are highly efficient cumulative incremental backups. As Recovery Appliance receives incremental backups, it indexes them and stores them in delta pools. Each separate data file backed up to the Recovery Appliance has its own separate delta pool set of backup blocks.

Recovery Appliance automatically manages the delta pools so that it can provide many virtual full backups. To create a virtual full backup, Recovery Appliance converts an incoming incremental level 1 backup into a virtual representation of an incremental level 0 backup.

A virtual full backup appears as an incremental level 0 backup in the recovery catalog. From the user's perspective, a virtual full backup is indistinguishable from a non-virtual full backup. Using virtual backups, Recovery Appliance provides the protection of frequent level 0 backups with only the cost of frequent level 1 backups. These backups are stored in their original encrypted format.

Recovery Appliance can store, archive, and retrieve them just as it can for unencrypted RMAN backup sets. Recovery Appliance uses virtual full backups to provide rapid recovery to any point in time, regardless of the amount of data being recovered.

The on-disk recovery strategy of Recovery Appliance has the advantage that RMAN can recover virtual full backups to any point in time without applying incremental backups. When a database is protected by the Recovery Appliance, RMAN must only restore a single level 0 backup for the day of the RPO, and then recover up to the last second using redo log files sent using the real-time redo transport feature.

For example, if the recovery window is 7 days, and if the RPO is 5 days ago, then RMAN can restore a single virtual full level 0 backup that is current to 5 days ago, and then recover it using redo—not level 1 incremental backups.

In " Traditional Database Backup Techniques " , management of the database, media server, and tape drives are often separated. For example, a DBA group may manage the databases, while a separate backup administrator group manages the backups, and a storage group manages the disk and tape devices.

The overall process lacks visibility, which makes it difficult to manage backups for thousands of databases, each with different recovery requirements.

Cloud Control provides a complete, end-to-end view into the backup lifecycle managed by the Recovery Appliance, from the time the RMAN backup is initiated on the database, to when it is stored on disk, tape, or replicated to a downstream Recovery Appliance.

Standard metrics such as overall backup performance, and aggregate or per-database space consumption. For example, Cloud Control may alert the administrator if no backup is available to meet the defined RPO, or if corrupt backups are discovered.

Status reports, enabled by BI Publisher, are useful for capacity planning and to identify protected databases that are not meeting recovery window goals. For example, Recovery Appliance administrators can receive reports on historical space and network usage to identify backup volume and throughput trends. These trends may necessitate adding storage servers to an existing rack or connecting additional racks. For command-line monitoring and reporting, you can query the Recovery Appliance catalog views see Recovery Appliance View Reference.

Recovery Appliance scales at a cloud level, supporting tens to hundreds to thousands of databases across a data center. Essentially, Recovery Appliance enables you to create a private data protection cloud within the enterprise.

The following technology components within Recovery Appliance make this possible:. Policy-Based Data Protection Management. Database-Aware Space Management. Recovery Appliance simplifies management through the protection policy. Benefits include the following:.

A protection policy defines recovery window goals that are enforced for each database for backups to the Recovery Appliance or a tape device. Using protection policies, you can group databases by recovery service tier.

For example, databases protected by the Platinum policy require backups to be kept for 45 days on the Recovery Appliance and 90 days on tape, which means that backups aged 45 days or less exist on disk and tape, but backups older than 45 days are only on tape.

Databases protected by the Gold policy require 35 days on the local Recovery Appliance and 90 days on tape. Optionally, you can define a maximum retention time within each policy to limit the space consumed, and to comply with service level agreements dictating that backups cannot be maintained for longer than a specified period.

For example, you can configure Recovery Appliance replication or copy-to-tape for a specific protection policy, which means that the configuration applies to all databases associated with this policy. If you add a database to the policy, then the database automatically inherits the configurations and scheduling of the policy. Managing Protection Policies with Recovery Appliance.

Using protection policies, the Recovery Appliance manages backup storage space according to the recovery window goal for each protected database. This granular, database-oriented space management approach eliminates the need to manage space at the storage-volume level, as third-party appliances do. If space is available, then the Recovery Appliance may retain backups older than the recovery window goal, effectively extending the point-in-time recovery period.

When space pressure exists, the Recovery Appliance uses predefined thresholds to purge backups. The Recovery Appliance automatically provisions space so that the recovery window goal for each database is met. The approaches in " Traditional Database Backup Techniques " are prone to performance bottlenecks and multiplying points of failure.

As the number of databases increases, so does the number of media servers, disk arrays, tape devices, and third-party appliances, and thus so does the overall complexity.

The "add more devices" approach is not scalable. In contrast, Recovery Appliance can scale to accommodate increases in backup traffic, storage usage, and the number of databases by adding compute and storage resources in a simple, modular fashion. Oracle Data Guard is a component of a high availability HA and disaster recovery solution that can be integrated with Recovery Appliance to provide maximum data protection.

Oracle Data Guard minimizes service interruption and resulting data loss by maintaining a synchronized standby database for the protected database. When the primary system is unavailable, the standby immediately assumes the normal operations of the primary after a Data Guard failover operation, including backups to the local Recovery Appliance.

In Figure , the primary and standby databases each send incremental backups to their local Recovery Appliance. The primary database sends real-time redo changes to both the local Recovery Appliance and the physical standby, and the standby cascades the redo changes to the remote Recovery Appliance. Each Recovery Appliance has backups and redo information for the same database, therefore either appliance can be used for RMAN restore and recovery operations.

Optionally, read Recovery Appliance Architecture to obtain a more in-depth understanding of the principal components of the Recovery Appliance environment. Read Recovery Appliance Workflow to learn about basic tools and tasks.

Before you can use Recovery Appliance for data protection, you must perform the tasks described in the following topics:. If you have a question about your licensing needs, contact your Oracle sales representative, or refer to the resources listed in "Related Documents" for more information. Secure Backup Licensing Information. Licensing information for Oracle Secure Backup Release Notes Release Notes. Deployment Owner's Guide.

Describes data center site planning, network configuration, hardware and software installation, and maintenance of Oracle's Recovery Appliance. Safety and Compliance Guide. PDF for offline viewing. Administration Administrator's Guide.