Recovery Manager

Recovery Manager (RMAN) provides a comprehensive foundation for efficiently backing up and recovering the database. RMAN eliminates operational complexity while providing superior performance and availability of the database.

RMAN determines the most efficient method of running the requested backup, restoration, or recovery operation and then submits these operations to the Oracle AI Database server for processing. RMAN and the server automatically identify modifications to the structure of the database and dynamically adjust the required operation to adapt to the changes.

RMAN is the standard interface to backup and restore from Recovery Appliance, local disk (ZFS storage), tape, and cloud object store.

RMAN provides the following benefits:

Support for Oracle Sharding - RMAN support for every independent database (shard)
Enhancement for Sparse Databases - allows backup and restore to operate on
```
SPARSE
```
backup sets and or image copies
Over the Network Standby Database repair of
```
NONLOGGED
```
operation - new syntax for validation and repair on Standby -
```
VALIDATE/RECOVER .. NONLOGGED BLOCK;
```
```
RMAN DUPLICATE
```
feature enhanced to support creation of Far Sync from Primary and backup
```
RMAN DUPLICATE
```
Using Encrypted Backups - RMAN enhanced support non Auto-login wallet based encrypted backups with a new
```
SET
```
command - enables interrupt-free cloning
Support for cross-platform backup and restore over the network
Network-enabled restoration allows the
```
RESTORE
```
operations to copy data files directly from one database to another over the network
Simplified table restoration with the
```
RECOVER TABLE
```
command
Support for Oracle Multitenant, including backup and recovery of individual pluggable databases
Support for cross-platform Oracle Multitenant, including backup and recovery of individual PDBs
Automatic channel failover on backup and restore operations
Automatic failover to a previous backup when the restore operation discovers a missing or corrupt backup
Automatic creation of new database files and temporary files during recovery
Automatic recovery through a previous point-in-time recovery—recovery through reset logs
Block media recovery, which enables the data file to remain online while fixing the block corruption
Fast incremental backups using block change tracking
Fast backup and restore operations with intrafile and interfile parallelism
Enhanced security with a virtual private recovery catalog
Merger of incremental backups into image copies, providing up-to-date recoverability
Optimized backup and restoration of required files only
Retention policy to ensure that relevant backups are retained
Ability to resume backup and restore operations in case of failure
Automatic backup of the control file and the server parameter file, ensuring that backup metadata is available in times of database structural changes and media failure and disasters
Easily reinstantiate a new database from an existing backup or directly from the production database (thus eliminating staging areas) using the
```
DUPLICATE
```
command.