A basic backup strategy involving Recovery Manager (RMAN) consists of a set of backup scripts that are scheduled to run at specified intervals. When you decide to use Recovery Appliance for data protection, you need to develop a plan to migrate your existing backup strategy to one that uses Recovery Appliance.

This section provides a high-level overview of the tasks involved in migrating your existing protected database backup strategy to Recovery Appliance. Details about how to perform each task are provided in the following sections.

If you are starting with Recovery Appliance for your protected database's data protection, then skip to Configuring Protected Databases.

1. Adapt the existing backup strategy for Recovery Appliance

   All RMAN commands, with the exception of those listed in Unsupported RMAN Commands will work with Recovery Appliance. You must make some changes to your existing RMAN backup strategy to adapt it for Recovery Appliance.

   See Also:

   "Adapting an Existing Backup Strategy for Recovery Appliance"

2. Migrate backup metadata to the Recovery Appliance catalog

   Your existing backup strategy may be using an RMAN recovery catalog to store backup metadata for the protected database. You can migrate existing backup metadata for your protected database to the Recovery Appliance catalog.

   See Also:

   "Migrating Backup Metadata to the Recovery Appliance Catalog"

3. Migrate existing protected database backups to the Recovery Appliance

   You can migrate valid database backups that are within the configured recovery window goals to the Recovery Appliance. Alternately, you can start backing up to the Recovery Appliance without migrating existing protected database backups.

   See Also:

   "Migrating Existing Backups to Recovery Appliance"