HP Storage Essentials NAS Manager Software - Manual (Page 270)

Database Maintenance and Management 238
archive mode, you reset the logs SCN, set the archive parameter in the database parameter file and
disable the RMAN backup scheduler.
IMPORTANT: Export the database after switching to no archive mode. See ” Exporting the
Database ” on page 245 for more information.
Keep in mind the following implications if you do decide to change the database to no archive
mode.
• If you set the management server to Disable Database Archive Mode and RMAN Backup, it
is up to you to back up the management server manually. If you forget to back up your
management server and your management server fails, you will not have a database to import.
To learn more about manual backups, see ” Running a Cold Backup ” on page 250. Export the
database after you change the database mode to no archive. See ” Exporting the Database ” on
page 245.
• Scheduled RMAN backup jobs do not run. If you change the database mode to no archive
during an RMAN backup, the RMAN backup will error out.
• If the database fails as a result of a corrupt data file, the database can only be restored to the
last export backup available. This requires recreating the database along with the import.
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 240.
Architectural Overview of RMAN Backups
By default the management server does not backup the database automatically. If you enabled the
database archive mode and RMAN backup as described in ” Setting the Archive Mode ” on
page 248, the management server backs up the Oracle instance for the management server every
three days and saves the backup for two weeks. The management server alternates the directories in
which it saves the backup. When the management server first performs a scheduled backup, the
backup is saved in $ORACLE_HOME/rman/backup1 on UNIX systems and
%ORA_HOME%\rman\backup1 on Microsoft Windows. The next time the management server
performs a scheduled backup, it is saved $ORACLE_HOME/rman/backup2 on UNIX systems and
%ORA_HOME%\rman\backup2 on Microsoft Windows. The management server saves the backup
in alternating directories (backup1 and backup2), so you always have a copy of the last backup
and the previous backup. To learn how to change the frequency of the scheduled backups, see
” Scheduling RMAN Hot Backups of the Database ” on page 241.
You can back up the database at any time by clicking the Backup Now button on the Database
tab. When you back up the database using this technique, the backup is saved only in
$ORACLE_HOME/rman/current on UNIX systems and %ORA_HOME%\rman\current on
Microsoft Windows. To recover the database, contact customer support.