RMAN备份Oracle数据库脚本（包括全备与增量）__RMAN_LOG_FILE_the_backup_BACKUP_TYPE_echo_

当前位置: 数据库>oracle

RMAN备份Oracle数据库脚本（包括全备与增量）

来源: 互联网发布时间：2017-05-09

本文导语: 一个客户原来的Oracle数据库没有上RMAN备份，平时都是使用的EXPDP来导数据做为备份，今天叫我给他们写一个脚本来实现每天的增量，一周做一次全备。于是马上把原来把NBU自带的RMAN备份脚本拿出来改改。下面是脚本内容，实现...

一个客户原来的Oracle数据库没有上RMAN备份，平时都是使用的EXPDP来导数据做为备份，今天叫我给他们写一个脚本来实现每天的增量，一周做一次全备。

于是马上把原来把NBU自带的RMAN备份脚本拿出来改改。

下面是脚本内容，实现每周周末一天全备，其它的时候都是增量备份，备份完的归档自己删除。

注意其中的参数，因为环境不同需要做相应的修改。

[oracle@11rac1 ~]$ cat hot_rman_backup.sh

#!/bin/sh

# $Header: hot_database_backup.sh,v 1.3 2010/08/04 17:56:02 $

# ---------------------------------------------------------------------------

# this script directory.

# ---------------------------------------------------------------------------

SHELL_HOME=/home/oracle

# ---------------------------------------------------------------------------

# Determine the time executing this script.

# ---------------------------------------------------------------------------

RMAN_DATA=`date '+%Y%m%d%H'`

# ---------------------------------------------------------------------------

# test log directiry . If not, run the following lines.

# ---------------------------------------------------------------------------

if [ ! -d "$SHELL_HOME/log" ]

then

mkdir -p $SHELL_HOME/log

# ---------------------------------------------------------------------------

# Put output in .out. Change as desired.

# Note: output directory requires write permission.

# ---------------------------------------------------------------------------

RMAN_LOG_FILE=${SHELL_HOME}/log/hot_rman_backup_${RMAN_DATA}.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"

# ---------------------------------------------------------------------------

# rman image output directory.

# ---------------------------------------------------------------------------

RMAN_IMAGE_DIR=/home/oracle/rman

echo "rman image output directory:${RMAN_IMAGE_DIR}">>$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/ora102, below, with the Oracle home path.

# ---------------------------------------------------------------------------

ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1

export ORACLE_HOME

# ---------------------------------------------------------------------------

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

# ---------------------------------------------------------------------------

ORACLE_SID=power1

export ORACLE_SID

# ---------------------------------------------------------------------------

# Set the target connect string.

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

# ---------------------------------------------------------------------------

TARGET_CONNECT_STR=sys/manager

# ---------------------------------------------------------------------------

# 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

# ---------------------------------------------------------------------------

# 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.

# ---------------------------------------------------------------------------

INCR_DATA=`date '+%A'`

if [ "$INCR_DATA" = "Sunday" ]

then

echo "Full backup requested" >> $RMAN_LOG_FILE

BACKUP_TYPE="INCREMENTAL LEVEL=0"

else

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"

echo "BACKUP_TYPE">> $RMAN_LOG_FILE

echo ${BACKUP_TYPE} >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------

# 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

# 'catalog /@' 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 NET SERVICE NAME: When connecting to a database

# using a net service name, 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.

# ---------------------------------------------------------------------------

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 $RMAN_LOG_FILE

echo ==== end on `date` ==== >> $RMAN_LOG_FILE

echo >> $RMAN_LOG_FILE

把脚本增加到crontab中

[oracle@11rac1 ~]$ crontab -l

1 3 * * * ksh /home/oracle/hot_rman_backup.sh >>/home/oracle/log/hot_rman_backup_crontab_`date "+%Y%m%d%H%M"`.log 2>&1

每天早上的3点进行备份，另外我们还需要的就是在RMAN中配置备份的保留时间与controlfile与spfile的自己备份。

您可能感兴趣的文章:

rman备份脚本和rman增量备份脚本分享

linux自动运行rman增量备份脚本

本站(WWW.)旨在分享和传播互联网科技相关的资讯和技术，将尽最大努力为读者提供更好的信息聚合和浏览方式。
本站(WWW.)站内文章除注明原创外，均为转载、整理或搜集自网络。欢迎任何形式的转载，转载请注明出处。