Backup Optimization for SBT Backups With Redundancy Retention Policy

ocp 053

703. Given below are RMAN commands to enable ba ckup optimization and set  the retention policy:

The USERS tablespace has never been backed up. Y ou take the USERS tablespace offline on Monday.

View the Exhibit to examine the operations performed by using RMAN. Which two statements are true

about the backup of the USERS tablespace? (Choose two.)

A.It will be backed up as a part of database backup on Friday.

B.It will be backed up as a part of database backup on Tuesday.

C.It will not be backed up as a part of database backup on Wednesday.

D.The command on Sunday deletes the backup of the USERS tablespace taken on Tuesday.

Answer: AB

答案解析:

从以下答案指导BD正确。

参考:http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV89464

Backup Optimization for SBT Backups With Redundancy Retention Policy

Assume that you configure a retention policy for redundancy. In this case, RMAN only skips backups of offline or read-only data files to SBT when there are r + 1 backups of the files, where r is set in CONFIGURE RETENTION POLICY TO REDUNDANCY r.

For example, assume that you enable backup optimization and set the following retention policy:

CONFIGURE DEFAULT DEVICE TYPE TO sbt;

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

With these settings, RMAN only skips backups when three identical files are already backed up. Also assume that you have never backed up the userstablespace, which is read/write, and that you perform the actions described in Table 5-5 over the course of the week.

Table 5-5 Effect of Redundancy Setting on Backup Optimization

Day Action Result Redundant Backup

Monday


Take users offline normal.

   

Tuesday


BACKUP DATABASE


The users tablespace is backed up.

 

Wednesday


BACKUP DATABASE


The users tablespace is backed up.

 

Thursday


BACKUP DATABASE


The users tablespace is backed up.


Tuesday backup


Friday


BACKUP DATABASE


The users tablespace is not backed up.


Tuesday backup


Saturday


BACKUP DATABASE


The users tablespace is not backed up.


Tuesday backup


Sunday


DELETE OBSOLETE


The Tuesday backup is deleted.

 

Monday


BACKUP DATABASE


The users tablespace is backed up.


Wednesday backup

The backups on Tuesday, Wednesday, and Thursday back up the offline users tablespace to satisfy the condition that three backups must exist (one more than redundancy setting). The Friday and Saturday backups do not back up the users tablespace because of backup optimization. The Tuesday backup of users is obsolete beginning on Thursday.

On Sunday, you delete all obsolete backups, which removes the Tuesday backup of users. The Tuesday backup is obsolete because of the retention policy setting. The whole database backup on Monday then backs up the users tablespace to satisfy the condition that three backups must exist (one more than redundancy setting). In this way, you can recycle your tapes over time.

RMAN> show all;

RMAN configuration parameters for database with db_unique_name TEST0221 are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

CONFIGURE BACKUP OPTIMIZATION ON;

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 ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM ‘AES128‘; # default

CONFIGURE COMPRESSION ALGORITHM ‘BASIC‘ AS OF RELEASE ‘DEFAULT‘ OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_test0221.f‘; # default

RMAN> list backup;

specification does not match any backup in the repository

RMAN> sql ‘alter tablespace users offline‘;----------星期一offline

sql statement: alter tablespace users offline

RMAN> backup database; -----------------星期二,全库备份

Starting backup at 06-MAR-14

using channel ORA_DISK_1

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/test0221/system01.dbf

input datafile file number=00002 name=/u01/app/oracle/oradata/test0221/sysaux01.dbf

input datafile file number=00005 name=/u01/app/oracle/oradata/test0221/example01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/test0221/undotbs01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/test0221/users01.dbf

channel ORA_DISK_1: starting piece 1 at 06-MAR-14

channel ORA_DISK_1: finished piece 1 at 06-MAR-14

piece handle=/u01/app/oracle/fast_recovery_area/TEST0221/backupset/2014_03_06/o1_mf_nnndf_TAG20140306T123613_9khysyg0_.bkp tag=TAG20140306T123613 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 06-MAR-14

channel ORA_DISK_1: finished piece 1 at 06-MAR-14

piece handle=/u01/app/oracle/fast_recovery_area/TEST0221/backupset/2014_03_06/o1_mf_ncsnf_TAG20140306T123613_9khyxm0v_.bkp tag=TAG20140306T123613 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02

Finished backup at 06-MAR-14

RMAN> backup database;----------星期三全库备份

Starting backup at 06-MAR-14

using channel ORA_DISK_1

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/test0221/system01.dbf

input datafile file number=00002 name=/u01/app/oracle/oradata/test0221/sysaux01.dbf

input datafile file number=00005 name=/u01/app/oracle/oradata/test0221/example01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/test0221/undotbs01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/test0221/users01.dbf

channel ORA_DISK_1: starting piece 1 at 06-MAR-14

channel ORA_DISK_1: finished piece 1 at 06-MAR-14

piece handle=/u01/app/oracle/fast_recovery_area/TEST0221/backupset/2014_03_06/o1_mf_nnndf_TAG20140306T123854_9khyyyqz_.bkp tag=TAG20140306T123854 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:56

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 06-MAR-14

channel ORA_DISK_1: finished piece 1 at 06-MAR-14

piece handle=/u01/app/oracle/fast_recovery_area/TEST0221/backupset/2014_03_06/o1_mf_ncsnf_TAG20140306T123854_9khz2mf1_.bkp tag=TAG20140306T123854 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 06-MAR-14

Backup Optimization for SBT Backups With Redundancy Retention Policy

时间: 2024-11-07 11:57:05

Backup Optimization for SBT Backups With Redundancy Retention Policy的相关文章

Rman备份的保留策略(retention policy)

什么是备份的保留策略(retention policy) 保留策略就是指某份备份是否要保留以及保留多久.可以使用configure retention policy命令来创建一个一致的.自动的备份保留策略. 当一个备份策略生效后,rman就认为数据文件.控制文件的备份是obsolete的,也就是说根据用户配置,不再需要这些备份进行恢复.用户可以使用report obsolete命令找出obsolete的文件并使用delete obsolete将其删除. 随着备份次数的增加,老的备份文件会变得ob

【oracle】oracledba23 change the backup retention policy to retain the backups for a sma ller period o

An RMAN backup job fails, displaying the following error: ORA-19809: limit exceeded for recovery files Your analysis shows that the Flash Recovery area is full. Which two a ctions could you take to resolve the error and avoid this error in th e futur

backup命令中的 keep forever关键字会 屏蔽rman的retention policy

众所周知,Oracle Rman的retention policy 在任意一个时刻:只能有一个生效.也就是说,两个retention policy 之间是or的关系. 如下使用catalog数据库完成,因为backup 命令的keep forever关键字只支持catalog [[email protected] ~]$ rman target / catalog rc/[email protected] Recovery Manager: Release 10.2.0.1.0 - Produc

Influx Sql系列教程二:retention policy 保存策略

retention policy这个东西相比较于传统的关系型数据库(比如mysql)而言,是一个比较新的东西,在将表之前,有必要来看一下保存策略有什么用,以及可以怎么用 I. 基本操作 1. 创建retention policy retention policy依托于database存在,也就是说保存策略创建时,需要指定具体的数据库,语法如下 CREATE RETENTION POLICY <retention_policy_name> ON <database_name> DUR

TFS 2013 生成(构建)历史记录保持策略(Retention Policy)

TFS服务器通过自动构建,实现软件生成和发布的自动化过程,这一直是TFS系统中非常重要的一个功能模块.近年来发布的TFS版本,都在自动化构建方面大幅增强了相应的功能.在这篇博客里我主要总结TFS 2013的生成记录保留策略的问题. 在TFS系统中,每次生成结束以后都会产生大量的临时数据,例如输出版本.日志信息.标签.测试用例记录等.这些信息长期保留在系统中,不仅没有太大的价值,对系统的维护也会造成很大的麻烦.因此需要设置一个合理的保留策略,以提高系统的使用性能. 在TFS 2013中,生成的保留

配置RMAN备份环境

关于配置RMAN备份环境你可以给每个目标数据库设置一些固定的配置,这些配置控制着RMAN多个方面的行为.例如,你可配置备份的保存策略.默认的备份目录.默认的备份设备类型等.你可以用show命令来查看配置及用configure来修改RMAN的配置. 1.查看和清除RMAN配置参数show命令可以查看RMAN当前的配置情况,以及这些参数当前是否设置了默认值.SHOW ALL; --查看说有的配置情况 你也可以通过SHOW命令加指定的配置参数的名字来查看它的值.例:SHOW RETENTION POL

转 RMAN: RAC Backup, Restore and Recovery using RMAN

PURPOSE The purpose of this document is to give a quick guide for using RMAN on RAC databases. We will follow this points: 1. Verify the database mode and archive destination.2. Verify connectivity using sqlnet for target and catalog.3. Determine the

rman multisection backup试验之一

multisection backup是Oracle11g(确切的说是从11.1.0.6开始)的新特性,见mos文章 MultiSection Backups (文档 ID 406295.1) 下面来做实验: [[email protected] ~]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Thu Feb 19 01:07:28 2015 Copyright (c) 1982, 2011, Orac

Setting Up and Configuring Backup and Recovery1

3.Setting Up and Configuring Backup and Recovery 这个单元讲述如何启动.与rman client如何互动,准备rman环境,实现备份和恢复策略 注意:尽管闪回数据库和安全还原点不是真的数据库备份,但是它们是数据保护策略一个重要部分.这些特性需要一些初始化设置,这些设置依赖于在备份策略中你怎么混合它们.Chapter 5-Data Protection with Restore Points andFlashback Database 提供了关于怎么