在备库上进行热备份--11.2.0.4之后

本文涉及的产品
日志服务 SLS,月写入数据量 50GB 1个月
简介: 一个经典的备份语句:backup database plus archivelog;

一个经典的备份语句:backup database plus archivelog;

完成的4个步骤:

  1. 备份现有的归档日志
  2. 备份数据文件
  3. 归档当前日志
  4. 再次备份归档日志

在备库上执行这条语句在第3步时可能会遇到问题。

用os用户登录rman时,不能滚主库的归档

[oracle@dg121-2 ~]$ rman target /
Recovery Manager: Release 12.1.0.2.0 - Production on Tue Sep 8 19:29:13 2020
Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.
connected to target database: ORCL (DBID=1461820645, not open)
RMAN> 2> 3> 4> 5> 6> 7> 
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=363 device type=SBT_TAPE
channel c1: DBackup3 Oracle MMS Library
Starting backup at Sep 08 2020 19:29:24
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database: 
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
channel c1: starting archived log backup set

用数据库用户sys或sysbackup登录可以滚主库的归档

[oracle@dg121-2 ~]$ rman target sys/dingjia
Recovery Manager: Release 12.1.0.2.0 - Production on Tue Sep 8 19:31:14 2020
Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.
connected to target database: ORCL (DBID=1461820645, not open)
RM                                    
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "advise, allocate, alter, analyze, associate statistics, audit, backup, begin, @, call, catalog, change, comment, commit, configure, connect, convert, copy, create, create catalog, create global, create script, create virtual, crosscheck, declare, delete, delete from, describe, describe catalog, disassociate statistics, drop, drop catalog, drop database, duplicate, exit, explain plan, flashback, flashback table, grant, grant catalog, grant register, host, import, insert, list, lock, merge, mount, noaudit, open, print, purge, quit, recover, register, release, rename, repair, replace, report, "
RMAN-01008: the bad identifier was: �
RMAN-01007: at line 1 column 1 file: standard input
RMAN> 
run{
allocate channel c1 type 'sbt_tape' parms='
SBT_LIBRARY=/opt/scutech/dbackup3/lib/libobk.so,
ENV=(URL=http://192.168.87.155:50306/d2/data/0d36020eecec11ea8000b49691622ac4/c7873e9aed0811ea8000b49691622ac4,
EXTRA=X-Access-Key:ea5350ac00fa61d08533a729da808de0)' trace=0;
backup database plus archivelog delete input;
}
RMAN> 2> 3> 4> 5> 6> 7> 
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=363 device type=SBT_TAPE
channel c1: DBackup3 Oracle MMS Library
Starting backup at Sep 08 2020 19:31:31
current log archived at primary database
channel c1: starting archived log backup set
channel c1: specifying archived log(s) in backup set
input archived log thread=1 sequence=273 RECID=166 STAMP=1050607241
input archived log thread=1 sequence=274 RECID=167 STAMP=1050607891
.....

检查备份集


RMAN> list backup summary;
163     B  A  A SBT_TAPE    Sep 08 2020 19:31:34 1       1       NO         TAG20200908T193133
164     B  F  A SBT_TAPE    Sep 08 2020 19:32:02 1       1       NO         TAG20200908T193135
165     B  F  A SBT_TAPE    Sep 08 2020 19:32:21 1       1       NO         TAG20200908T193135
166     B  F  A SBT_TAPE    Sep 08 2020 19:32:31 1       1       NO         TAG20200908T193135
167     B  F  A SBT_TAPE    Sep 08 2020 19:32:34 1       1       NO         TAG20200908T193135
168     B  A  A SBT_TAPE    Sep 08 2020 19:32:36 1       1       NO         TAG20200908T193236
RMAN>  list backup tag TAG20200908T193236;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time     
------- ---------- ----------- ------------ --------------------
168     256.00K    SBT_TAPE    00:00:00     Sep 08 2020 19:32:36
        BP Key: 168   Status: AVAILABLE  Compressed: NO  Tag: TAG20200908T193236
        Handle: 59v9u0ak_1_1   Media: 59v9u0ak_1_1
  List of Archived Logs in backup set 168
  Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
  ---- ------- ---------- -------------------- ---------- ---------
  1    275     10389987   Sep 08 2020 19:31:11 10390124   Sep 08 2020 19:32:14



我们可以看到最后一个备份集是归档日志,这个归档日志的时间范围正好cover整个备份过程,当然我们这个备份的时间跨度不算长,我们有客户100多T的数据库,通过光纤备份要10多个小时,在备份过程中大约会产生1T的数据,这样最后一个归档的备份集就不只包含一个归档日志了。


相关实践学习
通过日志服务实现云资源OSS的安全审计
本实验介绍如何通过日志服务实现云资源OSS的安全审计。
相关文章
|
网络协议 Linux
route 或 ip route命令详解
【4月更文挑战第9天】`route`和`ip route`是Linux下管理IP路由的命令,用于查看和配置路由表。`route`命令简单,可查看、添加和删除路由,而`ip route`更现代且功能强大,支持路由可信度和距离设置。`ip route show`类似于`route -n`用于显示路由信息。路由类型包括主机、网络和默认路由。在现代Linux系统中,推荐使用`ip route`。
2080 1
|
存储 负载均衡 调度
Docker 多主机部署:构建容器集群的最佳实践,助力高可用性与负载均衡
Docker 多主机部署:构建容器集群的最佳实践,助力高可用性与负载均衡
1160 0
|
SQL 关系型数据库 MySQL
TiDB安装简介
TiDB安装简介
2744 0
|
关系型数据库 MySQL Linux
Linux7部署 Mysql初始化报错GLIBC_2.28处理
Linux7部署 Mysql初始化报错GLIBC_2.28处理
2240 0
Linux7部署 Mysql初始化报错GLIBC_2.28处理
|
网络协议 Linux Python
Linux如何后台运行服务
Linux如何后台运行服务
299 0
|
11月前
|
负载均衡 Oracle 网络协议
Oracle中TAF与SCANIP全面解析
通过本文的解析,读者可以清晰地理解Oracle中TAF与SCAN IP的概念、工作原理及其在实际应用中的优势和局限性。TAF通过自动故障转移提升了会话的高可用性,而SCAN则通过简化客户端连接和负载均衡提升了集群的可管理性和扩展性。这两种技术在现代企业数据库架构中扮演着重要角色,能够显著提高系统的稳定性和可用性。
438 6
|
存储 监控 安全
得物 ZooKeeper SLA 也可以 99.99%丨最佳实践
在本文中,作者探讨了ZooKeeper(ZK)的一个内存占用问题,特别是当有大量的Watcher和ZNode时,导致的内存消耗。
44078 117
|
前端开发 C++
CSS【详解】 标准盒模型 VS IE 盒模型
CSS【详解】 标准盒模型 VS IE 盒模型
186 0
|
负载均衡 算法 容灾
slb基础概念
【9月更文挑战第2天】
3711 25
|
存储 负载均衡 数据管理
OceanBase分区表优势
【8月更文挑战第13天】OceanBase分区表优势
246 7