Migrating Backup Metadata to the Recovery Appliance Catalog
Your existing RMAN backup strategy typically involves storing backup metadata in an RMAN recovery catalog. When migrating to a data protection strategy that uses Recovery Appliance, you need a strategy to manage existing backup metadata that is stored in an RMAN recovery catalog.
See Also:
-
Zero Data Loss Recovery Appliance Administrator's Guide for information about the Recovery Appliance catalog
-
Oracle Database Backup and Recovery User's Guide for more information about the RMAN recovery catalog
To manage existing backup metadata while moving to Recovery Appliance, use one of the following strategies:
-
Import existing backup metadata for your protected database into the Recovery Appliance catalog
Importing backup metadata stored in an RMAN recovery catalog ensures that existing backup metadata for your protected databases is now contained in the Recovery Appliance catalog.
-
Retain existing backup metadata in the RMAN recovery catalog and store metadata for backups created to Recovery Appliance in the Recovery Appliance catalog
You must manage the RMAN recovery catalog in conjunction with the Recovery Appliance catalog. To create local backups and store the backup metadata in the RMAN recovery catalog, use the steps described in "Creating Local Backups". To create backups to a Recovery Appliance, configure the protected database and then back up to the Recovery Appliance.