备份恢复"/>
RMAN备份恢复
RMAN(Recovery Manager) 是Oracle最初为实现数据库物理备份与介质回复方案而提供的专门工具,功能不断得到完善;目前他已经成为基于数据库备份管理的综合工具。
RMAN一些概念
目标数据库(Target Database):RMAN需要对其进行备份的数据库
快速恢复区(flash/fast Recovery Area),从Oracle 10G开始的一个专门的存储区域,专门用来存储,管理与数据库备份与恢复相关的各类数据。当目标数据库设置了快速恢复区后,数据库归档日志默认的本地存储目的地就是快速恢复区,RMAN默认的备份目的地也是。快速恢复区中的文件采用OMF(Oracle Managed File)形式管理。在目标数据库和RMAN中可以设置FRA文件和备份的保留策略。控制文件联机镜像、联机重做日志组陈冠、归档日志、RMAN备份片-BACKUP PIECE、RMAN镜像复制-IMAGE COPY、数据库闪回日志-FLASHBACK LOG的日志,有两个视图,v$recovery_file_dest -- 快速恢复区的整体使用,v$recovery_area_usage -- 快速恢区不同文件空间占用情况
RMAN服务器进程,是RMAN客户端连接到目标数据库时在服务器上生成的进程,他执行rman发出的指令。当执行时候,会在目标数据库创建两个会话---v$session试图可见,一个主进程用于执行对程序包的调用,实现rman备份恢复等,另一个次进程轮训前一个进程的各种内部操作,并将各种操作结果记录到RMAN存储库--repository。在RMAN执行期间使用V$SESSION_LONGOPS中看到系进程状态信息。
快照控制文件--Snapshot Controlfile是RMAN在执行联机数据库备份时必须创建的特定控制文件,是联机控制文件在备份时的静态版本,RMAN依据它进行后续的备份操作。数据库在运行过程中,控制文件处于动态读写状态,如果启动了数据库的备份操作,RMAN需要一个稳定的,一致的控制文件信息,所以在每次备份时候都会创建快照控制文件。
RMAN在执行过程中,会产生关于备份的原数据Metadata,我们将它称为恢复存储库--Recovery Repository。这个存储池有两种,一个是目标数据库的控制文件,一个是恢复目录--Recovery Catalog。恢复目录是个特定用户模式,RMAN通过该模式下的一系列表视图RC_*,来存储和管理repository的信息。并且恢复目录存在于目标数据库之外的数据库中,并且称之为恢复目录数据库。
辅助数据库实例--Auxiliary Database instance 是RMAN环境中在执行某些特定操作(数据库复制,创建备用数据库等)需要的特定数据库实例,RMAN连接到该实例后,可以根据目标数据库并结合用户需要创建特性用途的数据库。
介质管理层--Media Management Layer 是RMAN使用磁带设备所必需的,是RMAN和磁带设备之间的软件曾,RMAN通过介质管理层软件来读写磁带设备。
目标数据库设置
配置快速恢复区,注意空间
设置归档模式
启动数据库闪回,设置db_flashback_retention_target 参数
设置control_file_record_keep_time,该参数设置控制文件中的Repository信息保留的天数
配置目录数据库
创建用户:
create bigfile tablespace rc_tbs datafile /u01/app/oracle/oradata/ORCL/rc_tbs.dbf size 100M autoextend on;
create user rc_user identified by rc_user default tablespace rc_tbs;
grant resource,connect,recovery_catalog_owner to rc_user;
创建恢复目录模式对象
[oracle@cent admin]$ rman catalog rc_user/RC_USER@orclRecovery Manager: Release 11.2.0.3.0 - Production on Sat Apr 22 21:55:17 2017Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.connected to recovery catalog databaseRMAN> create catalog tablespace rc_tbs;recovery catalog created
将目标数据库注册到恢复目录
[oracle@cent ~]$ rman target / catalog rc_user/RC_USER@orclRecovery Manager: Release 11.2.0.3.0 - Production on Sat Apr 22 22:00:07 2017Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.connected to target database: db1 (DBID=2096620489)
connected to recovery catalog databaseRMAN> upgrade catalog;recovery catalog owner is RC_USER
enter UPGRADE CATALOG command again to confirm catalog upgradeRMAN> upgrade catalog;recovery catalog upgraded to version 11.02.00.03
DBMS_RCVMAN package upgraded to version 11.02.00.03
DBMS_RCVCAT package upgraded to version 11.02.00.03RMAN> register database;database registered in recovery catalog
starting full resync of recovery catalog
full resync completeRMAN> resync catalog;starting full resync of recovery catalog
full resync complete
取消注册使用:
set dbid xxx
unregister database db_name
常用的配置
备份的保留策略
RMAN> configure retention policy to recovery window of 7 days;new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully storedRMAN> report obsolete;RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found
归档日志删除策略
RMAN> configure archivelog deletion policy to backed up 1 times to device type disk;new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
new RMAN configuration parameters are successfully stored
说明:
这里配置的是至少备份一次,并且类型是disk的,另外可配置删除策略为传输并应用到至少一个备用数据库,
RMAN> configure archivelog deletion policy to applied on standby;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
RMAN-08591: warning: invalid archived log deletion policy
排除不需要的表空间
RMAN> configure exclude for tablespace users;Tablespace USERS will be excluded from future whole database backups
new RMAN configuration parameters are successfully stored
如果在需要备份时候,可以使用noexclude关键字即可
压缩备份
rman提供三种级别的选择,low,medium,high。需要注意的是,压缩级别会影响rman对cpu的消耗
RMAN> show compression algorithm;RMAN configuration parameters for database with db_unique_name CDB1 are:
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # defaultRMAN> configure compression algorithm 'low';new RMAN configuration parameters:
CONFIGURE COMPRESSION ALGORITHM 'low' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
new RMAN configuration parameters are successfully storedRMAN> show compression algorithm;RMAN configuration parameters for database with db_unique_name CDB1 are:
CONFIGURE COMPRESSION ALGORITHM 'low' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;RMAN> configure compression algorithm clear;old RMAN configuration parameters:
CONFIGURE COMPRESSION ALGORITHM 'low' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
RMAN configuration parameters are successfully reset to default value
配置备份通道与存储
通道是RMAN与目标数据库的连接在数据库中开辟的会话,负责执行将RMAN备份结果以特定格式写入备份设备。默认情况下,备份通道指向磁盘设备,存储目的地是数据库的快速恢复区。
RMAN> configure default device type to disk;new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully storedRMAN> configure default device type to sbt;old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters are successfully storedRMAN> configure device type disk backup type to copy;new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COPY PARALLELISM 1;
new RMAN configuration parameters are successfully storedRMAN> configure device type disk backup type to backupset;old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COPY PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
new RMAN configuration parameters are successfully storedRMAN> RMAN> configure device type disk parallelism 2;old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully storedRMAN> configure channel device type disk format '/dbbak/oradata/backup_%U';new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/dbbak/oradata/backup_%U';
new RMAN configuration parameters are successfully storedRMAN> configure channel 1 device type disk format '/dbbak/oradata/backup1_%U';new RMAN configuration parameters:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/dbbak/oradata/backup1_%U';
new RMAN configuration parameters are successfully storedRMAN> configure channel 2 device type disk format '/dbbak/oradata/backup2_%U';new RMAN configuration parameters:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/dbbak/oradata/backup2_%U';
new RMAN configuration parameters are successfully storedRMAN> configure maxsetsize to 500M;new RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 500 M;
new RMAN configuration parameters are successfully stored
影响备份结果--备份集,备份片以及文件大小的有maxpiecesize,maxsetsize,filesperset,其中filesperset需要在rman备份指令中设置。
RMAN> configure exclude for tablespace users clear;Tablespace USERS will be included in future whole database backups
old RMAN configuration parameters are successfully deleted
备份操作
RMAN的特点
1,RMAN自动生成关于备份的元数据,便于对备份结果的管理
2,RMAN只会备份使用过的数据块
3,备份过程中对数据库的检测,也可以单独对要备份的内容执行物理的和逻辑的数据块检测
4,可以联机备份-- 归档模式下,也可以在脱机-mount下备份
5,RMAN可以增量备份,也可以执行压缩备份,加密备份
6,可以监控备份过程,进度---v$session_longops,备份过程的输出--v$rman_output
备份目标和备份结果
rman可以备份整个数据库,耽搁表空间,甚至是RMAN的备份结果也可以是rman的备份内容,备份内容清单:
数据库--database
表空间--tablespace
数据文件-datafile
归档日志文件-archivelog
控制文件-controlfile
初始化文件-spfile
数据文件复制-datafilecopy
控制文件复制-controlfilecopy
rman备份集-backupset
快速恢复区-recovery area
备份的结果:
备份集-beckupset
备份片-backuppiece
压缩备份集-compressed backupset
映像复制-image copy
RMAN备份BACKUP
RMAN的备份操作通过BACKUP命令实现,该类指令有一系列的选项可以控制备份目标,备份结果,备份过程等。该指令有两种使用模式::一种是交互模式(interactive mode);另一种是批处理模式(batch mode),将一族相关的RMAN执行包含在RUN{...}快中执行
比如:
backup database plus archivelog;
和
run{
allocate channel c1 device type disk format '/dbbak/ora_%U';
backup database plus archivelog;
}
常用的rman备份内容:
backup database;
backup tablespace ...;
backup datafile ...;
backup current controlfile;
backup spfile;
backup archivelog ...;
backup ... plus archivelog;
backup recovery area;
backup datafilecopy ...;
backup controlfilecopy ...;
backup copy of database;
backup copy of tablespace ...;
backup copy of datafile ...;
skip 选项手动筛选掉备份内容
backup ... skip readonly;
backup ...skip offline;
backup ... skip inaccessible;
通过not backed up 选项,自动筛选备份的内容
backup not backed up ...;
backup not backed up x times ...;
backup not backed up since time 'sysdate - n' ...;
通过as ... 选项控制备份结果的输出形态,设备类型,文件命名格式
backup as baskupset ...;
backup as compressed backupset ...;
backup as copy ...;
backup device type disk | sbt ....;
backup format ...;
keep选项
backup ... keep forever;
backup ... keep until time 'sysdate +n';
plus archivelog
可以查看哪些归档日志要备份:v$archived_log——记录归档日志的信息!
backup指令可以附加对归档日志的备份, backup.... plus archivelog;
执行backup database plus archivelog;
查看:archive log list;
rman>list archivelog all;-- 查看归档
最后执行backup database plus archivelog;
list backup;
查看:archive log list;
得到执行过程:
1,归档当前联机日志,产生日志切换---相当于执行了alter system archivelog current指令
2,备份数据库已有的归档日志,产生一个备份集
3,备份数据库的数据文件,产生备份集
4,备份数据库的SPFILE和控制文件,产生备份集
5,再次归档当前的联机日志--备份期间产生的日志,发生第二次日志切换
6,备份前一步骤中产生的归档日志,产生备份集
可以使用backup database plus archivelog delete input或者backup database plus archivelog delete all input删除备份的归档日志
RMAN的增量备份
rman增量备份仅备份那些经历改变的数据快,好处有:显著减少备份集大小,节约备份时间等。但在恢复时候会增加数据库的恢复时间
启动快变更跟踪
rman备份的本质是只备份自上次备份以来发生改变的数据块,所以在默认情况下,rman需要搜寻所有的数据文件以找出已经变更的数据块,此操作会增加备份时间。
oracle11g增加了一个特性,叫块变更跟踪(block change tracking),用于将发生改变的数据块信息记录到特定的文件中,利用该文件,oracle可以显著增加执行增量备份的效率,启用快变更跟踪:
alter database enable block change tracking using file 'xxx' [reuse]; -- xxx为具体的目录文件
启用之后,可以在v$block_change_tracking获取块改变跟踪文件信息。
禁用:
alter database disable block change tracking;
增量备份类别
执行增量备份需要一个完全备份,即level 0的备份,在此基础上可以执行增量为1的备份,level 1的备份只能依赖于level 0的备份,而不能依赖于其他的完全备份
rman有两种增量备份,差异备和累积备份。差异增量备份时备份自上次level 0或者level 1的增量备份依赖已经改变的数据块;累积增量备份时忽略已经执行的增量备份,备份自会桑次level 0备份以来所有的已经改变的数据块
level 0的增量备份;backup incremental level 0 database;
level 1的差异增量备份:backup incremental level 1 database;
level 1的累积增量备份:backkup incremental level 1 cumulative database;
注意如果在执行level增量备份时候没有level 0 的备份,将自动转换当次的level 1为level 0的备份
增量备份可以在数据库,表空间,数据文件级别执行;可以执行大于1的增量备份,但是不推荐
基于scn的增量备份
此增量备份多用于Data guard环境中,由于某种原因,物理备用数据库严重滞后于主数据库,为了快速使物理备用数据库与主库同步,或者物理备用数据库缺乏必要的归档日志与主数据库同步,此时可以先查询物理备用数据库的scn(v$database.current_scn),之后从主数据库执行基于scn的备份,将获得的增量备份集注册至物理备用数据库,启动介质恢复--必须带noredo选项,将物理备用数据库恢复至与主库同步的状态。
RMAN>backup incremental from scn scn_number database;
SYS@PROD> recover database noredo;
RMAN备份其他选项
backup指令的其他选项
控制备份及大小及数据库文件数量
backup ... filesperset n maxsetsize xm;
归档日志备份后删除,前边有介绍
backup archivelog ... delete input;
backup archivelog ... delete all input;
delete all input会删除所有目的地的归档日志
选项force和noexclude
foce备份内容强制包含备份优化省略的备份内容(比如为更改的数据文件,只读表空间等)
选项noexclude针对预先配置了configure exclude for tablespace ..的情况,使得备份包含exclude的表空间
backup ... force;
backup ... noexclude;
备份添加标签
backup database tag 'my_full_backup';
检查数据块
默认情况下,rman在备份时执行对数据块的数据校验计算和检查,checksum是oracle根据数据块内容计算出数据校验值。当初始化参数DB_BLOCK_CHECKSUM设置为typical时,实例在读写数据块时同样执行数据校验检查
rman的backup指令还可以对数据块执行进一步的物理检查和逻辑检查,判断待备份的数据块是否出现物理或者逻辑的讹误(corruption).
backup nochecksum ...;
backup validate ...;
backup check logical ...;
比如backup validate check logical database;
控制备份片的命名
常用的两个备份片唯一性命名的有%U和%F,%F是DBID和时间信息的组合,默认对控制文件的备份,%U是8位字符的时间表示(%u)和备份额片编号(%p),备份片的复制数(%c)三者结合,默认对于其他备份片命名
限定RMAN备份过程
我们可以对rman进行时间限制,一是备份持续时间,一是备份符合限制
backup duration hh:mm ...;
backup duration hh:mm partial ...;
backup minimize time ...;
backup minimize load ...;
比如,设置备份数据库的操作,限制在一个半小时,minimize time指示rman全速备份,超过一个半小时备份终止,partial选项指示rman由于时间限制而终止的备份并不会做为失败的备份处理,已经生成的备份片正常注册至repository,恢复时可用
backup duration 01:30 minimize time partial database;
管理RMAN备份结果
目标数据库中,可以看到一些备份相关的视图,比如v$backup_set,v$baskup_piece等,这些信息来源于目标数据库的控制文件,受到参数control_file_record_keep_time的限制
在RMAN环境中可以执行的常用指令:
list,report,delete,crosscheck,catalog,change,
查看备份结果list
语法list [expired|recoverable] object [of obj_contain] [by file | summary]
其中obj有,backup,backupset,backuppiece,copy,archivelog,controlfilecopy,datafilecopy
obj_contain 有database,tablespace,datafile,archivelog,controlfile,spfile
比如
list backup;
list backup of tablespace example summary;
list其他用法
list arvhivelog all;
list backup of archivelog all;
list backup of controlfile;
list backup of spfile;
list copy;
list copy of database;
list copy of tablespace users;
list copy archivelog all;
list backup of archivelog sequence between 200 and 210
list backup of archivelog until time 'sysdate-2'
list backun of archivelog from time 'sysdate -7'
list backup completed between 'sysdate - 7' and 'sysdate - 1'
备份报告
report生成关于备份结果的报告,比如:
report need backup;
report obsolete;-- 根据retention policy确定是否过期,区别于expired文件不在的过期
report schema;
report unrecoveralbe;
备份的状态和交叉检验
用于检查备份结果是否存在,若存在,则备份结果的状态标记为Available-可用,否则标记为Expired-过期或者不可用
crosscheck backup;
crosscheck backup of database users;
crosscheck backup of datafile 3;
crosscheck backup comprete between 'sysdate-7' and 'sysdate -1'
rman根据备份策略,将不再需要的备份标记为obsolete-过时的;通过交叉检查,将无利不存在的备份记录标记为expired-过期的,可以通过delete指令删除备份结果以及备份记录
delete backup...
delete copy ...
delete obsolete ...
delete expired ...
可以根据需人工将某个备份或者某些备份标记为unavailable,这样的状态表示rman的restore指令不会利用备份对数据库进行还原
change ... available;
change ... unavailable;
change ... uncatalog;
change ... keep forever;
change ... keep until time '...'
RMAN中注册备份
使用rman备份时候,将自动将备份结果注册至目标数据库的控制文件,或者恢复目录中,但是在某些情况下,需要使用catalog指令手工注册手工备份结果,归档日志或者额外的rman备份结果
catalog archivelog 'logfilespec';
catalog backuppiece 'piecefilespec';
catalog datafilecopy 'copyfilespec';
catalog controlfilecopy 'copyfilespec';
catalog recovery area;
catalog start with 'dirspec';
备份集备份片
RMAN> backup database;Starting backup at 13-MAY-17
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/cdb1/system01.dbf
input datafile file number=00007 name=/u01/app/oracle/oradata/cdb1/users01.dbf
channel ORA_DISK_1: starting piece 1 at 13-MAY-17
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00003 name=/u01/app/oracle/oradata/cdb1/sysaux01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/cdb1/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 13-MAY-17
channel ORA_DISK_1: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup1_01s45vcn_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:18
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00010 name=/u01/app/oracle/oradata/cdb1/cdb1pdb/sysaux01.dbf
channel ORA_DISK_1: starting piece 1 at 13-MAY-17
channel ORA_DISK_2: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup2_02s45vcn_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:01:21
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00009 name=/u01/app/oracle/oradata/cdb1/cdb1pdb/system01.dbf
input datafile file number=00011 name=/u01/app/oracle/oradata/cdb1/cdb1pdb/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 13-MAY-17
channel ORA_DISK_1: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup1_03s45vf7_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/u01/app/oracle/oradata/cdb1/pdbseed/sysaux01.dbf
channel ORA_DISK_1: starting piece 1 at 13-MAY-17
channel ORA_DISK_2: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup2_04s45vf8_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:46
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00005 name=/u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf
input datafile file number=00008 name=/u01/app/oracle/oradata/cdb1/pdbseed/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 13-MAY-17
channel ORA_DISK_1: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup1_05s45vgm_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00012 name=/u01/app/oracle/oradata/cdb1/cdb1pdb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 13-MAY-17
channel ORA_DISK_2: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup2_06s45vgm_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: finished piece 1 at 13-MAY-17
piece handle=/dbbak/oradata/backup1_07s45vhp_1_1 tag=TAG20170513T222630 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-MAY-17Starting Control File and SPFILE Autobackup at 13-MAY-17
piece handle=/u01/app/oracle/fast_recovery_area/cdb1/CDB1/autobackup/2017_05_13/o1_mf_s_943914554_dkg61wdk_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 13-MAY-17
备份集:是RMAN用来保存备份特有的格式,一个备份集可以包含一个或者多个物理文件。
备份集有三种:
-
数据文件:可以包含数据文件和控制文件,但不包含归档日志。
-
归档日志:仅包含归档日志,不能包含数据文件或控制文件。
-
备份集:在RMAN中可以对备份集做备份,也就是说备份集里面包含备份集
备份集的特性
-
可以使用BACKUP 命令创建备份集。FILESPERSET 参数可以控制备份集中包含的数据文件个数。
-
备份集通常包含多个文件。
-
可以将备份集写入磁盘或磁带。
-
要从备份集中提取文件,必须使用还原操作。
-
数据文件备份集可以是增量备份或完全备份。
-
备份集不包含从未使用过的块。
piece即时备份片的意思。备份片在物理上将备份集拆分成一个或多个文件
备份片的特性
-
备份片是备份集中的一个文件。
-
备份片可以包含来自多个数据文件的数据块。
-
可以使用参数MAXPIECESIZE来控制备份片的最大大小。
RMAN> list backup summary;List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
1 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
2 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
3 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
4 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
5 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
6 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
7 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222630
8 B F A DISK 13-MAY-17 1 1 NO TAG20170513T222914RMAN> list backup;List of Backup Sets
===================BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
1 Full 692.95M DISK 00:01:14 13-MAY-17 BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup1_01s45vcn_1_1List of Datafiles in backup set 1File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----1 Full 1795990 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/system01.dbf7 Full 1795990 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/users01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
2 Full 463.09M DISK 00:01:19 13-MAY-17 BP Key: 2 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup2_02s45vcn_1_1List of Datafiles in backup set 2File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----3 Full 1795989 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/sysaux01.dbf4 Full 1795989 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/undotbs01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3 Full 309.84M DISK 00:00:38 13-MAY-17 BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup1_03s45vf7_1_1List of Datafiles in backup set 3Container ID: 3, PDB Name: CDB1PDBFile LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----10 Full 1794209 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/cdb1pdb/sysaux01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
4 Full 236.41M DISK 00:00:38 13-MAY-17 BP Key: 4 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup2_04s45vf8_1_1List of Datafiles in backup set 4Container ID: 3, PDB Name: CDB1PDBFile LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----9 Full 1794209 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/cdb1pdb/system01.dbf11 Full 1794209 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/cdb1pdb/undotbs01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
5 Full 276.70M DISK 00:00:29 13-MAY-17 BP Key: 5 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup1_05s45vgm_1_1List of Datafiles in backup set 5Container ID: 2, PDB Name: PDB$SEEDFile LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----6 Full 1442584 15-APR-17 NO /u01/app/oracle/oradata/cdb1/pdbseed/sysaux01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
6 Full 237.55M DISK 00:00:34 13-MAY-17 BP Key: 6 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup2_06s45vgm_1_1List of Datafiles in backup set 6Container ID: 2, PDB Name: PDB$SEEDFile LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----5 Full 1442584 15-APR-17 NO /u01/app/oracle/oradata/cdb1/pdbseed/system01.dbf8 Full 1442584 15-APR-17 NO /u01/app/oracle/oradata/cdb1/pdbseed/undotbs01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7 Full 1.04M DISK 00:00:00 13-MAY-17 BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222630Piece Name: /dbbak/oradata/backup1_07s45vhp_1_1List of Datafiles in backup set 7Container ID: 3, PDB Name: CDB1PDBFile LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name---- -- ---- ---------- --------- ----------- ------ ----12 Full 1794209 13-MAY-17 NO /u01/app/oracle/oradata/cdb1/cdb1pdb/users01.dbfBS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
8 Full 17.94M DISK 00:00:02 13-MAY-17 BP Key: 8 Status: AVAILABLE Compressed: NO Tag: TAG20170513T222914Piece Name: /u01/app/oracle/fast_recovery_area/cdb1/CDB1/autobackup/2017_05_13/o1_mf_s_943914554_dkg61wdk_.bkpSPFILE Included: Modification time: 13-MAY-17SPFILE db_unique_name: CDB1Control File Included: Ckp SCN: 1796060 Ckp time: 13-MAY-17
一个备份脚本
run{
allocate channel c1 device type disk maxpiecesize=10G;
allocate channel c2 device type disk maxpiecesize=10G;
allocate channel c3 device type disk maxpiecesize=10G;
allocate channel c4 device type disk maxpiecesize=10G;
allocate channel c5 device type disk maxpiecesize=10G;
allocate channel c6 device type disk maxpiecesize=10G;
crosscheck backup;
crosscheck archivelog all;
delete expired archivelog all;
delete noprompt expired backup;
delete noprompt obsolete;
delete noprompt backup of database completed before 'sysdate - 30';
sql 'alter system archive log current';
backup database format '/home/oracle/backup/backupall_df_%d_%T_%U.rmn';
sql 'alter system archive log current';
backup archivelog all format '/home/oracle/backup/arclg_%t_%s_%U .arch' delete all input;
backup current controlfile format '/home/oracle/backup/contrlf_%s_%p_%s_%U.ctr';
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
}
更多推荐
RMAN备份恢复
发布评论