Managing multiple archive log destinations with RMAN
(Doc ID 443814.1)
Last updated on JANUARY 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
Explain how multiple archive destinations are handled during an RMAN backup and restore process
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| For the purposes of this document, the following fictitious environment is used as an example to describe the procedure: |
| DELETE INPUT |
| Backup and Delete from a Specified Archive Destination |
| The FRA and DELETE INPUT |
| Where do the restored archivelogs go? |
| Restoring archivelog to FRA in ASM |