rman incremental merge 增量备份自动合并 不再需要做多次0级备份

本文主要是介绍rman incremental merge 增量备份自动合并 不再需要做多次0级备份,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

There are several ways to use a Merged Incremental Backup Strategy. However, before implementing the strategy, there are several things to consider when not using the basic Oracle Suggested Strategy as given in EM.  This note will cover the different ways to implement your strategy tailored to fit your business needs.

What is a Merged Incremental Backup?

Merged Incremental creates a level 0 image copy backup of all of your database's datafiles in a disk location.  All datafiles are backed up using the same tag name. The Oracle Database 10g feature Block Change Tracking can be used for the incremental level 1 backups for Fast Incremental Backups.

Once a level 0 backup copy is created on disk there is no need for future level 0 backups to be taken.  This reduces the load and backup window for VLDB systems. All future backups will be level 1 backupsets and are used to recover the image copies on disk thus making the current level 0 image backup copies more current each time the level 1 incremental is applied.  Having the level 0 image copy newer with each level 1 incremental backupsets means there is no need to make another level 0 backup/image copy of your database. 

SOLUTION

First let look at the Enterprise Manager Merged Incremental "Oracle-Suggested Strategy".

Daily Script:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
}

By default the Merged Incremental Strategy creates differential incremental backups. If there are no level 0 copies then the first execution will make level 0 datafile copy backups to the specified location or to the Flash Recovery Area if one is defined in the parameter file of the database.

With the default EM script the image copies will always be 24 hours behind the current incremental backup taken. If the business requires that you keep the image backup more current you can change the recover command to be executed after the backup command so the most current changes are applied to the image copies.

Default behavior for Merged Incremental Backups

First Execution, Day 1:  The 'recover copy' command will show ' no copy of datafile 1 found to recover' as this is the first execution and   no  level 0 backup existing.   The 'backup incremental....' command will make a new level 0 copy as there is no existing level 0.

Second Execution, Day 2:  The 'recover copy' command will show 'no copy of datafile 1 found to recover' as there  is still no previous level 1 backup.  The 'backup incremental...' command will create a level 1 datafile backupset.

Third Execution, Day 3:  The 'recover copy' command will recover the level 0 image copy and displays 'recovering datafile copy fno=....'.   不是recover 生产database的数据

The 'backup incremental....' command will create a new level 1 datafile backupset.   



Future Executions:  Each backup taken after the 3rd should show the same behavior as in backup on Day 3.

The following is an example of making the Merged Incremental Backups so the image copies remain 24 hours behind the incremental backups taken.  This is the same as one described above through EM.  

run {
recover copy of database with tag 'MIB_LEVEL_0';
backup incremental level 1 copies=1 for recover of copy with tag 'MIB_LEVEL_0' database;
}

In this example, the backup and recover commands are flipped.  The backup is taken before the recover statement.  The recover command will apply the most recent level 1 backup.  Thus the image copy backups have the incremental backup applied to them directly after they're taken. This keeps the image copies most current and can be executed several times a day according to your business requirements.

run {
backup incremental level 1 copies=1 for recover of copy with tag 'MIB_LEVEL_0' database;
recover copy of database with tag 'MIB_LEVEL_0';
}

If there is not enough space in the Flash Recovery Area or on a single mount to make image copies of the  entire database, they can be spread across multiple disk mounts. To do this, the initial level 0 image copy must be executed manually. For example, the following performs a backup by tablespace written to different mount points. The key is is using the same tag for backup then again for subsequent recovery commands.

run {
backup as copy incremental level 0 format '/<path>/<mount1>/%U' tag 'MIB_LEVEL_0'
tablespace SYSTEM, UNDOTBS1;
backup as copy incremental level 0 format '/<path>/<mount2>/%U' tag 'MIB_LEVEL_0'
tablespace SYSAUX, USERS;
backup as copy incremental level 0 format '/<path>/<mount3>/%U' tag 'MIB_LEVEL_0'
tablespace <user tablespace name separated by comma>;
 }

After the level 0 image copy backup is created to the respective mount points, the daily script to create incremental backupsets to recover the image copies can be executed. Although the image copies are on different mount points, their use of the same tag will cause RMAN to find the most recent copy with the respective tag to apply the recovery.

It should be noted, that in this case, it is the DBA's responsibility to maintain/take Incremental Level 0 Backups if for example NEW TABLESPACES or DATAFILES are added to the Database. Of course the RMAN Incremental Level 1 Backups will do automatically a Incremental Level 0 Backup if there is none available, but then this automatically created Incremental Level 0 Backup does not go to one of the Destination Mount Points, but to a DEFAULT Location i.e. FRA or $ORACLE_HOME/dbs is FRA is not specified.

run {
backup incremental level 1 for recover of copy with tag 'MIB_LEVEL_0' database;
recover copy of database with tag 'MIB_LEVEL_0';
 }

When using the Oracle-Suggested Strategy or daily Merged Incremental Backup and using a Flash Recovery Area then keep the RMAN Retention Policy set for Redundancy 1.

This will ensure that Oracle space management will automatically remove the level 1 incremental backups from the FRA after they have been applied to the image copy based on space pressure in the FRA. If you increase the redundancy or set a Recovery Window the space will no longer be automatically reclaimed by Oracle. This works only when retention policy is set to the default of redundancy=1. If the configured retention policy is set  to recovery window or to a redundancy > 1, then RMAN cannot satisfy the retention policy if there is only one copy of database and it is at a later point in time. So, in order to satisfy the retention policy Oracle keeps all the incrementals and archivelogs since database creation because ideally a datafile can be re-created and archivelogs can be applied to satisfy the retention policy (though not followed in practical case).

Review:  
Merged Incremental Backup & Backup Retention (Doc ID 351455.1)

When the business requires a retention policy to recovery window of 7 days.  The retention policy can be configured as such by the user. In addition, a customized script using a UNTIL CLAUSE of 8 days must be created.  This will keep the copy of the database to at least 8 days older. This will satisfy the retention policy and make the archivelogs and incremental delete-able from FRA.

Another image copy can be made back to lag the recover using 'SYSDATE-x' for the 'recover the copy' command.  The only caveat is the tag being used and another incremental backup is required using the tag for the copy you wish to recover.

 RECOVER COPY OF DATABASE WITH TAG 'MIB_LEVEL_0' UNTIL TIME "SYSDATE-8" FROM TAG 'MIB_LEVEL_0';

This would keep the copy of database to satisfy the retention policy of 7 days.

Block Change Tracking and Merged Incrementals

If using BCT Block Change Tracking for the level 1 incremental backups you must note the BCT file will only allow up to 8 bitmaps by default. So it can only trace 8 days or 8 incremental backups between each recover command.

 The limit can be increased using the underscore parameter listed in Note: 452455.1

A database with Block Change Tracking enabled and if more than 8 RMAN incremental backups are executed without consolidating them into image copies, then the backup process will be very slow since the Block Change Tracking won't be used in subsequent backups.

The limit is set by the "_bct_bitmaps_per_file" parameter. This parameter sets the number of bitmaps to be stored for each datafile, and its default value is 8. In order to avoid this limit one can either run less than 8 incremental backups or can increase the "_bct_bitmaps_per_file" parameter.

Note:
Verified by Documentation checking clause "FOR RECOVER OF COPY"
to find DEFAULT used for INCREMENTAL MERGE Backup:
.
10gR2: "FOR RECOVER OF COPY" Incremental Merge Backups are by default CUMULATIVE.   (up to a including 10.2.0.4 )
11gR1: "FOR RECOVER OF COPY" Incremental Merge Backups are by default CUMULATIVE.   (up to a including 11.1.0.7 )
11gR2: "FOR RECOVER OF COPY" Incremental Merge Backups are by default DIFFERENTIAL.  >= 11.2.
---------

Reference:
(Doc ID 6459358.8) Bug 6459358 - Differential incremental backups not created for "RECOVER OF COPY WITH TAG"
 Versions confirmed as being affected     
    11.1.0.7
    10.2.0.4
 This issue is fixed in    
    11.2.0.1 (Base Release)
    10.2.0.5 (Server Patch Set)
    10.2.0.4 Patch 32 on Windows Platforms

PURPOSE

To understand and use oracle recommended strategy (incremental merge) for disk only backups to achieve a recovery window of N days.

This note is essentially written to clarify bug# 3826979.

SCOPE

All users of RMAN that have the need of backing up the database to disk only and may use flash recovery area. 

DETAILS

 1.Disk Backup Strategy

The Oracle recommended disk backup strategy is to have:
  a) retention policy is redundancy 1
  b) create a copy of database on disk in flash recovery area
  c) take cumulative incrementals over this copy
  d) rollforward the copy of database daily

To achieve this...

a) configure retention policy once

RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

b, c & d)

The backup script would be like:

run {
 recover copy of database with tag 'ORA_BACKUP';
 backup incremental level 1 Tag 'ORA_BACKUP' for recover of copy Tag 'ORA_BACKUP' database;
}

The first command roll forwards the copy of database with tag ORA_BACKUP to latest point in time by applying incrementals over the backup.

The second command creates an incremental backup with parent as copy of database with tag ORA_BACKUP. If there is no copy of database with tag ORA_BACKUP, then it will create a copy.

  Timeline      first command                       second command
  ========      =============                       ==============
  Day 1         no copy of rollforward              creates a copy of database
  Day 2         no incr to be applied               creates incremental
  Day 3         copy roll forwarded through Day2    creates incremental --- 第三天增量合并,可以恢复到前天
  Day 4         copy roll forwarded through Day3    creates incremental--- 只可以恢复到昨天,如果交换顺序只能当天。
  ...


As you can see that the above script will make the copy one day older at given time. Hence, the script is good to attain a recovery window of 1 days assuming the script is executed every night.
 

2. How to obtain recovery window of N days using disk backup strategy?

Now instead of attaining 1 day recovery window on disk, user may wish to achieve a recovery window of N days. For example, assume user want a recovery window of 15 days.

There are two changes that needed to be done -
  a) change retention policy to recovery window of 15 days;
  b) change backup script to keep copy 15 days older

To achieve this...


a) configure the retention policy once:

RMAN> configure retention policy to recovery window of 15 days;

This configuration is optional. We can obtain recovery window of 15 days with redundancy 1 and using below script. The advantage of changing the configuration is to make sure that RMAN doesn't mark any tape backups (if any) as obsolete that are require to attain 15 day recovery window.


b) The backup script is similar to the below:

     run {
        recover copy of database with tag ORA_BACKUP until time 'sysdate - 16';
        backup device type disk incremental level 1 for recover of copy with TAG ORA_BACKUP database;
     }
 

 We use one day more as 'sysdate-16' to take care of daylight savings.

The first command roll forwards the copy of database with tag ORA_BACKUP to a point in time 16 days older by applying incrementals over the backup.

The second command creates an incremental backup with parent as copy of database with tag ORA_BACKUP. If there is no copy of database with tag ORA_BACKUP, then it will create a copy.

  Timeline      first command                       second command
  ========      =============                       ==============
  Day 1         no copy of rollforward              creates a copy of database
  Day 2         no incr to applied                  creates incremental
  ...
  Day 15        no incr to applied                  creates incremental
  Day 16        copy roll forwarded through Day2    creates incremental------15天内的增量都在,0级还是15天前的。
  Day 17        copy roll forwarded through Day3    creates incremental
  ...


As you can see you can achieve a recovery window of 15 days on disk.

这篇关于rman incremental merge 增量备份自动合并 不再需要做多次0级备份的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/450342

相关文章

浏览器插件cursor实现自动注册、续杯的详细过程

《浏览器插件cursor实现自动注册、续杯的详细过程》Cursor简易注册助手脚本通过自动化邮箱填写和验证码获取流程,大大简化了Cursor的注册过程,它不仅提高了注册效率,还通过友好的用户界面和详细... 目录前言功能概述使用方法安装脚本使用流程邮箱输入页面验证码页面实战演示技术实现核心功能实现1. 随机

k8s上运行的mysql、mariadb数据库的备份记录(支持x86和arm两种架构)

《k8s上运行的mysql、mariadb数据库的备份记录(支持x86和arm两种架构)》本文记录在K8s上运行的MySQL/MariaDB备份方案,通过工具容器执行mysqldump,结合定时任务实... 目录前言一、获取需要备份的数据库的信息二、备份步骤1.准备工作(X86)1.准备工作(arm)2.手

HTML5实现的移动端购物车自动结算功能示例代码

《HTML5实现的移动端购物车自动结算功能示例代码》本文介绍HTML5实现移动端购物车自动结算,通过WebStorage、事件监听、DOM操作等技术,确保实时更新与数据同步,优化性能及无障碍性,提升用... 目录1. 移动端购物车自动结算概述2. 数据存储与状态保存机制2.1 浏览器端的数据存储方式2.1.

一文详解MySQL如何设置自动备份任务

《一文详解MySQL如何设置自动备份任务》设置自动备份任务可以确保你的数据库定期备份,防止数据丢失,下面我们就来详细介绍一下如何使用Bash脚本和Cron任务在Linux系统上设置MySQL数据库的自... 目录1. 编写备份脚本1.1 创建并编辑备份脚本1.2 给予脚本执行权限2. 设置 Cron 任务2

MyBatis Plus 中 update_time 字段自动填充失效的原因分析及解决方案(最新整理)

《MyBatisPlus中update_time字段自动填充失效的原因分析及解决方案(最新整理)》在使用MyBatisPlus时,通常我们会在数据库表中设置create_time和update... 目录前言一、问题现象二、原因分析三、总结:常见原因与解决方法对照表四、推荐写法前言在使用 MyBATis

Python使用smtplib库开发一个邮件自动发送工具

《Python使用smtplib库开发一个邮件自动发送工具》在现代软件开发中,自动化邮件发送是一个非常实用的功能,无论是系统通知、营销邮件、还是日常工作报告,Python的smtplib库都能帮助我们... 目录代码实现与知识点解析1. 导入必要的库2. 配置邮件服务器参数3. 创建邮件发送类4. 实现邮件

Python使用pynput模拟实现键盘自动输入工具

《Python使用pynput模拟实现键盘自动输入工具》在日常办公和软件开发中,我们经常需要处理大量重复的文本输入工作,所以本文就来和大家介绍一款使用Python的PyQt5库结合pynput键盘控制... 目录概述:当自动化遇上可视化功能全景图核心功能矩阵技术栈深度效果展示使用教程四步操作指南核心代码解析

SpringBoot实现文件记录日志及日志文件自动归档和压缩

《SpringBoot实现文件记录日志及日志文件自动归档和压缩》Logback是Java日志框架,通过Logger收集日志并经Appender输出至控制台、文件等,SpringBoot配置logbac... 目录1、什么是Logback2、SpringBoot实现文件记录日志,日志文件自动归档和压缩2.1、

SpringCloud使用Nacos 配置中心实现配置自动刷新功能使用

《SpringCloud使用Nacos配置中心实现配置自动刷新功能使用》SpringCloud项目中使用Nacos作为配置中心可以方便开发及运维人员随时查看配置信息,及配置共享,并且Nacos支持配... 目录前言一、Nacos中集中配置方式?二、使用步骤1.使用$Value 注解2.使用@Configur

Python中合并列表(list)的六种方法小结

《Python中合并列表(list)的六种方法小结》本文主要介绍了Python中合并列表(list)的六种方法小结,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋... 目录一、直接用 + 合并列表二、用 extend() js方法三、用 zip() 函数交叉合并四、用