The scheduled backup writes in the backup1 and backup2 folders, in rotation. The Backup Now backup from the management server keeps overwriting in the current folder. See ”Architectural Overview of RMAN Backups” on page 229 for more information about RMAN backups.
Database ModeThe database can be set to archive mode or
Archive Mode
To facilitate the HOT RMAN backup, you must change the database mode to archive mode, as described in ”Changing the Archive Mode” on page 240. The default database archive destination is
\oracle\oradata\APPIQ\archive on Microsoft Windows and
$ORACLE_HOME/oradata/APPIQ/archive on UNIX systems. This destination can be modified as described in ”Changing the Archive Destination” on page 242.
Depending on the input/output of the data, archiving can be in the range of 2.5 GB to 10 GB per day. The archive folder gets cleaned during on a scheduled RMAN backup.
When you change the database to archive mode, you reset the logs SCN, set the archive parameter in the database parameter file and enable the RMAN backup scheduler. Take a current RMAN backup after switching to archive mode, as described in ”Performing an RMAN Hot Backup” on page 230.
You can change the database mode to run in
IMPORTANT: Export the database after switching to
Keep in mind the following implications if you do decide to change the database to
•If you set the management server to
•Scheduled RMAN backup sessions do not run. If you change the database mode to
228 Database Maintenance and Management