Veritas NetBackup Oracle客户端配置步骤
Veritas NetBackup Oracle客户端配置步骤
至此NBU Oracle Agent安装完毕,执行下述步骤:
1、正常的关闭oracle数据库
# su - oracle
$ sqlplus ‘/as sysdba’
sqlplusshutdown immediately
sqlplusexit
2、以oracle用户的身份,执行oracle_link
$ /usr/openv/netbackup/bin/oracle_link
3、在数据库服务器的数据分区内创建数据库备份脚本目录
# mkdir /oracle/ora_bak_scripts
4、创建oracle备份的脚本
# cp –r /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/* /data01/bak_scripts
5、根据实际情况编辑oracle备份脚本
在我们拷贝到数据库备份脚本目录中的范本文件中,我们比较多使用的是hot_database_backup.sh (联机数据库备份脚本)。以下说明如何编辑数据库备份脚本。
#!/bin/sh
# $Header: hot_database_backup.sh,v 1.2 2002/08/06 23:51:42 $
#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2003 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=/u01/oracle/product/9.2.0 注意:如果实际的oracle主目录与此不同,请根据实际情况更改
export ORACLE_HOME
# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle SID of the target database.
# ---------------------------------------------------------------------------
ORACLE_SID=oraprod 注意:管理员需要根据需要备份的数据库名修改
export ORACLE_SID
# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle DBA user id (account).
# ---------------------------------------------------------------------------
ORACLE_USER=oraprod 此处需要填写实际的oracle数据库用户
# ---------------------------------------------------------------------------
# Set the target connect string.
# Replace ;sys/manager;, below, with the target connect string.
# ---------------------------------------------------------------------------
TARGET_CONNECT_STR=system/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
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 isBACKUP_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
RUN {
为备份打开备份通道,如果是lan free备份则打开两个通道,如果是lan备份则只要打开一个通道,本次备份使用了一个通道
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' ;
BACKUP
$BACKUP_TYPE
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
# recommended format
FORMAT 'bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
# backup all archive logs
BACKUP
filesperset 20
FORMAT 'al_%s_%p_%t'
ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00; 如果只打开一个备份通道则不需要这行
#
# 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.
# To 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.
#
BACKUP
# recommended format
FORMAT 'cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
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;
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
http://www.unionchina.com.cn/veritas-netbackup-oracle-config.htm
分享到:
相关推荐
在安装和配置Veritas NetBackup时,需要首先准备安装环境,然后进行NetBackup服务器和客户端的安装。服务器安装完成后,需要进行相应的配置,包括设备配置、备份策略配置等。安装步骤包括: 1. 安装环境准备。 ***...
配置NetBackup涉及设置Master Server、Media Server、客户端以及备份策略等。用户界面直观,提供图形化工具进行管理。 1. **安装与升级**:遵循官方提供的步骤进行安装,确保所有组件正确配置。 2. **策略创建**:...
### VERITAS NetBackup 6.0 系统管理员指南:介质管理器知识点解析 #### 一、介质管理器的功能 介质管理器是VERITAS NetBackup 6.0的重要组成部分,它主要用于控制磁带存储设备,并跟踪这些设备中使用的可移动介质...
- 在执行任何恢复操作之前,请确保已经正确配置了NETBACKUP服务器和客户端之间的连接,并且备份集已经被正确创建。 - 时间点恢复可能会导致丢失从目标时间点到当前时间的数据更改,因此在执行此类操作之前需要仔细...
1. **安装与配置**:在Windows环境中安装NetBackup软件,包括设置备份服务器、配置客户端代理以及安装SAP特定插件。这涉及到对操作系统、网络和SAP系统的深入了解。 2. **SAP集成**:NetBackup与SAP的紧密集成,...
接下来,NetBackup的安装和配置是实现备份功能的关键步骤。Master Server作为整个备份环境的核心,负责管理和调度备份作业。在安装前,确保硬件和操作系统满足最低要求,并准备好必要的许可证文件。安装过程包括安装...
NetBackup 7.7.3 是Veritas公司推出的一款强大的企业级数据保护解决方案,它能够为各种环境提供全面的数据备份和恢复服务。本套资源包含了NetBackup 7.7.3的官方全套中文版手册,对于理解和操作NetBackup系统具有极...
NetBackup 10.0 for Oracle 的安装和配置过程包括以下步骤: * 安装 NetBackup Server:安装 NetBackup Server 软件,配置服务器的基本信息。 * 安装 NetBackup Client:安装 NetBackup Client 软件,配置客户端的...
总的来说,《Netbackup for Oracle配置指南》提供了详细的步骤和说明,帮助用户在UNIX环境下正确配置Netbackup客户端和Oracle代理,实现高效的数据保护。对于从事Oracle数据库管理和维护的IT专业人员,这份指南无疑...
Veritas NetBackup Copilot是Veritas Technologies LLC推出的一款专门针对Oracle数据库备份与恢复的解决方案,其配置指南3.1和3.1.1版本详细介绍了如何有效地设置和使用该工具。Copilot旨在提供一个直观、高效的环境...
1. 安装和激活:首先,你需要安装NetBackup Copilot软件,并确保所有依赖项已就绪,如Java运行环境和Oracle客户端。 2. 配置Oracle环境:配置Oracle数据库服务器和NetBackup服务器之间的通信,包括网络设置、认证和...
配置步骤大致如下: 1. 配置Oracle环境:确保Oracle数据库已经正确安装并配置,包括RMAN配置和必要的权限设置。 2. 安装NetBackup Copilot:按照官方文档的指示,在各个服务器上安装所需的组件。 3. 配置NetBackup...
接下来,我们将分步骤介绍 Oracle 客户端代理的安装和备份计划的配置。 1. 安装 Oracle 客户端代理 在 Oracle 主机上安装 NBU 客户端代理前,你需要访问 Veritas 官方网站...
《NetBackup for Oracle on Windows NT 系统管理指南》是一本详细介绍如何在 Windows NT 环境下使用 Veritas NetBackup 软件对 Oracle 数据库进行备份与恢复的专业指南。该文档针对系统管理员编写,旨在帮助他们理解...
3. **集成NetBackup**:Copilot需要与现有的NetBackup基础设施集成,这涉及到配置NetBackup主服务器、客户端代理以及必要的策略设置,以确保Copilot能顺利地监控和管理Oracle备份作业。 4. **Oracle数据库配置**:...
Veritas NetBackup Copilot是Veritas Technologies LLC推出的一款专门针对Oracle数据库备份与恢复的解决方案,其配置指南(Release 3.1)详细介绍了如何设置和管理这个工具,以确保高效、安全地保护Oracle数据。...
Veritas NetBackup 8.1.1 网络端口参考指南 Veritas NetBackup是一款业界领先的数据保护解决方案,其8.1.1版本提供了全面的网络端口配置...理解并正确配置这些端口是实现NetBackup系统无缝集成和稳定运行的关键步骤。
- **选择客户端以供脚本或模板使用**:若采用传统的客户端脚本备份方式,则在此步骤进行配置。 - **图形化配置实例**:若采用图形化配置,则可以选择整库、单独表空间、库文件或快速恢复区(FRA)等不同的备份对象...