Shulou(Shulou.com)06/01 Report--

Recoverymanager (RMAN) is a backup and recovery tool provided after ORACLE 8i. It can back up the entire database or database parts, including tablespaces, data files, control files and archive files. RMAN can access and perform backups and restores as required.

RMAN components: target database (target database), server process, channel (Channel), RMAN database (Recovery ManagerRepository) and RMAN metadata (Recovery Manager Metadata), recovery directory, media management layer (Media Management Layer), RMAN package (Recovery Manager package)

Connect to the backup target database

View current RMAN configuration

One experimental operation: modify RMAN configuration

Set the redundancy policy. When the backup object has more than one backup set, the redundancy policy is not met because the backup set is marked as obsolete, waiting for the administrator to clear it.

RMAN > configureretention policy to recovery window of 7 days

(restore windowed redundancy strategy. Currently set to 7 days, that is, any database backup longer than the last seven days will be marked as obsolete)

RMAN > configureretention policy to redundancy 2

(backup mirror redundancy strategy. Currently set to 2 copies, that is, the maximum number of backup sets for the same backup object is 2 copies. More than 2 copies, with the oldest backup set marked obsolete)

RMAN > configuredefault device type to sbt

(specifies that the device type for all Istroke O operations is hard disk or tape, and the default value is hard disk)

-force the database to automatically back up the control files after backing up the files or executing the command to change the database structure. The default is off.

RMAN > configurecontrolfile autoback on

-configure the parallelism of the database device type

RMAN > configuredevice type disk parallelism 2

-restore RMAN configuration to default values

RMAN > configuredefault type clear

Second, experimental RMAN backup

Lab operation: general backup operation

In archive mode, DBA performs hot backups of multiple policies on the target object through the backup instruction of RMAN. Note: we rarely use RMAN for cold backup.

Step1: full library hot backup (Whole Database)

RMAN > backupdatabase

Step2: backup specified tablespace (Tablespaces)

RMAN > backuptablespace users

Step3: backing up specified data files (Datafiles)

RMAN > backupdatafile 4

Step4: backup control fil

RMAN > backupcurrent controlfile

Step5: backing up archive log files (Archived logs)

RMAN > backuparchivelog all

Step6: backing up archive log files while deleting archives

RMAN > backuparchivelog all delete input

Step7: full library backup, plus all archive log files

RMAN > backupdatabase plus archivelog

Step8: specify the location where backup sets are stored

By default, if the flashback recovery area is set (specified by the db_recovery_file_dest parameter), the backup set is automatically stored in it.

If you want to store it in a specified location, you need to use the format command.

RMAN > backupformat'/ home/oracle/users.bak' tablespace users

Manage backup sets

In RMAN, DBA can view the backup set information stored in it through the list command

Check the backup status of the whole library

RMAN > listbackup of database

View the backup of the specified tablespace

RMAN > listbackup of tablespace users

View the backup of specified data files

RMAN > listbackup of datafile 4

Check the backup of control files

RMAN > listbackup of controlfile

View archive log backups

RMAN > listbackup of archivelog all

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.