- Configuring the Environment for RMAN Backups 配置RMAN环境
- Configuring RMAN to Make Backups to a Media Manager 备份到介质管理器
- Configuring the Fast Recovery Area 配置快速恢复区
- Configuring the Backup Retention Policy 配置备份保留策略
- Backup Optimization and the CONFIGURE command 备份优化
- Configuring an Archived Redo Log Deletion Policy 配置归档日志删除策略
- Configuring RMAN in a Data Guard Environment 在DG下配置RMAN
- Showing and Clearing Persistent RMAN Configurations 查看和清除RMAN配置
- Configuring the Default Device for Backups: Disk or SBT 配置默认备份设备:磁盘或SBT
- Configuring the Default Type for Backups: Backup Sets or Copies 设置备份类型:备份集或镜像
- Configuring Channels 配置通道
- Configuring Control File and Server Parameter File Autobackups 配置文件和控制文件自动备份
CONFIGURE BACKUP OPTIMIZATION CLEAR;CONFIGURE RETENTION POLICY CLEAR;CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;| Command | Explanation |
|---|---|
| Specifies that backups should go to disk by default. 配置后默认备份到磁盘 If a recovery area is enabled, then the backup location defaults to the fast recovery area. Otherwise, the backup location defaults to an operating system-specific directory on disk. When backing up to disk, the logical block size of the database file must be an even multiple of the physical block size of the destination device. For example, a device of type DISK with a block size of 2 kilobytes can only be used as a destination for backups of database files with logical block sizes of 2 KB, 4 KB, 6 KB, and so on. Most disk drives have physical block sizes of 512 bytes, so this limitation rarely affects backup to disk drives. Nevertheless, you can encounter this limitation when backing up to a writable DVD or a device that has a larger physical block size. 如果配置了FRA,不指定路径时就备份到FRA.当备份到磁盘时,逻辑块的大小必须是物理块大小的数据倍. |
| Specifies that backups should go to tape by default. "Configuring RMAN to Make Backups to a Media Manager" explains how to set up RMAN for use with a media manager. After RMAN can communicate with the media manager, you can configure RMAN to make backups to tape and specify SBT as the default device type. 配置后默认备份到磁带. |
BACKUP DEVICE TYPE sbt DATABASE;
BACKUP DEVICE TYPE DISK DATABASE;CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COPY; # image copies
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET; # uncompressedCONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO COMPRESSED BACKUPSET;CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2G;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT /tmp/%U;CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/disk1/ora_df%t_s%s_s%p';CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '+dgroup1';RMAN> CONFIGURE DEVICE TYPE sbt PARALLELISM 2;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters are successfully storedRMAN> CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO BACKUPSET;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO BACKUPSET PARALLELISM 2;
new RMAN configuration parameters are successfully storedRUN
{
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
BACKUP TABLESPACE users;
}
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP OFF;CONFIGURE CONTROLFILE AUTOBACKUP FORMAT
FOR DEVICE TYPE DISK TO '?/oradata/cf_%F';CONFIGURE CONTROLFILE AUTOBACKUP FORMAT
FOR DEVICE TYPE DISK TO '+dgroup1/%F';CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE sbt CLEAR;- SET CONTROLFILE AUTOBACKUP FORMAT (within a RUN block) RUN块内
- SET CONTROLFILE AUTOBACKUP FORMAT (at RMAN prompt) 提示符下
- CONFIGURE CONTROLFILE AUTOBACKUP FORMAT configure命令
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'controlfile_%F';
BACKUP AS COPY DATABASE;
RUN
{
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/tmp/%F.bck';
BACKUP AS BACKUPSET
DEVICE TYPE DISK
DATABASE;
}- Prerequisites for Using a Media Manager with RMAN 事先准备
- Determining the Location of the Media Management Library 介质管理器的库文件位置
- Configuring Media Management Software for RMAN Backups 设置介质管理软件
- Testing Whether the Media Manager Library Is Integrated Correctly 检查介质管理器库是否完整
- Configuring SBT Channels for Use with a Media Manager 配置SBT通道
CONFIGURE CHANNEL DEVICE TYPE sbt
PARMS 'SBT_LIBRARY=pathname';
/opt/oracle/extapi/[32,64]/{SBT}/{VENDOR}/{VERSION}/libobk.so.so, .sl on HP-UX,
.a on AIX,windows下:%SYSTEM_DRIVE%oracleextapi[32,64]{SBT}{VENDOR}{VERSION}orasbt.dllCONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE'
PARMS 'ENV=(OB_MEDIA_FAMILY=datafile_mf)';RUN
{
ALLOCATE CHANNEL c1 DEVICE TYPE sbt
PARMS 'SBT_LIBRARY=/mydir/lib/libobk.so,
ENV=(OB_DEVICE=drive1,OB_MEDIA_FAMILY=datafile_mf)';
}RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on c1 channel at 11/30/2007 13:57:18
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 25SKGFQ OSD: Error in function sbtinit on line 2278
SKGFQ OSD: Look for SBT Trace messages in file /oracle/rdbms/log/sbtio.log
SBT Initialize failed for /oracle/lib/libobk.so
RUN{ ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=/mydir/lib/libobk.so, ENV=(OB_DEVICE=drive1,OB_MEDIA_FAMILY=datafile_mf)'; RESTORE SPFILE TO PFILE '/tmp/test_restore.f'; # If your database does not use a server parameter file, use: # RESTORE CURRENT CONTROLFILE TO '/tmp/test_restore.f';}CONFIGURE DEFAULT DEVICE TYPE TO sbt;
CONFIGURE CHANNEL DEVICE TYPE sbt
PARMS 'ENV=(OB_RESOURCE_WAIT_TIME=1minute,OB_DEVICE=tape1)';CONFIGURE DEVICE TYPE sbt PARALLELISM 2;SHOW CHANNEL FOR DEVICE TYPE sbt- Overview of the Fast Recovery Area FRA概述
- Enabling the Fast Recovery Area 开启FRA
- Disabling the Fast Recovery Area 关闭FRA
- Configuring Locations for Control Files and Redo Logs 设置控制文件和日志文件位置
- Configuring RMAN File Creation in the Fast Recovery Area 配置备份到FRA
| Files | Type | Database Behavior When Fast Recovery Area Is Inaccessible |
|---|---|---|
Permanent | The instance fails if the database cannot write to a multiplexed copy of the control file stored in the fast recovery area. Failure occurs even if accessible multiplexed copies are located outside the recovery area.如果控制文件不可读,则实例崩溃 See Also: "Configuring Control File Locations" to learn how to configure control files in the recovery area | |
Online redo log files | Permanent | Instance availability is not affected if a mirrored copy of the online redo log exists in an accessible location outside the fast recovery area. Otherwise, the instance fails. 如果一个日志组中的所有日志不可读写,则实例崩溃,只要有一个可读写,实例就可以运行. See Also: "Configuring Online Redo Log Locations" to learn how to configure online redo logs in the recovery area |
Archived redo log files | Transient | Instance availability is not affected if the log is archived to an accessible location outside the fast recovery area. Otherwise, the database eventually halts because it cannot archive the online redo logs. See Also: "Configuring Archived Redo Log Locations" to learn how to configure archived redo logs in the recovery area |
Foreign archived redo log files | Transient | Instance availability is not affected. Note: Foreign archived redo logs are received by a logical standby database for a LogMiner session. Unlike a normal archived log, a foreign archived redo log is associated with a different DBID. For this reason, it cannot be backed up or restored on a logical standby database. |
Image copies of data files and control files | Transient | Instance availability is not affected. |
Backup pieces | Transient | Instance availability is not affected. |
Flashback logs | Transient | Instance availability is not affected if guaranteed restore points are not defined. In this case, the database automatically disables Flashback Database, writes a message to the alert log, and continues with database processing. If guaranteed restore points are configured, the instance fails because of interdependencies on the flashback logs. The Oracle Flashback Database feature, which provides a convenient alternative to database point-in-time recovery (DBPITR), generates flashback logs. These logs are transient files and must be stored in the fast recovery area. Unlike other transient files, flashback logs cannot be backed up to other media. If the fast recovery area has insufficient space to store flashback logs and meet other backup retention requirements, then the recovery area may delete flashback logs. See Also: "Enabling Flashback Database" to learn how to enable flashback logging |
Yes | Specifies the disk quota, which is maximum storage in bytes of data to be used by the recovery area for this database. You must set this parameter before The
| |
Yes | Specifies the recovery area location, which can be a file system directory or ASM disk group, but not a raw disk. The location must be large enough for the disk quota.可以磁盘或ASM上,但是不能在RAW设备上 | |
No | Specifies the upper limit (in minutes) on how far back in time the database may be flashed back. This parameter is required only for Flashback Database. 设置闪回日志保存时间,不一定能保证.比如设置为1440分钟,表示最大可保存1440分钟,也可能只能保存10分钟,具体看闪回空间的大小,也可能保存的比1440分钟大.其实没有啥意义的参数. This parameter indirectly determines how much flashback log data is kept in the recovery area. The size of flashback logs generated by the database can vary considerably depending on the database workload. If more blocks are affected by database updates during a given interval, then more disk space is used by the flashback log data generated for that interval. |
A ALTER DATABASE FLASHBACK OFF;
B 如果使用使用FRA保存归档日志,把 归档日志放在其它地方:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=/ORACLE/DBS/';
C
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='';
DB_CREATE_ONLINE_LOG_DEST_n DB_RECOVERY_FILE_DEST DB_CREATE_FILE_DEST DB_CREATE_ONLINE_LOG_DEST_n---> DB_CREATE_FILE_DEST ----> DB_RECOVERY_FILE_DEST
控制位置由四个参数决定CONTROL_FILESDB_CREATE_ONLINE_LOG_DEST_nDB_RECOVERY_FILE_DESTDB_CREATE_FILE_DEST 优先级: DB_CREATE_ONLINE_LOG_DEST_n---> DB_CREATE_FILE_DEST----> DB_RECOVERY_FILE_DESTDB_RECOVERY_FILE_DEST LOG_ARCHIVE_DEST_n LOG_ARCHIVE_DEST DB_RECOVERY_FILE_DEST (FRA),则并且LOG_ARCHIVE_DEST_n 没有设置,则LOG_ARCHIVE_DEST_10 是自动设置为FRA路径,并且归档将会保存在FRA,如果不想使用FRA,则将LOG_ARCHIVE_DEST_10 设置为其它值.设置了DB_RECOVERY_FILE_DEST 同样可以设置LOG_ARCHIVE_DEST_n . LOG_ARCHIVE_DEST_n 和LOG_ARCHIVE_DEST 是冲突的,不能同时设置这两个参数,只能二选一CONFIGURE RETENTION POLICY 命令设置保留策略CONFIGURE RETENTION POLICY TO NONE;| Type of File | Criteria to Determine an Identical File |
|---|---|
Data file | The data file must have the same DBID, checkpoint SCN, creation SCN, and 数据文件有相同的DBID CHECKPOINT SCN 日志序列,已经备份过并且当前是正常脱机或read-only状态 |
Archived log | Same DBID, thread, sequence number, and 已经备份过的归档日志 |
Backup set | Same DBID, backup set record ID, and stamp |
BACKUP DATABASE FORCE;
BACKUP ARCHIVELOG ALL FORCE;CONFIGURE DEFAULT DEVICE TYPE TO sbt;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;| Day | Action | Result | Redundant Backup |
|---|---|---|---|
Monday | Take | ||
Tuesday |
| The | |
Wednesday |
| The | |
Thursday |
| The | Tuesday backup |
Friday |
| The | Tuesday backup |
Saturday |
| The | Tuesday backup |
Sunday |
| The Tuesday backup is deleted. | |
Monday |
| The | Wednesday backup |
BACKUP ... DELETE INPUT 或者 DELETE ARCHIVELOG 命令可以删除任何地方的归档日志.