RMAN Architecture

Recovery Manager (RMAN) is a client application that performs backup and recovery operations. 

Components of the RMAN Environment:

Component	Description	Required?
Target database	The control files, datafiles, and optional archived redo logs that RMAN is in charge of backing up or restoring. RMAN uses the target database control file to gather information about the database and to store information about its own operations. The actual work of the backup and recovery jobs is performed by server sessions on the target database.	Yes
RMAN executable	The client application that manages backup and recovery operations for a target database. The RMAN client uses Oracle Net to connect to a target database, so it can be located on any host that is connected to the target host through Oracle Net.	Yes
Recovery catalog database	A database containing the recovery catalog schema, which contains the metadata that RMAN uses to perform its backup and recovery operations.	No
Recovery catalog schema	The user within the recovery catalog database that owns the metadata tables maintained by RMAN. RMAN periodically propagates metadata from the target database control file into the recovery catalog.	No
Standby database	A copy of the primary database that is updated using archived logs created by the primary database. RMAN can create or back up a standby database.	No
Media management application	A vendor-specific application that allows RMAN to back up to a storage system such as tape. When doing backups or restores, the RMAN client connects to the target instance and directs the instance to talk to its media manager. No direct communication occurs between the RMAN client and the media manager: all communication occurs on the target instance.	No
Media management catalog	A vendor-specific repository of information about a media management application.	No
Oracle Enterprise Manager	A GUI-based application that you can use as an interface to RMAN.	No

 Enjoy:-)