[20170208]rman tape.txt

[20170208]rman tape.txt

--前一阵子,同事测试使用磁带做rman备份,留下一些备份信息在控制文件,要清除.
--我依稀记得我以前也干过这些事情,晚上看了一下书:

Apress.RMAN.Recipes.for.Oracle.Database.12c.2nd.Edition.Jul.2013.pdf

Allocating an RMAN Maintenance Channel P145

Suppose your current backup strategy uses only disk, but you have several old tape backups you want to get rid of.
You can allocate a maintenance channel for performing the deletion of the tape backups by using the dummy sbt API
(because the media manager isn't available any longer). You can then use the delete obsolete command to remove
the tape backups. Here's an example showing how to do those things:
 
RMAN> allocate channel for maintenance device type sbt
      parms 'SBT_LIBRARY=oracle.disksbt,
      ENV=(BACKUP_DIR=/tmp)';
 
RMAN> delete obsolete;

--allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/u01/backup)';
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;

--//在自己测试环境做一下测试:

1.环境:
SCOTT@book> @ &r/ver1
PORT_STRING                    VERSION        BANNER
------------------------------ -------------- --------------------------------------------------------------------------------
x86_64/Linux 2.4.xx            11.2.0.4.0     Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

--//在rman下执行:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;

RMAN> backup datafile 6 ;
Starting backup at 2017-02-10 10:08:01
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting full datafile backup set
channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/mnt/ramdisk/book/tea01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 2017-02-10 10:08:01
channel ORA_SBT_TAPE_1: finished piece 1 at 2017-02-10 10:08:02
piece handle=5grs7g41_1_1 tag=TAG20170210T100801 comment=API Version 2.0,MMS Version 8.1.3.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:01
Finished backup at 2017-02-10 10:08:02

$ ls -ltr /u01/backup/
total 191240
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 10:08:01 5grs7g41_1_1
-rw-r--r-- 1 oracle oinstall     3360 2017-02-10 10:08:02 Oracle_Disk_SBT_Catalog
-rw-r--r-- 1 oracle oinstall 16777232 2017-02-10 10:08:02 c-1337401710-20170210-01

--//建立了3个文件.

RMAN> list backupset ;
using target database control file instead of recovery catalog
List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
155     Full    8.00M      SBT_TAPE    00:00:00     2017-02-10 10:08:01
        BP Key: 155   Status: AVAILABLE  Compressed: NO  Tag: TAG20170210T100801
        Handle: 5grs7g41_1_1   Media: /backup,5grs7g41_1_1
  List of Datafiles in backup set 155
  File LV Type Ckp SCN    Ckp Time            Name
  ---- -- ---- ---------- ------------------- ----
  6       Full 13276136948 2017-02-10 10:08:01 /mnt/ramdisk/book/tea01.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
156     Full    16.00M     SBT_TAPE    00:00:00     2017-02-10 10:08:02
        BP Key: 156   Status: AVAILABLE  Compressed: NO  Tag: TAG20170210T100802
        Handle: c-1337401710-20170210-01   Media: /backup,c-1337401710-201702
  SPFILE Included: Modification time: 2017-02-10 08:53:36
  SPFILE db_unique_name: BOOK
  Control File Included: Ckp SCN: 13276136955   Ckp time: 2017-02-10 10:08:02

--//假设现在的环境如下:
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO disk;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
released channel: ORA_SBT_TAPE_1

RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear;

old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
old RMAN configuration parameters are successfully deleted
released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
released channel: ORA_SBT_TAPE_1

RMAN> show all ;
RMAN configuration parameters for database with db_unique_name BOOK are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 3 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 '/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs/snapcf_book.f'; # default

--//这样的情况下是无法剔除backupset 155,156.

RMAN> delete backupset 155,156;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=56 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=68 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=80 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 02/10/2017 10:14:52
RMAN-06160: no backup pieces found for backup set key: 155

RMAN> crosscheck backupset;
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
specification does not match any backup in the repository

RMAN> list backupset ;
List of Backup Sets
===================
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
155     Full    8.00M      SBT_TAPE    00:00:00     2017-02-10 10:08:01
        BP Key: 155   Status: AVAILABLE  Compressed: NO  Tag: TAG20170210T100801
        Handle: 5grs7g41_1_1   Media: /backup,5grs7g41_1_1
  List of Datafiles in backup set 155
  File LV Type Ckp SCN    Ckp Time            Name
  ---- -- ---- ---------- ------------------- ----
  6       Full 13276136948 2017-02-10 10:08:01 /mnt/ramdisk/book/tea01.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
156     Full    16.00M     SBT_TAPE    00:00:00     2017-02-10 10:08:02
        BP Key: 156   Status: AVAILABLE  Compressed: NO  Tag: TAG20170210T100802
        Handle: c-1337401710-20170210-01   Media: /backup,c-1337401710-201702
  SPFILE Included: Modification time: 2017-02-10 08:53:36
  SPFILE db_unique_name: BOOK
  Control File Included: Ckp SCN: 13276136955   Ckp time: 2017-02-10 10:08:02

2.如何清除呢?

RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tmp)';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tmp)';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
--//我使用不同的目录.

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;

old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters are successfully stored

--//首先标志EXPIRED.
RMAN> crosscheck backupset;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=56 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=68 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=80 device type=DISK
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=90 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: WARNING: Oracle Test Disk API
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=5grs7g41_1_1 RECID=155 STAMP=935575681
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-1337401710-20170210-01 RECID=156 STAMP=935575682
Crosschecked 2 objects

RMAN> delete backupset 155,156;
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_SBT_TAPE_1
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
155     155     1   1   EXPIRED     SBT_TAPE    5grs7g41_1_1
156     156     1   1   EXPIRED     SBT_TAPE    c-1337401710-20170210-01

Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=5grs7g41_1_1 RECID=155 STAMP=935575681
deleted backup piece
backup piece handle=c-1337401710-20170210-01 RECID=156 STAMP=935575682
Deleted 2 objects

$ ls -ltr /u01/backup/
total 24620
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 10:08:01 5grs7g41_1_1
-rw-r--r-- 1 oracle oinstall     3360 2017-02-10 10:08:02 Oracle_Disk_SBT_Catalog
-rw-r--r-- 1 oracle oinstall 16777232 2017-02-10 10:08:02 c-1337401710-20170210-01
--//可以发现文件还在.

4.配置要注意一点:
--//DEVICE类型SBT_TAPE要与原先的备份一致.我这里犯了一点点小错误.有一些命名SBT.都不一样.

CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;

5.好奇一点,我这里是模拟,是否可以按照以前的方式catalog呢?

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored

RMAN> show all ;
RMAN configuration parameters for database with db_unique_name BOOK are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 3 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 '/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs/snapcf_book.f'; # default

RMAN> catalog backuppiece  '/u01/backup/5grs7g41_1_1';
ORA-19870: error while restoring backup piece /u01/backup/5grs7g41_1_1
ORA-19505: failed to identify file "/u01/backup/5grs7g41_1_1"
ORA-27048: skgfifi: file header information is invalid
Additional information: 8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of catalog command at 02/10/2017 10:27:57
RMAN-06209: List of failed objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    /u01/backup/5grs7g41_1_1

--//很明显文件头写入其他信息.对比看看:

RMAN> backup datafile 6 format '/u01/backup/6_%U';
Starting backup at 2017-02-10 10:29:00
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=56 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=68 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=80 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/mnt/ramdisk/book/tea01.dbf
channel ORA_DISK_1: starting piece 1 at 2017-02-10 10:29:01
channel ORA_DISK_1: finished piece 1 at 2017-02-10 10:29:02
piece handle=/u01/backup/6_5irs7hbd_1_1 tag=TAG20170210T102901 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 2017-02-10 10:29:02
Starting Control File and SPFILE Autobackup at 2017-02-10 10:29:02
piece handle=/u01/app/oracle/fast_recovery_area/BOOK/autobackup/2017_02_10/o1_mf_s_935576942_d9t9cg9m_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 2017-02-10 10:29:03

$ ls -l /u01/backup
total 31408
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 10:08:01 5grs7g41_1_1
-rw-r----- 1 oracle oinstall  6938624 2017-02-10 10:29:01 6_5irs7hbd_1_1
-rw-r--r-- 1 oracle oinstall 16777232 2017-02-10 10:08:02 c-1337401710-20170210-01
-rw-r--r-- 1 oracle oinstall     3360 2017-02-10 10:08:02 Oracle_Disk_SBT_Catalog

--//文件大小不一样.使用磁道是否有某些信息写入了Oracle_Disk_SBT_Catalog.这里估计记录类似磁带的信息(BTW:我仅仅是猜测).

CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;

RMAN> catalog start with '/u01/backup/';
searching for all files that match the pattern /u01/backup/
List of Files Unknown to the Database
=====================================
File Name: /u01/backup/Oracle_Disk_SBT_Catalog
File Name: /u01/backup/5grs7g41_1_1
File Name: /u01/backup/c-1337401710-20170210-01

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
no files cataloged

List of Files Which Where Not Cataloged
=======================================
File Name: /u01/backup/Oracle_Disk_SBT_Catalog
  RMAN-07517: Reason: The file header is corrupted
File Name: /u01/backup/5grs7g41_1_1
  RMAN-07517: Reason: The file header is corrupted
File Name: /u01/backup/c-1337401710-20170210-01
  RMAN-07517: Reason: The file header is corrupted

--//昏,如何能catalog呢?
--//google 找到如下链接:
https://dba010.wordpress.com/2012/08/31/how-to-catalog-backup-located-on-tape-in-rman/
http://msutic.blogspot.fr/2014/03/rman-catalog-backuppiece-located-on-tape.html
--//把百度扔到垃圾堆里去吧.这么简单的问题百度查询太失望了,打入如下:

RMAN> catalog device type 'SBT_TAPE' backuppiece '5grs7g41_1_1';

allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=56 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: WARNING: Oracle Test Disk API
cataloged backup piece
backup piece handle=5grs7g41_1_1 RECID=159 STAMP=935578092

RMAN> list backupset summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time     #Pieces #Copies Compressed Tag
------- -- -- - ----------- ------------------- ------- ------- ---------- ---
157     B  F  A DISK        2017-02-10 10:29:01 1       1       NO         TAG20170210T102901
158     B  F  A DISK        2017-02-10 10:29:02 1       1       NO         TAG20170210T102902
159     B  F  A SBT_TAPE    2017-02-10 10:08:01 1       1       NO         TAG20170210T100801

--//把这个文件移到到别的目录:
$ mv Oracle_Disk_SBT_Catalog ../backup_xxx/Oracle_Disk_SBT_Catalog

RMAN> catalog device type 'SBT_TAPE' backuppiece 'c-1337401710-20170210-01';
released channel: ORA_SBT_TAPE_1
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=56 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: WARNING: Oracle Test Disk API
cataloged backup piece
backup piece handle=c-1337401710-20170210-01 RECID=160 STAMP=935578351

[oracle@gxqyydg4 IP=100.78 /u01/backup 97]$ ls -l
total 31408
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 10:08:01 5grs7g41_1_1
-rw-r----- 1 oracle oinstall  6938624 2017-02-10 10:29:01 6_5irs7hbd_1_1
-rw-r--r-- 1 oracle oinstall 16777232 2017-02-10 10:08:02 c-1337401710-20170210-01
-rw-r--r-- 1 oracle oinstall     1120 2017-02-10 10:52:31 Oracle_Disk_SBT_Catalog
--//Oracle_Disk_SBT_Catalog的大小发生了变化.

RMAN> delete backupset 159,160 ;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=68 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=80 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=90 device type=DISK
using channel ORA_SBT_TAPE_1
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
161     159     1   1   AVAILABLE   SBT_TAPE    5grs7g41_1_1
160     160     1   1   AVAILABLE   SBT_TAPE    c-1337401710-20170210-01

Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=5grs7g41_1_1 RECID=161 STAMP=935578696
deleted backup piece
backup piece handle=c-1337401710-20170210-01 RECID=160 STAMP=935578351
Deleted 2 objects

6.收尾还原:
RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear;

old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/u01/backup)';
old RMAN configuration parameters are successfully deleted
released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
released channel: ORA_SBT_TAPE_1

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored

--最后补充一点:
1.我个人反对使用磁带,一般现在采用虚拟带库的方式,使用的是磁盘.
2.各个不同的厂家参数都不一样,而且测试也不见得比我目前使用NFS的方式快多少.
3.压缩问题,我在模拟磁带的环境测试,无法压缩的,许多开发公司使用自己压缩技术.

RMAN> backup as compressed backupset datafile 6 ;
Starting backup at 2017-02-10 11:15:29
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting compressed full datafile backup set
channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/mnt/ramdisk/book/tea01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 2017-02-10 11:15:29
channel ORA_SBT_TAPE_1: finished piece 1 at 2017-02-10 11:15:30
piece handle=5qrs7k2h_1_1 tag=TAG20170210T111529 comment=API Version 2.0,MMS Version 8.1.3.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:01
Finished backup at 2017-02-10 11:15:30
Starting Control File and SPFILE Autobackup at 2017-02-10 11:15:30
piece handle=c-1337401710-20170210-06 comment=API Version 2.0,MMS Version 8.1.3.0
Finished Control File and SPFILE Autobackup at 2017-02-10 11:15:31

$ ls -l 5qrs7k2h_1_1
-rw-r--r-- 1 oracle oinstall 8388624 2017-02-10 11:15:29 5qrs7k2h_1_1

$ ls -ltr | grep -v 'c-'
total 105264
-rw-r----- 1 oracle oinstall  6938624 2017-02-10 10:29:01 6_5irs7hbd_1_1
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 11:13:33 6_5krs7jut_1_1
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 11:14:07 6_5mrs7jvu_1_1
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 11:14:53 7_5ors7k1c_1_1
-rw-r--r-- 1 oracle oinstall  8388624 2017-02-10 11:15:29 5qrs7k2h_1_1
-rw-r--r-- 1 oracle oinstall    10080 2017-02-10 11:15:30 Oracle_Disk_SBT_Catalog
--//可以发现根本没有压缩.我也看了他们的测试,通过v$rman_backup_job_details视图看0级备份根本不压缩.

4.恢复问题,当你要恢复你必须安装它的client段,不然你无法恢复.rman是oracle自带,安装好能访问备份就ok了.
5.许可问题,这个问题其实最麻烦,有一些通过限制通道数量,比如你购买10个通道,这样你多个备份同时进行,但是数量不能超过这个限制.
6.实际上这些技术都是基于rman来实现的,实际上厂家的技术含量很低(我个人认为).没有必要,不要以为提供一个图形界面就是什么好东西.
  其实这样丧失了灵活性.
7.我以前用过一款知名品牌,竟然显示备份文件大小是0(估计是显示溢出了),我提交bug,对方给我的回复是bug,但是保证这个备份是能恢
  复的数据库的,并且允诺在下一个版本解决这个问题,这一等就是半年,在我看来太失望了.从那以后我就决定不再使用类似的技术.
8.作为一个搞技术,不要被那些商务人员给忽悠了,适合自己的技术才是最好的.不要给别人商务洗脑.

时间: 2024-10-14 14:40:31

[20170208]rman tape.txt的相关文章

[20161230]rman checksyntax2.txt

[20161230]rman checksyntax2.txt --曾经写过一篇rman checksyntax的问题,这个问题存在10g: http://blog.itpub.net/267265/viewspace-2130511/ --今天看了一个链接重复测试:https://jhdba.wordpress.com/2016/12/29/rman-checksyntax-function/#comment-11009 1.环境: SYS@book> @ &r/ver1 PORT_STR

[20161214]rman checksyntax.txt

[20161214]rman checksyntax.txt --rman在命令行使用参数checksyntax可以检查命令语法是否正确,而且并不会真正执行.但是昨天在恢复一个10g的数据库时遇到问题,做 --一个记录: 1.环境: --要恢复的数据库版本: > @ &r/ver1 PORT_STRING                    VERSION        BANNER ------------------------------ -------------- -------

[20171122]rman filesystemio_options.txt

[20171122]rman备份与参数filesystemio_options设置.txt --//这几天写了几篇filesystemio_options参数设置的文章,单独测试这个参数对rman备份以及os缓存的影响. 1.测试环境: SYS@book> @ &r/ver1 PORT_STRING                    VERSION        BANNER ------------------------------ -------------- ----------

[20171130]关于rman的一些总结.txt

[20171130]关于rman的一些总结.txt --//最近一直做rman相关测试,测试那个乱,没办法.无法从周围的人获得帮助,纯粹是自己的乱猜,乱测,不知道别人是否能看懂我写的东西. --//有必要做一些总结,不一定对,仅仅是我当前的看法. 1.数据文件备份集中,文件头是最后写到备份集文件的. 2.使用备份集恢复也是一样,文件头也是最好写入的. 3.以上情况对as copy的方式也是一样. --//oracle这样操作主要目的保证备份是好的可用,反之恢复也是一样. 4.关于备份参数file

[20171128]rman Input or output Memory Buffers.txt

[20171128]rman Input or output Memory Buffers.txt --//Input Memory Buffers如何测试,不清楚.不过找到一本电子书.摘要如下: Oracle RMAN 11g Backup and Recovery.pdf 作者:Robert G. Freeman Matthew Hart 页数:689 出版社:Mc graw hill 出版号: ISBN: 978-0-07-162861-7         MHID: 0-07-16286

[20171129]rman input memory buffer 5.txt

[20171129]rman input memory buffer 5.txt --//Input Memory Buffers如何测试,不清楚.不过找到一本电子书.摘要如下: Oracle RMAN 11g Backup and Recovery.pdf 作者:Robert G. Freeman Matthew Hart 页数:689 出版社:Mc graw hill 出版号: ISBN: 978-0-07-162861-7         MHID: 0-07-162861-4 RMAN

[20171130]关于rman备份疑问.txt

[20171130]关于rman备份疑问.txt --//前面测试太乱,重新做一些rman as copy相关测试. 1.环境: SCOTT@book> @ &r/ver1 PORT_STRING                    VERSION        BANNER ------------------------------ -------------- --------------------------------------------------------------

[20161101]rman备份与数据文件变化7.txt

[20161101]rman备份与数据文件变化7.txt --//想象一下,如果备份文件时间很长,而这个时候数据文件大小发生了变化,oracle的备份如何解决这个问题呢? --//去年已经测试了建立备份集的情况,一直想做一次image copy的测试,一直脱,主要原因自己不想做这个测试.... --//而且当时的测试很乱,自己主要一边做一边想.... --//链接: http://blog.itpub.net/267265/viewspace-2127386/ http://blog.itpub

[20171121]rman使用copy image恢复.txt

[20171121]rman使用copy image恢复.txt --//上个星期做数据文件块头恢复时,提到使用rman备份数据文件时,文件头数据库信息是最后写入备份集文件的,在filesperset=1的情况 --//下写入备份集文件中的倒数第2块就是文件头的备份.参考链接: http://blog.itpub.net/267265/viewspace-2147297/=>[20171115]恢复数据文件块头4补充.txt --//而且我最后还做了测试证明如果resotre数据文件,实际上文件