Use the SECTION SIZE clause of the BACKUP command to create multisection backups. RMAN always creates multisection incremental backups with FILESPERSET set to 1. However, to create multisection incremental backups of level 1 or higher, you must set the COMPATIBLE parameter to 12.0.0 or higher. To create level 0 multisection incremental backups, the COMPATIBLE parameter must be set to 11.0 or higher.
Copy space check full#
When backup sets are used, you can create multisection full or Uses unused block compression and block change tracking while creating multisection (12.1), RMAN supports multisection incremental backups. Starting with Oracle Database 12 c Release 1 Multisection full backups of databases and data files are supported starting with
During a multisection backup operation, RMAN writes to each backup piece, in parallel, by using a separate channel for each backup piece. Tags cannot use operating system environment variables or use special formats such as %T or %D.Ī multisection backup contains multiple backup pieces. The maximum length of a backup tag is 30 bytes. Tags are stored in uppercase, regardless of the case used when entering them. If multiple backup sets are created by one BACKUP command, then each backup piece has the same default tag. The date and time refer to when RMAN started the backup in the time zone of the instance performing the backup. For example, a backup of data file 1 may get the tag TAG20070208T133437. The format of the tag is TAG YYYYMMDD T HHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. If you do not explicitly specify a tag with the TAG parameter of the BACKUP command, then RMAN implicitly creates a default tag for backups (except for control file autobackups). RECOVER commands let you specify a tag to restrict which backups to You associate a tag with a backup, and many RESTORE and For example, you mightĬreate a weekly incremental backup with a tag like BACKUP TAG Of a single strategy, such as an incremental backup strategy.
Copy space check series#
In practice, tags are often used to distinguish a series of backups created as part If multiple backups of the requested file have the desired tag, then RMAN restores the most recent backup that has the desired tag, within any constraints on the RESTORE command. Assume that you specify that a data file be restored from backups that have a specific tag. Tags do not need to be unique, so multiple backup sets or image copies can have the same tag (for example, weekly_backup). SWITCH command as for_switch_only and file copies ForĮxample, you can tag data file copies that you intend to use in a You can tag backup sets, proxy copies, data file copies, or control file copies. User-specified tags are a useful way to indicate the purpose or usage of different classes of backups or copies. Typically, you do not need to specify a format when backing up to tape because the default %U variable generates a unique file name for tape backups. CONFIGURE DEVICE TYPE DISK PARALLELISM 3 ĬONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/disk1/%d_backups/%U' ĬONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/disk2/%d_backups/%U' ĬONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '/disk3/%d_backups/%U' To create a default configuration that distributes backups to multiple disk drives by default, configure multiple disk channels. To back up a database to multiple disk drives, allocate one DISK channel for each disk drive and specify the format string on the ALLOCATE CHANNEL command so that the file names are on different disks.ĪLLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/disk1/%d_backups/%U' ĪLLOCATE CHANNEL disk2 DEVICE TYPE DISK FORMAT '/disk2/%d_backups/%U' ĪLLOCATE CHANNEL disk3 DEVICE TYPE DISK FORMAT '/disk3/%d_backups/%U'