RAC下RMAN备份的一些问题 - RMAN脚本分配通道连接不同的节点

最新推荐文章于 2022-04-03 15:44:51 发布

文档搬运工

最新推荐文章于 2022-04-03 15:44:51 发布

阅读量657

点赞数

分类专栏： RMAN

本文链接：https://blog.csdn.net/xxzhaobb/article/details/82980698

版权

RMAN 专栏收录该内容

43 篇文章 0 订阅

订阅专栏

最近RAC下的一个备份脚本，在分配通道的时候，发现不同的通道连接到了不同的节点上。这样也存在一些弊端，比如备份文件是分散在两个不同的节点上的。而且备份数据不是均匀分布的。主要还是看美每个通道都备份了那些表空间等等

--两个节点上的目录路径都一样，比如都有/rmanbackup这个文件夹

以下是测试过程

[oracle@node1 ~]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 9 17:59:50 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: RAC (DBID=2505207930)

RMAN> run{
allocate channel c1 type disk connect sys/oracle@rac1;
allocate channel c2 type disk connect sys/oracle@rac2;
crosscheck backup;
crosscheck archivelog all;
sql 'alter system archive log current';
backup  tag='cmd_data' database format '/rmanbackup/CDM2> /%d_%T_%s.data';
backup  tag='cdm_arch' archivelog all format '/rmanbackup/CDM/%d_%T_%s.arch';
backup current controlfile format '/rmanbackup/CDM/%d_%T_%s.ctl';
backup spfile format '/rmanbackup/CDM/%d_%T_%s.spf';
crosscheck backup;
delete noprompt expired backup;
delete noprompt backup completed before 'sysdate -3';
crosscheck archivelog all;
delete noprompt archivelog until time 'sysdate-3';
release channel c1;3> 
release channel c2;
}4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 

using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=32 instance=RAC1 device type=DISK

allocated channel: c2
channel c2: SID=30 instance=RAC2 device type=DISK

specification does not match any backup in the repository

specification does not match any archived log in the repository

sql statement: alter system archive log current

Starting backup at 09-OCT-18
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
input datafile file number=00002 name=+ASMDISK/rac/datafile/sysaux.257.917225827
input datafile file number=00004 name=+ASMDISK/rac/datafile/users.259.917225827
channel c1: starting piece 1 at 09-OCT-18
channel c2: starting full datafile backup set
channel c2: specifying datafile(s) in backup set
input datafile file number=00001 name=+ASMDISK/rac/datafile/system.256.917225827
input datafile file number=00003 name=+ASMDISK/rac/datafile/undotbs1.258.917225827
input datafile file number=00005 name=+ASMDISK/rac/datafile/undotbs2.267.917226053
channel c2: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_1.data tag=CMD_DATA comment=NONE
channel c1: backup set complete, elapsed time: 00:00:46
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
channel c1: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_3.data tag=CMD_DATA comment=NONE
channel c1: backup set complete, elapsed time: 00:00:04
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current SPFILE in backup set
channel c1: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_4.data tag=CMD_DATA comment=NONE
channel c1: backup set complete, elapsed time: 00:00:04
channel c2: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_2.data tag=CMD_DATA comment=NONE
channel c2: backup set complete, elapsed time: 00:00:52
Finished backup at 09-OCT-18

Starting backup at 09-OCT-18
current log archived
channel c1: starting archived log backup set
channel c1: specifying archived log(s) in backup set
input archived log thread=2 sequence=62 RECID=2 STAMP=989085627
input archived log thread=1 sequence=124 RECID=1 STAMP=989085626
channel c1: starting piece 1 at 09-OCT-18
channel c2: starting archived log backup set
channel c2: specifying archived log(s) in backup set
input archived log thread=1 sequence=125 RECID=3 STAMP=989085721
input archived log thread=2 sequence=63 RECID=4 STAMP=989085721
channel c2: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_5.arch tag=CDM_ARCH comment=NONE
channel c1: backup set complete, elapsed time: 00:00:02
channel c2: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_6.arch tag=CDM_ARCH comment=NONE
channel c2: backup set complete, elapsed time: 00:00:07
Finished backup at 09-OCT-18

Starting backup at 09-OCT-18
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
channel c1: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_7.ctl tag=TAG20181009T180218 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 09-OCT-18

Starting backup at 09-OCT-18
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current SPFILE in backup set
channel c1: starting piece 1 at 09-OCT-18
channel c1: finished piece 1 at 09-OCT-18
piece handle=/rmanbackup/CDM/RAC_20181009_8.spf tag=TAG20181009T180224 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 09-OCT-18

crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_1.data RECID=1 STAMP=989085633
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_3.data RECID=2 STAMP=989085687
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_4.data RECID=3 STAMP=989085694
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_5.arch RECID=5 STAMP=989085723
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_7.ctl RECID=7 STAMP=989085742
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_8.spf RECID=8 STAMP=989085744
Crosschecked 6 objects

crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_2.data RECID=4 STAMP=989085666
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/rmanbackup/CDM/RAC_20181009_6.arch RECID=6 STAMP=989085724
Crosschecked 2 objects


specification does not match any backup in the repository

specification does not match any backup in the repository

validation succeeded for archived log
archived log file name=+ASMDISK/rac/archivelog/2018_10_09/thread_1_seq_124.273.989085623 RECID=1 STAMP=989085626
validation succeeded for archived log
archived log file name=+ASMDISK/rac/archivelog/2018_10_09/thread_1_seq_125.275.989085719 RECID=3 STAMP=989085721
validation succeeded for archived log
archived log file name=+ASMDISK/rac/archivelog/2018_10_09/thread_2_seq_62.274.989085627 RECID=2 STAMP=989085627
validation succeeded for archived log
archived log file name=+ASMDISK/rac/archivelog/2018_10_09/thread_2_seq_63.276.989085721 RECID=4 STAMP=989085721
Crosschecked 4 objects


List of Archived Log Copies for database with db_unique_name RAC
=====================================================================

Key     Thrd Seq     S Low Time 
------- ---- ------- - ---------
2       2    62      A 01-OCT-18
        Name: +ASMDISK/rac/archivelog/2018_10_09/thread_2_seq_62.274.989085627

deleted archived log
archived log file name=+ASMDISK/rac/archivelog/2018_10_09/thread_2_seq_62.274.989085627 RECID=2 STAMP=989085627
Deleted 1 objects


released channel: c1

released channel: c2

RMAN>

通过以上的RMAN log，可以看到不同的通道，产生了不同的备份文件：
通道1 ，备份的是sysaux和users表空间，生成的备份文件是RAC_20181009_1.data、RAC_20181009_3.data，RAC_20181009_4.data，RAC_20181009_5.arch，RAC_20181009_7.ctl，RAC_20181009_8.spf
通道2 ，备份的是system,undotbs1,undotbs2 表空间。生成的备份文件是RAC_20181009_2.data，RAC_20181009_6.arch，

在两个节点上查看产生的备份文件，与上面各个通道产生的备份文件吻合（也就是说，备份文件分散到了不同的节点上）
-- 节点1 ，注意文件后面的1-8序号

[oracle@node1 CDM]$ ll
total 908620
-rw-r----- 1 oracle oinstall 889077760 Oct  9 18:01 RAC_20181009_1.data
-rw-r----- 1 oracle oinstall  18546688 Oct  9 18:01 RAC_20181009_3.data
-rw-r----- 1 oracle oinstall     98304 Oct  9 18:01 RAC_20181009_4.data
-rw-r----- 1 oracle oinstall   4051456 Oct  9 18:02 RAC_20181009_5.arch
-rw-r----- 1 oracle oinstall  18546688 Oct  9 18:02 RAC_20181009_7.ctl
-rw-r----- 1 oracle oinstall     98304 Oct  9 18:02 RAC_20181009_8.spf
[oracle@node1 CDM]$

--节点2

[oracle@node2 CDM]$ ll
total 653196
-rw-r----- 1 oracle oinstall 668852224 Oct  9 18:01 RAC_20181009_2.data
-rw-r----- 1 oracle oinstall     14336 Oct  9 18:02 RAC_20181009_6.arch
[oracle@node2 CDM]$

RMAN上验证：
-- 节点2上登录RMAN，查看表空间sysaux的备份，显示备份文件是/rmanbackup/CDM/RAC_20181009_1.data

[oracle@node2 CDM]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 9 18:14:40 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: RAC (DBID=2505207930)

RMAN> list backup of tablespace sysaux;

using target database control file instead of recovery catalog

List of Backup Sets
===================


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
1       Full    847.88M    DISK        00:00:44     09-OCT-18      
        BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: CMD_DATA
        Piece Name: /rmanbackup/CDM/RAC_20181009_1.data
  List of Datafiles in backup set 1
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  2       Full 7402886    09-OCT-18 +ASMDISK/rac/datafile/sysaux.257.917225827

RMAN>

-- 在节点2上进行查看该文件，是不存在的，因为该文件在节点1上。

[root@node2 u01]# ll /rmanbackup/CDM/RAC_20181009_1.data
ls: cannot access /rmanbackup/CDM/RAC_20181009_1.data: No such file or directory
[root@node2 u01]# 

[oracle@node1 CDM]$ ll /rmanbackup/CDM/RAC_20181009_1.data
-rw-r----- 1 oracle oinstall 889077760 Oct  9 18:01 /rmanbackup/CDM/RAC_20181009_1.data
[oracle@node1 CDM]$

结论：通过这样的方式备份，分配通道到了不同的节点上。会在不同的节点上产生备份，但是每个节点上的备份不是一个完整的数据库备份。其实是把一个数据库的备份文件，分散到了两个节点上。

END

文档搬运工

关注

0
点赞
踩
3

收藏

觉得还不错? 一键收藏
0
评论
RAC下RMAN备份的一些问题 - RMAN脚本分配通道连接不同的节点

最近RAC下的一个备份脚本，在分配通道的时候，发现不同的通道连接到了不同的节点上。这样也存在一些弊端，比如备份文件是分散在两个不同的节点上的。而且备份数据不是均匀分布的。主要还是看美每个通道都备份了那些表空间等等--两个节点上的目录路径都一样，比如都有/rmanbackup这个文件夹以下是测试过程[oracle@node1 ~]$ rman target /Recovery M...
复制链接

扫一扫