RAC环境的恢复策略
上一篇 / 下一篇 2007-06-26 00:00:00 / 个人分类:ORACLE
对于RAC环境,不同的备份策略会导致备份文件的分步不同,如果频繁修改备份策略,或者备份策略混乱的话,会给恢复过程带来很大的困难。
8hiD#q1O0
对于RAC环境中的多种备份策略,前面已经通过10篇文章详细描述了,这里想要强调的是,备份策略的不同,会导致备份结果的分步不同,进而影响恢复的策略和步骤。
一般情况下,恢复策略和备份策略必须是对应的。如果备份策略进行了修改,那么恢复也应该采用相同的策略。
这样描述太过于抽象,举个例子,比如备份的时候用RMAN配置两个CHANNEL,每个CHANNEL都通过CONNECT语句指向一个实例,在备份的时候,两个CHANNEL同时运行,每个实例会将本CHANNEL读取的数据文件写到这个实例所在服务器所挂接的磁带上。
而在恢复过程中,每个节点都只能挂接自己备份的磁带,而无法恢复别的节点备份的磁带。也就是说,恢复也必须启动两个CHANNEL,每个连接到一个实例上,同时进行恢复。
为了避免出现问题,建议在变更备份策略后,马上对整个数据库进行一次备份。另外在恢复之前,可以考虑利用VALIDATE来验证恢复是否是可行的,下面这个例子就说明备份机制和恢复机制不同的话,会造成的问题:
bash-2.03$ export NLS_LANG=americanITPUB个人空间o~r tW
bash-2.03$ export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS' ITPUB个人空间U.g"C6fP9mPE W
bash-2.03$ rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Tue Jun 26 13:11:42 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TESTRAC (DBID=4291216984, not open)
RMAN> run ITPUB个人空间|0J:jMu2K#@?
2> {ITPUB个人空间Ydh.MF]DY
3> set until time '2007-6-21 0:0:0';
?#U'RxLxV04> restore database;ITPUB个人空间m4d)_'G:B6??1YHGVW
5> recover database;ITPUB个人空间{a
f#l)P x'y_+q2I
6> }
executing command: SET until clause
P{#K#e)P0using target database control file instead of recovery catalog
Starting restore at 2007-06-26 13:14:31
9T:Pn\:j;Y#Dfzq)O0configuration for SBT_TAPE channel 2 is ignoredITPUB个人空间pl9tb:O?7U
allocated channel: ORA_SBT_TAPE_1
F+h2`/VrQ9_
SO6D0?A0channel ORA_SBT_TAPE_1: sid=313 instance=testrac2 devtype=SBT_TAPEITPUB个人空间,g+pIj4Xm
@;D
channel ORA_SBT_TAPE_1: VERITAS NetBackup for Oracle - Release 6.0 (2006110304)ITPUB个人空间4D+IOQ6r6gD4rs M
allocated channel: ORA_DISK_1
Y D;nu&M_'k m;F)Z0channel ORA_DISK_1: sid=305 instance=testrac2 devtype=DISK
_e-E7ABZl0allocated channel: ORA_DISK_2
Y
Ea)QH FYn;XJo0channel ORA_DISK_2: sid=304 instance=testrac2 devtype=DISK
channel ORA_SBT_TAPE_1: starting datafile backupset restoreITPUB个人空间;]D!\yB
x1r#[r
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup setITPUB个人空间jKM_4G5GLm
restoring datafile 00005 to +DISK/testrac/datafile/users.267.618591279ITPUB个人空间Ue6Ql6u%A
restoring datafile 00006 to +DISK/testrac/datafile/zhejiang01.dbf
%a`e@p5uC
T0restoring datafile 00008 to +DISK/testrac/datafile/ndmain01.dbfITPUB个人空间3lIpV`5SS*b.wt2H/s
restoring datafile 00009 to +DISK/testrac/datafile/zhejiang03.dbfITPUB个人空间.Bpe6S:o'h#D.P-@r
restoring datafile 00010 to +DISK/testrac/datafile/ndindex01.dbf
"s'~3j%N
@ fj0restoring datafile 00012 to +DISK/testrac/datafile/zhejiang05.dbfITPUB个人空间X)Ma8D ?j
channel ORA_SBT_TAPE_1: reading from backup piece krikm8an_1_1
B~Y_;Cu#UX0ORA-19870: error reading backup piece krikm8an_1_1ITPUB个人空间 s] u7P!hR
ORA-19507: failed to retrieve sequential file, handle="krikm8an_1_1", parms=""
b D+i*Q3Kk0ORA-27029: skgfrtrv: sbtrestore returned error
edRm
T)AK5ZO%?7w0ORA-19511: Error received from media manager layer, error text:ITPUB个人空间:I%M(ZW \2Q!s0ZI6a
Backup file <krikm8an_1_1> not found in NetBackup catalogITPUB个人空间;G
P/gy`_!V
channel ORA_SBT_TAPE_1: starting datafile backupset restoreITPUB个人空间
d(xJkZ&SQ'E6F
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
*S|#qlV'~4ZrN"f0restoring datafile 00001 to +DISK/testrac/datafile/system.262.618591167
E1J-ErK*I&r0{0restoring datafile 00002 to +DISK/testrac/datafile/undotbs1.263.618591197
)yG"m3zzK1Pu0channel ORA_SBT_TAPE_1: reading from backup piece kvikmgua_1_1