Oracle rman 备份日志单独备份和交叉校验
手动备份归档日志 1、database01 [oraprod@db01 scripts ]$ pwd/usr/tivoli/scripts[oraprod@db01 scripts ]$ ls1.txt
手动备份归档日志
1、database01
[oraprod@db01 scripts ]$ pwd
/usr/tivoli/scripts
[oraprod@db01 scripts ]$ ls
1.txt nohup.out oraicr0.sh scheoraicr0.sh
BKlog null oraicr1.sh scheoraicr0.sh.test
BKlog.tar oraarch.sh oraicr1.sh.orig scheoraicr1.sh
DBArchivelogBK.sh oraarch.sh.BK091206 oraicr1v.sh scheoraicr1.sh.test
DBArchivelogBK1130.sh oraarch.sh.yt oraicr2.sh scheoraicr1v.sh
DBFileBK_full.sh oraarch2.sh recover.sh scheoraicr2.sh
backup20130428.log oraarchyzz.sh refull.sh scheoraicr2.sh.test
nihao.c orafull.sh schearch.sh tdpora.tar
nihao.sh orafull.sh.20120912combak schearch.sh.bak test.sh
nihao02.sh orafull.sh.BK091206 scheorafull.sh
[oraprod@db01 scripts ]$ rman target / catalog rman/rman@rman log = backup2013_05_01.log
RMAN>@oraarchyzz.sh
database 02
[oraprod@db02 archivelog ]$ pwd
/u01/archivelog
[oraprod@db02 archivelog ]$ cat backuparc.sql
run {
####backup archivelog####
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/Oracle/bin64/tdpo.opt)'
connect backup/bk1949coal@PROD1;
allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'
connect backup/bk1949coal@PROD2;
backup filesperset 10
(archivelog all skip inaccessible delete input format '/arch_%s_%p/');
release channel t1;
release channel t2;
}
[oraprod@db02 archivelog ]$ rman target / catalog rman/rman@rman log = backup20130501.log
PS:手动备份归档日志,,每次都是从最近的归档日志开始备份,接在备份以前的,以前较早漏掉备份的可能每次执行都不会被备份。这样的话可能就要执行交叉检查命令来确认系统有多少备份日志成功备份,
crosscheck archivelog all;
crosscheck backupset;
进入rman:
list backup of archivelog all;
list backup of archivelog sequence 6474;
RMAN> list backup of archivelog from sequence 100425627276 thread 2;
RMAN>list backup of archivelog all; ------------列出所有归档日志
RMAN>list backup of archivelog from sequence 8116 thread 2; ------------列出某条归档日志
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
1728048 11.14G SBT_TAPE 00:16:16 06-SEP-13
BP Key: 1728052 Status: AVAILABLE Compressed: NO Tag: TAG20130906T091351
Handle: /arch_40509_1/ Media: 103
List of Archived Logs in backup set 1728048
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
2 7774 100425627276 06-SEP-13 100431144864 06-SEP-13
RMAN>
应该是归档日志备份后被删除了吧,没做交叉检验?
crosscheck archivelog all;
delete archivelog all completed before 'sysdate-7';
推荐阅读:
RMAN 配置归档日志删除策略
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
