Oracle: RMAN Backup & Recovery

1. Check if the database is in archive mode:

Archive mode is disabled.


(2): Set the database is in archive mode:

Premise set up the database in archive mode of the database in mount state, restart the database to mount state:

In the mount state, the use alter database statement archive mode enabled:

2. Define the flash recovery area (flash recovery area):

Flashback recovery area, mainly through the following three initialization parameters to set up and manage:

db_recovery_file_dest : Specifies the position Flashback recovery area
db_recovery_file_dest_size : Specifies flash recovery area free space
db_flashback_retention_target : Specifies that the database can be rolled back in time, in                                                                         minutes,
 The default 1440 minutes, which is one day. Of course, actually be rolled back in time also decided to return the size of the flash recovery area, because it saved the rollback required flash log. So this parameter to modify and db_recovery_file_dest_size fit.

(1) view the current location and the size of the flash recovery area:

(2), setting the flashback recovery area location and size:

Before setting up the flash recovery area location, determine the directory has been created,

or in the process of modification will be reported the following error:

(3) To view the results of the above settings:

(4) If you want to view the flash recovery area space usage, you can view the following views:

(5) If you want to free up more space, you can use the following command to delete all archived log files to free up space:

3. Set the archive logs multipath storage:
(1) view the current configuration information log_archive_dest:

(2), Define a new location:

The first command uses the flash recovery area, the second using a custom location.
(3) to see if the definition of success:

4, on the control file control_file_record_keep_time parameters:
This parameter specify the minimum days the RMAN information is stored in the control file before overwritten. The default value is 7 days. When using catalog, a smaller value should be chosen.
See the value of this parameter:

5, rman use:
(1) Enable rman:

Which means a non-catalog 1,2,3,5,6 connection section 4 is connected to the catalog, db02 is the target database, db01 directory database.
(2) to display the rman configuration information:

(3) Configured rman:
Enable automatic backup control file:

Enable backup set compression:

Define retention policies:
The default retention value is 1.

(4), Restore the configuration defaults rman:

6, The backup command backup:
If the direct use backup database, the whole preparation, this method can not be incremental and differential backups.

Level 0 backup performed, this can be incremental and differential backups:

Level 1 backup performed:

The level at which the cumulative (cumulative) backup 1:

           

Delete all archive logs after the backup is complete:

7, List the command:

                               

8, Report command:

9, Delete the command:


                               

10, Related to the several views rman:


V$ARCHIVED_LOG
V$BACKUP_CORRUPTION
V$BACKUP_DEVICE
V$BACKUP_FILES
V$BACKUP_PIECE
V$BACKUP_REDOLOG
V$BACKUP_SET
V$BACKUP_SPFILE
V$COPY_CORRUPTION
V$RMAN_CONFIGURATION