The figure illustrates the components of RMAN:

1. RMAN Executable: This is an executable file similar to the EXP.exe export file and also the IMP.exe import file. When you run this file, it opens a window where you can type <RMAN>, allowing it to accept the commands you write, which it then converts into a series of steps executed on the target database.
2. Target Database: This is the target database where we want to create a backup using RMAN.
3. RMAN Repository: This stores all information about backup and recovery operations, as well as data about the target database and its structure. It also retains RMAN Configuration Settings. The RMAN Repository is permanently stored in the Control File of the target database, but it is important to note that the duration for which backup information is retained in the Control File depends on the CONTROL_FILE_RECORD_KEEP_TIME variable, which contains the number of days for retaining backup information before the same fields are reused for writing new data.
4. Recovery Catalog: Note that the backup information retained in the Control File is temporary data. If we lose the Control File in the target database, we would lose this information. Therefore, Oracle provides another option to retain this data, which is to keep the RMAN Repository in another database called the Recovery Catalog. RMAN scripts are also stored in it.
5. Flash Recovery Area: This refers to a space on the disk that is managed by Oracle, where backup files are stored. This space is managed through Oracle, and its location is specified by the DB_RECOVERY_FILE_DEST variable. The size of this space is specified by the DB_RECOVERY_FILE_DEST_SIZE variable. Managing this space includes determining the retention period for backup files, deleting old expired files, and increasing the size of this space as needed, among other management actions.
6. Enterprise Manager: Previously, there was a problem writing code for backup and recovery operations and managing the Recovery Flash Area. However, Oracle provides a user interface to solve this problem, which is the Enterprise Manager, allowing you to perform all tasks without writing any code.
7. Auxiliary Database: This refers to a database created using RMAN, which is a copy of the target database used for various purposes, including testing operations since tests cannot be conducted on the original database. Additionally, sometimes it is needed for Tablespace Point-in-Time Recovery, which involves reverting the Tablespace without affecting the target database.
8. Channel: This is a work session through which backup and recovery operations are performed. Channels can be created manually by writing code or automatically through RMAN configuration.
9. Media Management Library (MML): RMAN can send backup files to disk or to MML, a program used by RMAN to send files to tape.