RMAN備份與恢複之基於時間點的不完全恢複

來源:互聯網
上載者:User

一 不完全恢複講解

在上一篇文章(RMAN備份與恢複之UNDO資料表空間丟失  )中,我們講到UNDO資料表空間丟失怎麼處理。UNDO資料表空間是不可離線的,同樣,SYSTEM資料表空間也是不可離線的,所以SYSTEM資料表空間丟失的處理辦法和UNDO資料表空間丟失的處理辦法類似,在此不贅述。

RMAN恢複分為完全恢複和不完全恢複。完全恢複,顧名思義,就是基於全備的基礎上對資料進行恢複。但是真實環境中這樣的恢複用得很少。相反,不完全恢複使用較多。不完全恢複,也就是通過備份檔案,恢複某一個誤操作或者是某一段時間丟失的資料。不完全恢複可以基於時間,基於SCN,基於記錄序號、基於備份控制檔案。本文講解基於時間點的不完全恢複。

二 基於時間點的不完全恢複講解

與前面的文章一樣,既然要做恢複,我們首先要有備份檔案,我們使用RMAN工具對資料庫進行備份。備份完全後,我們切換到SQL Plus中,開啟顯示完整時間的選項,為什麼要顯示完整時間呢?因為基於時間點的恢複需要一個時間點,開啟這個選項後,一是可以使我們更方便的查看到操作過程中經曆的時間,二是保證時間點選取的精確性。然後我們登入到SCOTT使用者,建立一張測試表,插入資料,手動提交。注意,我們為了保證資料的一致性,最好切換到SYS使用者下手動切換日誌(ALTER SYSTEM SWITCH LOGFILE)和手動觸發CKPT(ALTERSYSTEM CHECKPOINT)。好了,資料準備完成,我們此時刪除表,並同時清空資源回收筒,記下刪除表之前的時間點,後面恢複操作要使用到。現在我們強制關閉資料庫,登入到RMAN中,啟動資料庫到MOUNT狀態,然後查看當前的INCARNATION號,至於INCARNATION號是什麼東西。我們可以這樣理解,每一次RESETLOGS就會使INCARNATION+1,如果想要恢複到之前INCARNATION的scn(或者時間點),就需要先跳轉到之前的INCARNATION。跳轉到之前的INCARNATION,我們可以使用如下命令:RESET DATABASE TO INCARNATION <INCARNATION號>。舉一個不太恰當的比喻,這個INCARNATION就像我們在十字路口,此時我們不知道應該往哪個方向走,如果你一旦走錯,還得回到這個十字路口選取下一條路。此時我們需要編輯恢複指令碼,內容就是告訴Oracle恢複到哪個時間點,並且還原和恢複資料庫。恢複完成後,我們需要使用RESETLOGS方式開啟資料庫,此時我們登入到SQL Plus中,查看錶只中的資料,如果能夠成功查詢到,證明恢複成功。如果不能查詢到,第一考慮時間點是否選擇正確,第二確認INCARNATION號是否正確,第三資料是否保持了一致性。因為我們重設了日誌,所以需要重新備份資料庫。至此,完整的恢複操作完成。

三 基於時間點的恢複類比

Step 1,SQL Plus中確保資料庫在歸檔模式,RMAN中備份資料庫

SQL> ARCHIVE LOG LIST;
Database log mode        Archive Mode
Automatic archival        Enabled
Archive destination        USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence    68
Next log sequence to archive  70
Current log sequence        70
[oracle@orcl ~]$ uniread rman target /
[uniread] Loaded history (2 lines)

Recovery Manager: Release 11.2.0.3.0 - Production on Fri Jan 17 09:44:40 2014

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

connected to target database: LARRRDB (DBID=3428598070)

RMAN> BACKUP DATABASE;

Starting backup at 17-JAN-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=36 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=00001 name=/u01/oracle/oradata/larrrdb/system01.dbf
input datafile file number=00003 name=/u01/oracle/oradata/larrrdb/undotbs01.dbf
input datafile file number=00002 name=/u01/oracle/oradata/larrrdb/sysaux01.dbf
input datafile file number=00004 name=/u01/oracle/oradata/larrrdb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 17-JAN-14
channel ORA_DISK_1: finished piece 1 at 17-JAN-14
piece handle=/u01/oracle/fast_recovery_area/LARRRDB/backupset/2014_01_17/o1_mf_nnndf_TAG20140117T094447_9fk2rhv7_.bkp tag=TAG20140117T094447 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:04:07
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 17-JAN-14
channel ORA_DISK_1: finished piece 1 at 17-JAN-14
piece handle=/u01/oracle/fast_recovery_area/LARRRDB/backupset/2014_01_17/o1_mf_ncsnf_TAG20140117T094447_9fk309p8_.bkp tag=TAG20140117T094447 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 17-JAN-14

 

Step 2,SQL Plus中開啟顯示完整時間

SQL> CONN SCOTT/tiger;
Connected.
SQL> SET TIME ON;
09:53:34 SQL>

 

Step 3,SQL Plus建立測試表

09:53:34 SQL> CREATE TABLE test(id NUMBER(2),name VARCHAR(20));

Table created.

09:53:59 SQL>

 

Step 4,SQL Plus插入資料,並提交,為了保持資料一致性,最好使用sys使用者手動切換日誌(ALTER SYSTEM SWITCHLOGFILE)和觸發CKPT(ALTERSYSTEM CHECKPOINT)

09:53:59 SQL> INSERT INTO test VALUES(1,'justdb');

1 row created.

09:54:16 SQL> COMMIT;

Commit complete.

09:54:25 SQL> SELECT * FROM test;

  ID NAME
---------- --------------------
  1 justdb

09:54:33 SQL>

 

Step 5,SQL Plus中刪除測試表

09:54:33 SQL> DROP TABLE test PURGE;

Table dropped.

 

Step 6,SQL Plus中一致性關閉資料庫

10:00:09 SQL> SHUTDOWN IMMEDIATE;
Database closed.
Database dismounted.
ORACLE instance shut down.
10:01:57 SQL>

 

Step 7,編輯基於時間點恢複的指令碼,注意時間點的選取,此處選取為刪除表的時間點(09:54:33),注意時間點尤其重要

[oracle@orcl ~]$ vim /home/oracle/recover_data_by_time.sql
[oracle@orcl ~]$ cat !$
cat /home/oracle/recover_data_by_time.sql
RUN {
  SET UNTIL TIME "to_date('2014-01-17 09:54:33','yyyy-mm-dd hh24:mi:ss')";
  RESTORE DATABASE;
  RECOVER DATABASE;
}

 

Step 8,登入到RMAN,啟動資料庫到MOUNT狀態

[oracle@orcl ~]$ uniread rman target /
[uniread] Loaded history (6 lines)

Recovery Manager: Release 11.2.0.3.0 - Production on Fri Jan 17 10:02:22 2014

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

connected to target database (not started)

RMAN> STARTUP MOUNT;

Oracle instance started
database mounted

Total System Global Area    839282688 bytes

Fixed Size                    2233000 bytes
Variable Size                494931288 bytes
Database Buffers            339738624 bytes
Redo Buffers                  2379776 bytes

 

Step 9,RMAN中查看當前INCARNATION號,注意:如果有其他的操作,以後恢複時應該選取當前查看到的INCARNATION號,使用RESET DATABASE TO INCARNATION <INCARNATION號>命令

RMAN> LIST INCARNATION;

using target database control file instead of recovery catalog

List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1      1      LARRRDB  3428598070      CURRENT 1          23-NOV-13

Step 10,RMAN中執行基於時間點的恢複指令碼

RMAN> @ /home/oracle/recover_data_by_time.sql
@ /home/oracle/recover_data_by_time.sql

RMAN> RUN {
2>  SET UNTIL TIME "to_date('2014-01-17 09:54:33','yyyy-mm-dd hh24:mi:ss')";
3>  RESTORE DATABASE;
4>  RECOVER DATABASE;
5> }
executing command: SET until clause

Starting restore at 17-JAN-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/oracle/oradata/larrrdb/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/oracle/oradata/larrrdb/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/oracle/oradata/larrrdb/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/oracle/oradata/larrrdb/users01.dbf
channel ORA_DISK_1: reading from backup piece /u01/oracle/fast_recovery_area/LARRRDB/backupset/2014_01_17/o1_mf_nnndf_TAG20140117T094447_9fk2rhv7_.bkp
channel ORA_DISK_1: piece handle=/u01/oracle/fast_recovery_area/LARRRDB/backupset/2014_01_17/o1_mf_nnndf_TAG20140117T094447_9fk2rhv7_.bkp tag=TAG20140117T094447
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:04:16
Finished restore at 17-JAN-14

Starting recover at 17-JAN-14
using channel ORA_DISK_1

starting media recovery
media recovery complete, elapsed time: 00:00:01

Finished recover at 17-JAN-14

RMAN> **end-of-file**


Step 11,RMAN中使用RESETLOGS開啟資料庫

RMAN> ALTER DATABASE OPEN RESETLOGS;

database opened

 

Step 12,SQL Plus中查看資料,如果能夠正確地查看到,證明恢複成功

[oracle@orcl ~]$ sqlplus
[uniread] Loaded history (66 lines)

SQL*Plus: Release 11.2.0.3.0 Production on Fri Jan 17 10:10:53 2014

Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options

SQL> SELECT open_mode FROM v$database;

OPEN_MODE
--------------------
READ WRITE

#這正是被刪除掉的表中的資料
SQL> SELECT * FROM scott.test;

  ID NAME
---------- --------------------
  1 justdb

 

Step 13,因為重設了日誌,我們需要重新在RMAN中備份

[oracle@orcl ~]$ uniread rman target /
[uniread] Loaded history (2 lines)

Recovery Manager: Release 11.2.0.3.0 - Production on Fri Jan 17 09:44:40 2014

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

connected to target database: LARRRDB (DBID=3428598070)

RMAN> BACKUP DATABASE;

推薦閱讀:

RMAN 配置歸檔日誌刪除策略

Oracle基礎教程之通過RMAN複製資料庫

RMAN備份策略制定參考內容

RMAN備份學習筆記

OracleDatabase Backup加密 RMAN加密

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.