暂无图片
oracle rman备份认为过期的逻辑
我来答
分享
Edward
2022-10-18
oracle rman备份认为过期的逻辑

1、数据库每天23点进行level 1的累计增量备份,同时为了与其它的备份产生时间上的隔离,加上了keep until time 'sysdate + 1’的命令后备份不自动删除;

2、备份执行脚本如下:

“----------------------------------------`date`---------------------------------------”

source ~/.bash_profile

export FILE=“mwdbbak_inc”$(date +%Y%m%d%H)

rman target / log /backup/dbincbak/${FILE}-LEVEL1.log<<EOF

run{

allocate channel c1 type disk;

allocate channel c2 type disk;

allocate channel c3 type disk;

allocate channel c4 type disk;

crosscheck archivelog all;

crosscheck backupset;

sql ‘alter system checkpoint’;

sql ‘alter system switch logfile’;

backup as compressed backupset incremental level=1 CUMULATIVE database tag=mwdb_bk_level1 format ‘/backup/dbincbak/mwdbbak_level1C_$(date +%Y%m%d%H)_%d_%s_%p.bak’ FILESPERSET 1000 MAXSETSIZE 500000M keep UNTIL TIME ‘sysdate+1’;

sql ‘alter system archive log current’;

backup as compressed backupset tag=mwdb_bkLOG_level1 not backed up 1 times archivelog all format ‘/backup/dbincbak/mvdbArchLog_%d_%T_%s_%p.bak’ FILESPERSET 1000 MAXSETSIZE 500000M keep UNTIL TIME ‘sysdate+1’;

backup as compressed backupset current controlfile tag=mwdb_controlfile_level1 format ‘/backup/dbincbak/controlfile_$(date +%Y%m%d%H)_%d_control.bak’ keep UNTIL TIME ‘sysdate+1’;

delete noprompt expired backupset;

delete noprompt archivelog all completed before ‘sysdate-1’;

delete noprompt obsolete;

release channel c1;

release channel c2;

release channel c3;

release channel c4;

}

exit;

EOF

3、但是查询备份记录发现每天晚上执行的level 1的备份并没有被标记过期,这样也没有被删除
20221018_152205.png

select * from v$BACKUP_SET

RECID STAMP SET_STAMP SET_COUNT BACKUP_TYPE CONTROLFILE_INCLUDED INCREMENTAL_LEVEL PIECES START_TIME COMPLETION_TIME ELAPSED_SECONDS BLOCK_SIZE INPUT_FILE_SCAN_ONLY KEEP KEEP_UNTIL KEEP_OPTIONS MULTI_SECTION
205894 1117671696 1117666820 213986 D NO 0 1 2022-10-09 23:00:20 2022-10-10 00:21:36 4876.000000000000000000000000000000000001 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205895 1117671874 1117666820 213987 D NO 0 1 2022-10-09 23:00:20 2022-10-10 00:24:34 5054.000000000000000000000000000000000003 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205896 1117671969 1117666820 213984 D NO 0 1 2022-10-09 23:00:20 2022-10-10 00:26:09 5148.999999999999999999999999999999999999 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205897 1117672407 1117666820 213985 D NO 0 1 2022-10-09 23:00:20 2022-10-10 00:33:27 5587.000000000000000000000000000000000004 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205898 1117672417 1117672417 213988 D NO null 1 2022-10-10 00:33:37 2022-10-10 00:33:37 0 16384 NO YES 2022-10-17 00:33:37 BACKUP_LOGS NO
205899 1117672425 1117672422 213989 L NO null 1 2022-10-10 00:33:42 2022-10-10 00:33:45 3 512 NO YES 2022-10-17 00:33:42 BACKUP_LOGS NO
205900 1117672426 1117672422 213990 L NO null 1 2022-10-10 00:33:42 2022-10-10 00:33:46 4 512 NO YES 2022-10-17 00:33:42 BACKUP_LOGS NO
205901 1117672427 1117672422 213991 L NO null 1 2022-10-10 00:33:42 2022-10-10 00:33:47 5 512 NO YES 2022-10-17 00:33:42 BACKUP_LOGS NO
205902 1117672434 1117672429 213992 D YES null 1 2022-10-10 00:33:49 2022-10-10 00:33:54 5 16384 NO YES 2022-10-17 00:33:49 BACKUP_LOGS NO
205982 1118190721 1118185220 214075 I NO 1 1 2022-10-15 23:00:20 2022-10-16 00:32:01 5501.000000000000000000000000000000000002 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205983 1118190844 1118190727 214078 I NO 1 1 2022-10-16 00:32:07 2022-10-16 00:34:04 117 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205984 1118190890 1118185221 214077 I NO 1 1 2022-10-15 23:00:21 2022-10-16 00:34:50 5668.999999999999999999999999999999999998 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205985 1118191142 1118185220 214076 I NO 1 1 2022-10-15 23:00:20 2022-10-16 00:39:02 5922.000000000000000000000000000000000003 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205986 1118191331 1118185220 214074 I NO 1 1 2022-10-15 23:00:20 2022-10-16 00:42:11 6111.000000000000000000000000000000000003 8192 NO YES 2022-10-16 23:00:19 BACKUP_LOGS NO
205987 1118191333 1118191332 214079 D NO null 1 2022-10-16 00:42:12 2022-10-16 00:42:13 0.9999999999999999999999999999999999999996 16384 NO YES 2022-10-17 00:42:12 BACKUP_LOGS NO
205988 1118191340 1118191338 214081 L NO null 1 2022-10-16 00:42:18 2022-10-16 00:42:20 2 512 NO YES 2022-10-17 00:42:17 BACKUP_LOGS NO
205989 1118191341 1118191338 214082 L NO null 1 2022-10-16 00:42:18 2022-10-16 00:42:21 3 512 NO YES 2022-10-17 00:42:17 BACKUP_LOGS NO
205990 1118191343 1118191338 214080 L NO null 1 2022-10-16 00:42:18 2022-10-16 00:42:23 5 512 NO YES 2022-10-17 00:42:17 BACKUP_LOGS NO
205991 1118191350 1118191345 214083 D YES null 1 2022-10-16 00:42:25 2022-10-16 00:42:30 5 16384 NO YES 2022-10-17 00:42:25 BACKUP_LOGS NO
205992 1118191387 1118191368 214087 L NO null 1 2022-10-16 00:42:48 2022-10-16 00:43:07 18.99999999999999999999999999999999999996 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205993 1118191439 1118191393 214088 L NO null 1 2022-10-16 00:43:13 2022-10-16 00:43:59 45.99999999999999999999999999999999999996 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205994 1118191448 1118191368 214084 L NO null 1 2022-10-16 00:42:48 2022-10-16 00:44:08 80.00000000000000000000000000000000000001 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205995 1118191449 1118191368 214086 L NO null 1 2022-10-16 00:42:48 2022-10-16 00:44:09 81 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205996 1118191449 1118191449 214089 L NO null 1 2022-10-16 00:44:09 2022-10-16 00:44:09 0 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205997 1118191451 1118191368 214085 L NO null 1 2022-10-16 00:42:48 2022-10-16 00:44:11 82.99999999999999999999999999999999999999 512 NO YES 2022-10-17 00:42:48 BACKUP_LOGS NO
205998 1118191473 1118191468 214090 D YES null 1 2022-10-16 00:44:28 2022-10-16 00:44:33 5 16384 NO YES 2022-10-17 00:44:28 BACKUP_LOGS NO
205999 1118362496 1118358014 214095 I NO 1 1 2022-10-17 23:00:14 2022-10-18 00:14:56 4482 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206000 1118363640 1118358013 214094 I NO 1 1 2022-10-17 23:00:13 2022-10-18 00:34:00 5626.999999999999999999999999999999999999 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206001 1118363772 1118362500 214096 I NO 1 1 2022-10-18 00:15:00 2022-10-18 00:36:12 1271.999999999999999999999999999999999998 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206002 1118363858 1118358013 214092 I NO 1 1 2022-10-17 23:00:13 2022-10-18 00:37:38 5845.000000000000000000000000000000000003 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206003 1118363985 1118363645 214097 D NO 0 1 2022-10-18 00:34:05 2022-10-18 00:39:45 340 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206004 1118364051 1118358013 214093 I NO 1 1 2022-10-17 23:00:13 2022-10-18 00:40:51 6038.000000000000000000000000000000000004 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206005 1118364250 1118363780 214098 D NO 0 1 2022-10-18 00:36:20 2022-10-18 00:44:10 470 8192 NO YES 2022-10-18 23:00:12 BACKUP_LOGS NO
206006 1118364256 1118364256 214099 D NO null 1 2022-10-18 00:44:16 2022-10-18 00:44:16 0 16384 NO YES 2022-10-19 00:44:16 BACKUP_LOGS NO
206007 1118364262 1118364261 214100 L NO null 1 2022-10-18 00:44:21 2022-10-18 00:44:22 0.9999999999999999999999999999999999999996 512 NO YES 2022-10-19 00:44:21 BACKUP_LOGS NO
206008 1118364264 1118364261 214102 L NO null 1 2022-10-18 00:44:21 2022-10-18 00:44:24 3 512 NO YES 2022-10-19 00:44:21 BACKUP_LOGS NO
206009 1118364264 1118364261 214101 L NO null 1 2022-10-18 00:44:21 2022-10-18 00:44:24 3 512 NO YES 2022-10-19 00:44:21 BACKUP_LOGS NO
206010 1118364269 1118364264 214103 D YES null 1 2022-10-18 00:44:24 2022-10-18 00:44:29 5 16384 NO YES 2022-10-19 00:44:24 BACKUP_LOGS NO
206011 1118364341 1118364287 214107 L NO null 1 2022-10-18 00:44:47 2022-10-18 00:45:41 54 512 NO YES 2022-10-19 00:44:46 BACKUP_LOGS NO
206012 1118364343 1118364342 214108 L NO null 1 2022-10-18 00:45:42 2022-10-18 00:45:43 0.9999999999999999999999999999999999999996 512 NO YES 2022-10-19 00:44:46 BACKUP_LOGS NO
206013 1118364368 1118364287 214106 L NO null 1 2022-10-18 00:44:47 2022-10-18 00:46:08 81 512 NO YES 2022-10-19 00:44:46 BACKUP_LOGS NO
206014 1118364370 1118364286 214104 L NO null 1 2022-10-18 00:44:46 2022-10-18 00:46:10 83.99999999999999999999999999999999999998 512 NO YES 2022-10-19 00:44:46 BACKUP_LOGS NO
206015 1118364372 1118364286 214105 L NO null 1 2022-10-18 00:44:46 2022-10-18 00:46:12 85.99999999999999999999999999999999999997 512 NO YES 2022-10-19 00:44:46 BACKUP_LOGS NO
206016 1118364391 1118364386 214109 D YES null 1 2022-10-18 00:46:26 2022-10-18 00:46:31 5 16384 NO YES 2022-10-19 00:46:26 BACKUP_LOGS NO

4、rman备份设置如下:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name EASDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘+FRANDREDG/EASDB/AUTOBACKUP/controlfile_%d_%T_%F_%s.bak’;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
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 ‘+FRANDREDG/easdb/controlfile/snapcf_EASDB.f’;

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘+FRANDREDG/easdb/controlfile/snapcf_easdb.f’;

4、

我来答
添加附件
收藏
分享
问题补充
3条回答
默认
最新
哇哈哈

crosscheck和delete之前执行

RMAN>report obsolete;

作用:

1、对数据文件备份的处理:对于每一个已经备份的数据文件,rman会在保留策略内标识出一个最老的的全数据备份或者0级别备份,如果其它任何数据文件备份比已标识的备份还老则再这一步直接认作obsolete

2、对归档日志文件或者增量备份处理:
首先应该有一个参照,这个参照就是保留策略内最老的非obsolete 全备份或者0级备份。
如果归档文件或者增量备份比标识的非obsolete且最老的full backup 还老,则视为obsolete。
如果归档文件或者增量备份能够被应用在一个非obsolete的全备份或者0级别备份,则归档及增量备份为非obsolete,反之则为obsolete。

暂无图片 评论
暂无图片 有用 2
打赏 0
暂无图片
Thomas

有个疑问,为什么备份片中还有ARCHIVELOG的备份呢?第一条备份语句不是只备份datafile吗?另外,哇哈哈的回答中说 report obsolete有对过期备份打 标记的作用?从字面理解,仅仅是REPORT,不是类似与LIST,只是查询,怎么会更新备份片的状态呢?

暂无图片 评论
暂无图片 有用 0
打赏 0
Edward

 Lists full backups, data file copies, and archived redo log files recorded in the RMAN repository that can be deleted because they are no longer needed. 

  1. For each data file that has been backed up, RMAN identifies the oldest full backup, level 0 backup, or image copy that is not obsolete under the retention policy. Any backup of the data file older than the one identified in this step is considered obsolete.

  2. Any archived redo log files and level 1 incremental backups that are older than the oldest nonobsolete full backup are considered obsolete. These files are obsolete because no full or level 0 backup exists to which they can be applied. Incremental level 1 backups or archived redo log files are not considered obsolete if they can be applied to nonobsolete level 0 or full backups.   
    看官方的解释report 的这个作用就是list和标记 

暂无图片 评论
暂无图片 有用 0
打赏 0
回答交流
Markdown


请输入正文
提交
相关推荐
rac+dg版本升级
回答 1
可参考这篇文章:https://blog.csdn.net/qq16729455/article/details/107044671
drop table 后会记录到v$sql等动态日志里面吗?除过recyclebin,哪块还有drop的记录?为什么找不到执行语句
回答 5
任何SQL语句都是需要优化器解析的,只要没有ageout出sharepool就可以在V$SQL类似动态性能视图中查到
Oracle set unused 命令
回答 3
已采纳
这不就是为了减少从大表中删除列时可能出现的数据库高负载情况发生么。业务高峰时段切断生产中对列的访问而没有I/O延迟,将列标记为未使用,然后在以后非高峰时段进行物理删除。
怎么查询某个用户在某段时间内执行过的所有SQL语句
回答 2
看awr快照保留配置,如果在查询范围内,可以通过以下几个视图查看:dbahistactivesesshistory,dbahistsqltext,dbausers;使用commandtype可过滤语句
Oracle exp导出分区表报错:EXP-00006: 出现内部不一致的错误 ,EXP-00000: 导出终止失败
回答 1
已采纳
exp的bug吧,使用exp到11g的新特性间隔分区表时报EXP00006:出现内部不一致的错误。如果无法登录oracle所在的服务器用expdp导出,应该就只能备份了吧
Oracle19c 配ords 20.2 链接报错分派挂钩引发内部错误,已中止处理。请问有人知道原因吗?
回答 1
升级问题到:紧急故障
要迁移oracle数据库,迁移前要给客户提供迁移评估报告,有什么工具能实现?
回答 3
从Oracle到Oracle?还是?
oracle JDBC驱动oci和thin区别
回答 2
已采纳
thin底层是通过tcp/ip协议实现的。oci是通过调用oci客户端动态库实现的。ocijdbc使用之前必须要安装oci客户端,所以我们通常会选择thin驱动来连接oracle数据库。理论上ocij
oracle怎么查整个库里某个时间后有新增或修改的库?
回答 1
已采纳
通过v$database查看创建时间
ogg 抽取进程报错
回答 1
ORA12805:parallelqueryserverdied并行查询服务器died,需要检查数据库是否正常,查看alert日志。此错误由并行SQL的QC(查询协调器)抛出。此错误通常是由“检测到I