Whole or full database backup can be performed by issuing BACKUP DATABASE command from the RMAN prompt. Make sure the database is mounted or open before issuing BACKUP DATABASE command.
- You can make backups as image copies or as backupsets. BACKUPSET is default if you do not specify.
- If you issue RMAN command without any option such as BACKUP DATABASE, RMAN determines the destination device, locations for backup output, and a backup tag automatically based on your configured environment and built-in RMAN defaults.
Backup Database without ARCHIVELOG
#Connect to RMAN
#Connect RMAN to target database
RMAN> CONNECT TARGET SYS/pass@TEST1;
#Connect RMAN to recovery catalog (optional)
RMAN> CONNECT CATALOG rman/cat@devdb;
#Issue RMAN BACKUP command.
RMAN> BACKUP DATABASE;
Backup Database plus ARCHIVELOG
BACKUP DATABASE PLUS ARCHIVELOG ensures that we have archived logs for all transactions, including those that occurred while the backup was taking place. This ensures that we can perform media recovery after restoring this backup
BACKUP DATABASE PLUS ARCHIVELOG;
Skipping Offline, Read-Only, and Inaccessible Files
By default, the RMAN BACKUP command terminates when it cannot access a datafile. You can prevent from termination. Use the following parameters when using RMAN BACKUP command.
- SKIP INACCESSIBLE skips Datafiles that RMAN cannot be read.
- SKIP OFFLINE skips Offline datafiles.
- SKIP READONLY skips Datafiles in read-only tablespaces.
Following example skips Offline, Read-Only, and Inaccessible data Files from backup.
Include tablespaces in full database backup configured for exclusion
RMAN> BACKUP DATABASE NOEXCLUDE;
Now RMAN will include all tablespaces in full database backup previously configured for exclusion as explained in "Configure RMAN Tablespace exclusion".