RMAN備份歸檔日誌多份 %c
專案要求,歸檔日誌需要備份兩份。RMAN中可以直接設定進行修改。不過在備份的時候遇到了錯誤,加了%c後備份成功,記錄一下。
■ %c Copy number for multiple copies in a duplexed backup
RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
RMAN> backup archivelog all format '/home/oracle/backup/%t_%d_%u.arc';
Starting backup at 18-NOV-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=9 recid=5 stamp=831479128
input archive log thread=1 sequence=10 recid=6 stamp=831548007
input archive log thread=1 sequence=11 recid=7 stamp=831806585
input archive log thread=1 sequence=12 recid=8 stamp=831823051
input archive log thread=1 sequence=13 recid=9 stamp=831823120
channel ORA_DISK_1: starting piece 1 at 18-NOV-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/18/2013 13:58:41
RMAN-20039: format requires %c when duplexing
RMAN> backup archivelog all format '/home/oracle/backup/%t_%d_%u_%c.arc';
Starting backup at 18-NOV-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=9 recid=5 stamp=831479128
input archive log thread=1 sequence=10 recid=6 stamp=831548007
input archive log thread=1 sequence=11 recid=7 stamp=831806585
input archive log thread=1 sequence=12 recid=8 stamp=831823051
input archive log thread=1 sequence=13 recid=9 stamp=831823120
input archive log thread=1 sequence=14 recid=10 stamp=831823172
channel ORA_DISK_1: starting piece 1 at 18-NOV-13
channel ORA_DISK_1: finished piece 1 at 18-NOV-13 with 2 copies and tag TAG20131118T135932
piece handle=/home/oracle/backup/831823172_PROD_0rop97a4_1.arc comment=NONE
piece handle=/home/oracle/backup/831823172_PROD_0rop97a4_2.arc comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 18-NOV-13
Starting Control File and SPFILE Autobackup at 18-NOV-13
piece handle=/home/oracle/backup/control/c-243217534-20131118-0f comment=NONE
Finished Control File and SPFILE Autobackup at 18-NOV-13
■ %c Copy number for multiple copies in a duplexed backup
RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
RMAN> backup archivelog all format '/home/oracle/backup/%t_%d_%u.arc';
Starting backup at 18-NOV-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=9 recid=5 stamp=831479128
input archive log thread=1 sequence=10 recid=6 stamp=831548007
input archive log thread=1 sequence=11 recid=7 stamp=831806585
input archive log thread=1 sequence=12 recid=8 stamp=831823051
input archive log thread=1 sequence=13 recid=9 stamp=831823120
channel ORA_DISK_1: starting piece 1 at 18-NOV-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/18/2013 13:58:41
RMAN-20039: format requires %c when duplexing
RMAN> backup archivelog all format '/home/oracle/backup/%t_%d_%u_%c.arc';
Starting backup at 18-NOV-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=9 recid=5 stamp=831479128
input archive log thread=1 sequence=10 recid=6 stamp=831548007
input archive log thread=1 sequence=11 recid=7 stamp=831806585
input archive log thread=1 sequence=12 recid=8 stamp=831823051
input archive log thread=1 sequence=13 recid=9 stamp=831823120
input archive log thread=1 sequence=14 recid=10 stamp=831823172
channel ORA_DISK_1: starting piece 1 at 18-NOV-13
channel ORA_DISK_1: finished piece 1 at 18-NOV-13 with 2 copies and tag TAG20131118T135932
piece handle=/home/oracle/backup/831823172_PROD_0rop97a4_1.arc comment=NONE
piece handle=/home/oracle/backup/831823172_PROD_0rop97a4_2.arc comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 18-NOV-13
Starting Control File and SPFILE Autobackup at 18-NOV-13
piece handle=/home/oracle/backup/control/c-243217534-20131118-0f comment=NONE
Finished Control File and SPFILE Autobackup at 18-NOV-13
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26084062/viewspace-1061785/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle設定多個歸檔路徑生成多份歸檔日誌,Rman備份時也只備份其中的一份歸檔日誌Oracle
- RMAN備份整庫和歸檔日誌的方法
- oracle rman備份歸檔日誌需要先切換日誌嗎Oracle
- 手工rm刪除歸檔日誌對備份歸檔日誌的影響
- rman開啟備份優化對備份歸檔的影響優化
- Oracle使用備份檔案集恢復歸檔日誌Oracle
- 12C多租戶rman備份文件
- dg丟失歸檔,使用rman增量備份恢復
- RMAN-ERROR:因為找不到過期和丟失的歸檔日誌而備份失敗Error
- 【RMAN】同時建立多個備份(建立多重備份)
- 如何快速找到備份過最近、最大序號的歸檔日誌
- ORACLE NBU調取oracle rman指令碼備份歸檔不自動刪除歸檔Oracle指令碼
- rman 還原歸檔日誌(restore archivelogRESTHive
- oracle 12c rman備份pdbOracle
- 【RMAN】RMAN備份至ASMASM
- RMAN備份概述
- 【備份】RMAN中對控制檔案的幾種備份方法
- oracle 如何不備份已經備份的歸檔Oracle
- 【RMAN】RMAN的備份保留策略
- RMAN備份恢復典型案例——RMAN備份&系統變慢
- 使用RMAN增量備份處理Dataguard因歸檔丟失造成的gap
- RMAN備份進度
- rman 備份指令碼指令碼
- RMAN的備份原理
- [20221121]rman刪除歸檔日誌問題.txt
- 12 使用RMAN備份和恢復檔案
- rman 增量備份恢復
- Oracle RMAN備份實戰Oracle
- Oracle OCP(60):RMAN 備份Oracle
- RMAN備份恢復技巧
- 【rman備份策略】實驗
- 【RMAN】Oracle中如何備份控制檔案?備份控制檔案的方式有哪幾種?Oracle
- [重慶思莊每日技術分享]-備庫使用RMAN獲得歸檔日誌
- mysqldump全量備份+mysqlbinlog二進位制日誌增量備份MySql
- 【RMAN】在多租戶環境下的RMAN備份及恢復
- 【RMAN】Oracle12c以後rman 備份恢復命令參考Oracle
- MySQL 日誌管理、備份與恢復MySql
- MySQL日誌管理,備份和恢復MySql
- RMAN刪除歸檔日誌出現RMAN-0813錯誤的處理