免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 14442 | 回复: 8
打印 上一主题 下一主题

[备份软件] 使用rman nocatalog方式备份Oracle - NetBackup配置方法 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-05-24 14:15 |只看该作者 |倒序浏览
最近有人要,就顺便把以前写的E文版的翻了改了一下,贴出来与大家共享。发现错误请订正。


NetBackup通过RMAN nocatalog方式备份设置步骤

当通过rman nocatalog方式备份Oracle,Oracle使用controlfile存放备份信息。因此,当使用rman nocatalog方式备份时,备份controlfile是非常重要的。

有一个问题,当使用rman nocatalog恢复时,数据库必须是处于“mount”状态的。而Oracle startup mount的前提条件是control必须存在。因此,你必须在恢复datafile之前先恢复controlfile。使用rman catalog方式时,可以startup nomount然后restore control file;但使用rman nocatalog时,必须先用文件方式恢复controlfile。

下面对比一下rman nocatalog和rman catalog的恢复时的步骤,以便建立正确的备份策略(以下的恢复都是在online状态下的备份):

rman nocatalog恢复:
1)        建立oracle运行环境(包括init或sp文件)
2)        文件方式恢复controlfile到init文件指定的位置
3)        startup mount
4)        rman,恢复datafile
5)        alter database open resetlogs

rman catalog恢复:
1)        建立oracle运行环境(包括init或sp文件)
2)        rman ,restore controfile
3)        alter database mount
4)        rman, restore datafile
5)        alter database open resetlogs

可以看出,rman nocatalog备份时,必须用文件方式备份controlfile。

另外,由于nocatalog时利用controlfile存放备份信息,建议将Oracle参数文件中的CONTROL_FILE_RECORD_KEEP_TIME值加大(缺省为7天), 该参数在$ORACLE_HOME/dbs/initSID.ora中(9i后也可能在spfile中,只能通过Oracle语句更改)。  

以下描述如何使用NetBackup对Oracle进行rman nocatalog方式下的备份:

一、备份服务器上的工作

1. 建立NetBackup policy,用于备份control file
建立policy “oracle_control_file”, backup type “standard”, client “oracle_server”, filelist “/scripts/control.ora”, schedule “user” type “user backup”, 选择所有时间范围。

2. 建立NetBackup policy,用于备份 Oracle database
建立policy “oracle_full”, backup type “oracle”, client “oracle_server”, script “/scripts/hot_database_level0.sh”,schedule自己定。

3. 如果需要,建立NetBackup policy用于备份archivelog,方法同上,脚本另写。

二、Oracle服务器上的工作
1. 在 “oracle_server”上,编辑“/scripts/hot_database_level0.sh”文件,加入下行,在rman指令结束符“}”前:
ALLOCATE CHANNEL ch00 TYPE disk;
COPY CURRENT CONTROLFILE to '/scripts/control.ora';
RELEASE CHANNEL ch00;

2. 在 “/scripts/hot_database_level0.sh”相关行(快结束的地方),加入:
/usr/openv/netbackup/bin/bpbackup -p oracle_control_file -s user –t 0 /scripts/control.ora

3. 如果另外有archivelog的备份,重复以上1、2步骤,加在archivelog备份的脚本中。

4. 改变oracle参数(可选,Oracle9i使用spfile的话通过oracle指令修改)
(1) shutdown oracle
(2) 编辑 $ORACLE_HOME/dbs/initSID.ora, 设置
CONTROL_FILE_RECORD_KEEP_TIME=365
(3) startup oracle


scripts举例:

#!/bin/sh
# $Header: hot_database_backup.sh,v 1.9 2002/02/06 16:48:56 lstrub Stab $
#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2002 VERITAS Software Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
#
# ---------------------------------------------------------------------------
#                          hot_database_backup.sh
# ---------------------------------------------------------------------------
#  This script uses Recovery Manager to take a hot (inconsistent) database
#  backup. A hot backup is inconsistent because portions of the database are
#  being modified and written to the disk while the backup is progressing.
#  You must run your database in ARCHIVELOG mode to make hot backups. It is
#  assumed that this script will be executed by user root. In order for RMAN
#  to work properly we switch user (su -) to the oracle dba account before
#  execution. If this script runs under a user account that has Oracle dba
#  privilege, it will be executed using this user's account.
# ---------------------------------------------------------------------------

# ---------------------------------------------------------------------------
# Determine the user which is executing this script.
# ---------------------------------------------------------------------------

CUSER=`id |cut -d"(" -f2 | cut -d "" -f1`

# ---------------------------------------------------------------------------
# Put output in <this file name>;.out. Change as desired.
# Note: output directory requires write permission.
# ---------------------------------------------------------------------------

RMAN_LOG_FILE=${0}.out

# ---------------------------------------------------------------------------
# You may want to delete the output file so that backup information does
# not accumulate.  If not, delete the following lines.
# ---------------------------------------------------------------------------

if [ -f "$RMAN_LOG_FILE" ]
then
        rm -f "$RMAN_LOG_FILE"
fi

# -----------------------------------------------------------------
# Initialize the log file.
# -----------------------------------------------------------------

echo >;>; $RMAN_LOG_FILE
chmod 666 $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Log the start of this script.
# ---------------------------------------------------------------------------

echo Script $0 >;>; $RMAN_LOG_FILE
echo ==== started on `date` ==== >;>; $RMAN_LOG_FILE
echo >;>; $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Replace /db/oracle/product/ora81, below, with the Oracle home path.
# ---------------------------------------------------------------------------

ORACLE_HOME=/oracle/app/oracle/product/8.1.7
export ORACLE_HOME

# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle SID of the target database.
# ---------------------------------------------------------------------------

ORACLE_SID=ora81
export ORACLE_SID

# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle DBA user id (account).
# ---------------------------------------------------------------------------

ORACLE_USER=oracle

# ---------------------------------------------------------------------------
# Set the target connect string.
# Replace "sys/manager", below, with the target connect string.
# ---------------------------------------------------------------------------

TARGET_CONNECT_STR=/

# ---------------------------------------------------------------------------
# Set the Oracle Recovery Manager name.
# ---------------------------------------------------------------------------

RMAN=$ORACLE_HOME/bin/rman

# ---------------------------------------------------------------------------
# Print out the value of the variables set by this script.
# ---------------------------------------------------------------------------

echo >;>; $RMAN_LOG_FILE
echo   "RMAN: $RMAN" >;>; $RMAN_LOG_FILE
echo   "ORACLE_SID: $ORACLE_SID" >;>; $RMAN_LOG_FILE
echo   "ORACLE_USER: $ORACLE_USER" >;>; $RMAN_LOG_FILE
echo   "ORACLE_HOME: $ORACLE_HOME" >;>; $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Print out the value of the variables set by bphdb.
# ---------------------------------------------------------------------------

echo  >;>; $RMAN_LOG_FILE
echo   "NB_ORA_FULL: $NB_ORA_FULL" >;>; $RMAN_LOG_FILE
echo   "NB_ORA_INCR: $NB_ORA_INCR" >;>; $RMAN_LOG_FILE
echo   "NB_ORA_CINC: $NB_ORA_CINC" >;>; $RMAN_LOG_FILE
echo   "NB_ORA_SERV: $NB_ORA_SERV" >;>; $RMAN_LOG_FILE
echo   "NB_ORA_POLICY: $NB_ORA_POLICY" >;>; $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# NOTE: This script assumes that the database is properly opened. If desired,
# this would be the place to verify that.
# ---------------------------------------------------------------------------

echo >;>; $RMAN_LOG_FILE
# ---------------------------------------------------------------------------
# If this script is executed from a NetBackup schedule, NetBackup
# sets an NB_ORA environment variable based on the schedule type.
# The NB_ORA variable is then used to dynamically set BACKUP_TYPE
# For example, when:
#     schedule type is                BACKUP_TYPE is
#     ----------------                --------------
# Automatic Full                     INCREMENTAL LEVEL=0
# Automatic Differential Incremental INCREMENTAL LEVEL=1
# Automatic Cumulative Incremental   INCREMENTAL LEVEL=1 CUMULATIVE
#
# For user initiated backups, BACKUP_TYPE defaults to incremental
# level 0 (full).  To change the default for a user initiated
# backup to incremental or incremental cumulative, uncomment
# one of the following two lines.
# BACKUP_TYPE="INCREMENTAL LEVEL=1"
# BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
#
# Note that we use incremental level 0 to specify full backups.
# That is because, although they are identical in content, only
# the incremental level 0 backup can have incremental backups of
# level >; 0 applied to it.
# ---------------------------------------------------------------------------

if [ "$NB_ORA_FULL" = "1" ]
then
        echo "Full backup requested" >;>; $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=0"

elif [ "$NB_ORA_INCR" = "1" ]
then
        echo "Differential incremental backup requested" >;>; $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=1"

elif [ "$NB_ORA_CINC" = "1" ]
then
        echo "Cumulative incremental backup requested" >;>; $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

elif [ "$BACKUP_TYPE" = "" ]
then
        echo "Default - Full backup requested" >;>; $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=0"
fi


# ---------------------------------------------------------------------------
# Call Recovery Manager to initiate the backup. This example does not use a
# Recovery Catalog. If you choose to use one, replace the option 'nocatalog'
# from the rman command line below with the
# 'rcvcat <userid>;/<passwd>;@<tns alias>;' statement.
#
# Note: Any environment variables needed at run time by RMAN
#       must be set and exported within the switch user (su) command.
# ---------------------------------------------------------------------------
#  Backs up the whole database.  This backup is part of the incremental
#  strategy (this means it can have incremental backups of levels >; 0
#  applied to it).
#
#  We do not need to explicitly request the control file to be included
#  in this backup, as it is automatically included each time file 1 of
#  the system tablespace is backed up (the inference: as it is a whole
#  database backup, file 1 of the system tablespace will be backed up,
#  hence the controlfile will also be included automatically).
#
#  Typically, a level 0 backup would be done at least once a week.
#
#  The scenario assumes:
#     o you are backing your database up to two tape drives
#     o you want each backup set to include a maximum of 5 files
#     o you wish to include offline datafiles, and read-only tablespaces,
#       in the backup
#     o you want the backup to continue if any files are inaccessible.
#     o you are not using a Recovery Catalog
#     o you are explicitly backing up the control file.  Since you are
#       specifying nocatalog, the controlfile backup that occurs
#       automatically as the result of backing up the system file is
#       not sufficient; it will not contain records for the backup that
#       is currently in progress.
#     o you want to archive the current log, back up all the
#       archive logs using two channels, putting a maximum of 20 logs
#       in a backup set, and deleting them once the backup is complete.
#
#  Note that the format string is constructed to guarantee uniqueness and
#  to enhance NetBackup for Oracle backup and restore performance.
#
#
#  NOTE WHEN USING TNS ALIAS: When connecting to a database
#  using a TNS alias, you must use a send command or a parms operand to
#  specify environment variables.  In other words, when accessing a database
#  through a listener, the environment variables set at the system level are not
#  visible when RMAN is running.  For more information on the environment
#  variables, please refer to the NetBackup for Oracle Admin. Guide.
#
# ---------------------------------------------------------------------------

CMD_STR="
ORACLE_HOME=$ORACLE_HOME
export ORACLE_HOME
ORACLE_SID=$ORACLE_SID
export ORACLE_SID
$RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append << EOF
allocate channel for maintenance type disk;
change archivelog all validate;
release channel;
RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch04 TYPE 'SBT_TAPE';
BACKUP
    $BACKUP_TYPE
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 7
    # recommended format
    FORMAT 'bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
RELEASE CHANNEL ch02;
RELEASE CHANNEL ch03;
RELEASE CHANNEL ch04;
# backup all archive logs
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
BACKUP
   filesperset 20
   FORMAT 'al_%s_%p_%t'
   ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
RELEASE CHANNEL ch02;
#
# Note: During the process of backing up the database, RMAN also backs up the
# control file.  This version of the control file does not contain the
# information about the current backup because "nocatalog" has been specified.
# Too include the information about the current backup, the control file should
# be backed up as the last step of the RMAN section.  This step would not be
# necessary if we were using a recovery catalog.
#
ALLOCATE CHANNEL ch00 TYPE disk;
COPY
    CURRENT CONTROLFILE to '/scripts/control.ora';
RELEASE CHANNEL ch00;
}
EOF
"
# Initiate the command string

if [ "$CUSER" = "root" ]
then
    su - $ORACLE_USER -c "$CMD_STR" >;>; $RMAN_LOG_FILE
    RSTAT=$?
else
    /usr/bin/sh -c "$CMD_STR" >;>; $RMAN_LOG_FILE
    RSTAT=$?
fi

# ---------------------------------------------------------------------------
# Log the completion of this script.
# ---------------------------------------------------------------------------

if [ "$RSTAT" = "0" ]
then
    LOGMSG="ended successfully"
/usr/openv/netbackup/bin/bpbackup -p oracle_control_file -s user -t 0 /scripts/control.ora
else
    LOGMSG="ended in error"
fi

echo >;>; $RMAN_LOG_FILE
echo Script $0 >;>; $RMAN_LOG_FILE
echo ==== $LOGMSG on `date` ==== >;>; $RMAN_LOG_FILE
echo >;>; $RMAN_LOG_FILE

exit $RSTAT

论坛徽章:
0
2 [报告]
发表于 2005-05-24 14:48 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

NetBACKUP 这么好,竟然提供这么详细的备份脚本。
我这里用的是TSM+RMAN,脚本都是自己写的,郁闷。

建议还是用catalog来做RMAN备份,只用controlfile来记录信息,总感觉不安全。

论坛徽章:
0
3 [报告]
发表于 2005-05-24 19:30 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

先顶一下!

论坛徽章:
0
4 [报告]
发表于 2005-05-24 19:50 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

好久不见斑竹了,留名先~~~~

论坛徽章:
0
5 [报告]
发表于 2005-05-25 15:11 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

原帖由 "balefired" 发表:
NetBACKUP 这么好,竟然提供这么详细的备份脚本。
我这里用的是TSM+RMAN,脚本都是自己写的,郁闷。

建议还是用catalog来做RMAN备份,只用controlfile来记录信息,总感觉不安全。


他的脚本通用得,大家都好用,你就不用写了

论坛徽章:
0
6 [报告]
发表于 2005-05-25 16:50 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

catalog是好,但是还要为此准备一个机器,有点烦:有时候生产环境是unix正版oracle,而catalog是win 盗版oracle。。。。

论坛徽章:
0
7 [报告]
发表于 2005-05-27 20:41 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

写得还比较详细

论坛徽章:
0
8 [报告]
发表于 2005-05-29 13:09 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

收藏拉,thanks

论坛徽章:
0
9 [报告]
发表于 2005-05-29 22:47 |只看该作者

使用rman nocatalog方式备份Oracle - NetBackup配置方法

在nocatalog下,采用邱总所说的以文件的方式备份controlfile的方法恢复起来比较容易,如果直接使用RMAN备份Controlfile,则恢复起来会比较麻烦。以前在nocatalog下一直都是采用RMAN备份controlfile的方法,恢复的时候稍微麻烦一点,记得以前有一个客户的数据库corrupt了,在OTN上找了很多资料才找到从磁带中恢复contolfile的方法。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP