Documentos de Académico
Documentos de Profesional
Documentos de Cultura
The RMAN client, which interprets advancement and accretion commands, directs server sessions to assassinate those commands, and annal your advancement and
accretion action in the ambition database ascendancy file.
Logical Backup : backup utility that performs backups on the logical components of the database. A logical backup consists of backing up the database at the
tablespace level or backing up other logical database components such as a table.
Physical Backup: Backing up the database files such as the datafiles, control files, and redo log file
Recovery Catalog
The first method is by accessing an RMAN catalog of information about backups. The second method is by accessing the necessary information about backups in the
target databases control files. The init.ora or spfile.ora parameter CONTROL_FILE_RECORD_KEEP_TIME determines how long information that can be used by
RMAN is kept in the control file. The default value for this parameter is 7 days and can be as many as 365 days.
The recovery catalog is designed to be a central storage place for multiple databases RMAN information. This centralizes the location of the RMAN information instead
of having this information dispersed in each target databases control file. Here is a list of the components contained in a recovery catalog:
Backup and recovery information that is logged for long-term use from the target databases
RMAN scripts that can be stored and reused
Backup information about datafiles and archive logs
Information about the physical makeup, or schema, of the target database
Note: here i am not utilizing defalt rman backup location (db_recovery_dest), i will create new directory named "rman" for holding all rman backups.
1.Login as root user, create directory and permit to rman user for reading/writing backups on directory;
[oracle@redhat ~]$rman
Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jun 1 18:38:55 2004
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN>connect target
connected to target database: ORCL (DBID=1232238763)
http://naeemsheeraz.blogspot.com/2010/01/rman-backup-recovery.html 2/4
23/11/2017 Oracle DBA -Tutorials: RMAN Backup & Recovery
Note: here i am changing default parameters - (you can leave it, if want to utilize default )
new RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1; new RMAN configuration parameters
are successfully stored starting full resync of recovery catalog full resync complete
RMAN>BACKUP DATABASE;
RMAN>run
{ allocate channecl c1 type disk;
backup database format '/rman/%d_%I_%s_%T';
}
RMAN>
http://naeemsheeraz.blogspot.com/2010/01/rman-backup-recovery.html 3/4
23/11/2017 Oracle DBA -Tutorials: RMAN Backup & Recovery
RMAN>run
{ allocate channel c1 type disk;
backup database format 'db_%u_%d_%s';
backup format 'log_t%t_s%s_p%p' (archivelog all);
}
RMAN>
Note: can user following parameters if required--BACKUP (ARCHIVELOG ALL DELETE INPUT);
RMAN>run
{ allocate channel c1 type disk;
backup database format 'db_%u_%d_%s' tag monthly_backup;
backup format 'log_t%t_s%s_p%p' (archivelog all);
}
http://naeemsheeraz.blogspot.com/2010/01/rman-backup-recovery.html 4/4