诊断Oracle RMAN备份慢的原因
㈠ 先在系统层面查询CPU、IO使用情况:top、iostat、sar...等 ㈡ EXEC DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT(); ㈢ rman target / debug trace =/tmp/rmandebug.txt log=/tmp/rman_log20130727.txt 执行备份 ㈣ EXEC DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT(); ㈤ 查询v$backup_datafileset markup html on set echo on set pages 80 set li
RMAN Compressed Backupset
先看一段官方文档的解释:There is some CPU overhead associated with compressing backup sets. If the database being backed up is running at or near its maximum load, you may find the overhead from using AS COMPRESSED BACKUPSET unacceptable. In most other circumstances, compressing backupsets saves enough disk space to be worth the CPU overhead 总之、占用更多的 CPU 开销、但备份集减小了 测试一把(平台:
RMAN delete expired & delete obsolete
先看官方文档解释: delete exipiredIf you run CROSSCHECK, and if RMAN cannot locate the files, then it updates their records in the RMAN repository to EXPIRED status. You can then use the DELETE EXPIRED command to remove records of expired backups and copies from the RMAN repository delete obsoleteThe RMAN DELETE command supports an OBSOLETE option, which deletes backups that are no longer needed to
RMAN Recovery Window retention policy tips
Assume the following retention policy illustrated in Figure rw01. The retention policy has the following aspects: ■ The recovery window is 7 days. ■ Database backups are scheduled every two weeks on these days: – January 1 – January 15 – January 29 – February 12 ■ The database runs in ARCHIVELOGmode, and archived logs are saved on disk &
Image Copy Incremental Updates(ICIU):concepts
㈠ 作用 限制 Redo 的运用量、从而降低恢复时间 ㈡ 原理 创建数据文件的镜像拷贝、随后用增量备份集更新镜像拷贝 即:把 1 级增量备份集并入已存在的镜像拷贝中 ㈢ 测试
RMAN not always use incremental backup if it has archivelog backup too
Refer to :metalink 134214.1如果存在归档日志备份集的话、那么 RMAN 就不一定会选择增量备份集让我们使用以下的 RECOVER 命令作为例子:RMAN> run{ 2> allocate channel x type disk; 3> restore datafile 7; 4> recover datafile 7; 5> } 首先、RMAN 将把从最后一次0级增量备份的数据文件 7 覆盖回去、接下来、RMAN 会有 2 条路:① 把自最后一次0级备份以来、所有存在的增量备份全部覆盖回去
RMAN incremental backup tips
原文地址:RMAN incremental backup tips 增量备份极大地降低了 Oracle备份的时间开支、但是这一机制可能比较繁琐 10g及之后版本、你能够使用 RMAN 的增量备份对数据文件的镜像拷贝进行前滚到指定的时间点、这一新特色提供如下益处: ① 用增量备份定期更新数据文件的镜像拷贝、被更新的镜像会前滚到一个更新的状态(也就是最近的 SCN)、这么做可能
Incremental Differential vs. Incremental Cumulative Backups
原文地址:Incremental Differential vs. Incremental Cumulative Backups 问题: RMAN differential Backups 是什么?它和 RMAN cumulative Backups 有啥区别?它们俩和 RMAN incremental backup 一样吗? 答案: Differential 和 cumulative 是 RMAN incremental backups 的两种类型。有时候、RMAN differential backups 被叫做 RMAN cumulative Backups 然而、RMAN incremental backups 、有时
RMAN 增量备份 的 对象测试
在练习 RMAN Incremental Backup 时、参照 OCP TK 042 : 对于 RMAN 增量备份的对象、官网摘入如下: You can make incremental backups of databases, individual tablespaces or datafiles. 显然、基于96 题的答案、archive log 不在列位、偶撞了南墙也想测试呀RMAN> backup incremental level
基于时间的备份保留策略的rman研究
1 实验准备 a)物理和逻辑上检查SQL> col file_name for a70 wrapped SQL> select file_name,status from dba_data_files where file_id=4; FILE_NAME STATUS ---------------------------------------------------------------------- --------- /u01/app/oracle/oradata/ORCL/datafile/o1_mf_users_7wvsw7hg_.dbf AVAILABLE SQL> select tablespace_name,status from dba_tablespace
rman配置参数详解
RMAN 配置参数为:RMAN> show all; CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO \'%F\'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE AR
RMAN备份FORMAT格式中%a的含义
oracle文档对%a的描述是:%a Specifies the activation ID of the database. rman备份并保存,查询%aRMAN> backup tablespace users format \'/home/oracle/think_%a\'; 由此,可知%a为:790774120 查询x$kccdisys@ORCL> SELECT didbn,dirlc,dirlc_i FROM x$kccdi; DIDBN DIRLC DIRLC_I --------- -------------------- ---------- ORCL 08/08/2012 11:28:40 790774120
rman基本组件和主要术语
rman可以用来backup和restore数据文件、控制文件、归档日志等,也可作完全和不完全的recover的oracle工具。由命令行或者OEM的backup manager GUI控制。RMAN是块级别的备份与恢复. rman主要组件: 1)Target Database:(目标数据库) rman的作用对象 2)会话 sys@ORCL> select sid,username,program from v$session where username is not null;
rman实验之归档模式无备份,正常关机丢失当前联机重做日志文件的恢复
所有的备份软件都没有备份联机重做日志文件的说法。因为,它几乎时刻都在写,单独备份某个时刻,没啥意义。再者,归档日志在某种意义上,也是对联机重做日志的备份。对联机重做日志文件的保护,核心就两个字:冗余。包括:多路镜像、RAID方式、HA的运用(如DG)。 1)查看当前的联机重做日志文件sys@ORCL> select group#,members,sequence#,status from v$
rman实验之归档模式有备份,正常关机丢失控制文件的恢复
在恢复控制文件之前,必须知道目标数据库的DBID。身为DBA的你,在接手数据库时,定要把数据库的DBID给备份出来! 1)备份控制文件RMAN> list backup of controlfile; 2)测试数据hr@ORCL> create table t (name varchar2(20)); Table created. hr@ORCL> insert into t values(\'think\'); 1 row created. hr@ORCL> commit; Commit complete. 3)模拟环境sys@ORCL> shutd
rman实验之归档模式有备份,正常关机丢失数据文件的恢复
1 创建备份RMAN> backup database plus archivelog; 2 搭建环境hr@ORCL> create table tt (name varchar2(20)); Table created. hr@ORCL> insert into tt values(\'test1\'); 1 row created. hr@ORCL> insert into tt values(\'test2\'); 1 row created. hr@ORCL> insert into tt values(\'test3\'); 1 row created. hr@ORCL> commit; Commit complete. hr@ORCL> select * from tt; NAME -------------------- test1 test2 test3 3 模拟
rman系列之7问rman
第一问:是否选择增量备份? 所有增量备份都必须先创建0级备份。0级备份相当于全库备份,但二者并不等同,因为,全库备份不包含增量备份策略。 对users 表空间建立增量备份:RMAN> backup incremental level=0 tablespace users; RMAN> backup incremental level=1 tablespace users; 如果选择了增量备份,请务必启用块修改跟踪,否则,会因
rman系列之进入rman
通过rman的方式无论是备份还是恢复,小生建议,大伙还是先预备两个东东: 1)到mount阶段,因为,缺省下rman的元数据被存在目标数据库控制文件中 2)如果数据库处于open read write状态,那么必须置于归档模式,否则会报ora-19602:错误无法按 NOARCHIVELOG 模式备份或复制活动文件。如何开启归档,请见:点击打开链接http://blog.csdn.n