Netbackup安装配置.doc

精诠资讯（上海）有限公司工作记录贵州联通公司Netbackup、Overland安装报告精诠资讯（上海）有限公司广州办：刘在峰一、磁带库的安装：1、 将磁带库拆箱，将其固定在机架上。2、 用SCSI线将带库与主机（gyang_bf）连接起来，带库上为左边第一个SCSI口，用带库所附的较短的SCSI线连接第二、第三口，第四口接带库所附的终结器。 最后接上电源线。3、 将随箱所带的五盘磁带加上标签（label）。4、 打开带库电源，等待其初始化结束，按Unlock键，然后拔出带库槽，将五盘带子根据其标签的大小顺序依次排列放到槽内，再次按Unlock键，门开启后将槽放入带库。5、 这时带库会自动搜索磁带，搜索结果显示在面板上。如果正确可接着进行带库的Load/Unload测试。6、 带库在操作系统中的配置：#ioscan可以看出磁带机（DLT7000）能由操作系统识别出并给出了其相应的设备名/dev/rmt/c5t4d0BESTnb。而机械手的设备名需要手工配置： #mkdir /dev/sctl #cd /dev/sctl #mknod c5t6d0 c 203 0x056000二、 软件的安装：1、光驱的使用 pfs_mount a) 光驱使用的进程#ps ef|grep pfs_mountd 看有无此进程，若无，则：#nohup pfs_mountd &#nohup pfs_pfsd &b) #pfs_mount -o xlat=unix /dev/rdsk/c*t*d* /cdrom 其中/dev/rdsk/c*t*d*为光驱在系统中的设备名。2、Netbackup BusinesServer V3.4的安装a) server端的安装（gyang_bf）:将Netbackup BusinesServer V3.4安装盘放入光驱 #pfs_mount -o xlat=unix /dev/rdsk/c*t*d* /cdrom #cd /cdrom #install 选1 进行安装，最后输入产品的License号。b) client端的安装（gyang_yy）: 将Netbackup BusinesServer V3.4安装盘放入光驱 #pfs_mount -o xlat=unix /dev/rdsk/c*t*d* /cdrom #cd /cdrom #install选2 进行安装。c) Oracle Agent 的安装（gyang_yy）:将Netbackup BusinesServer V3.4 Oracle Agent安装盘放入光驱 #pfs_mount -o xlat=unix /dev/rdsk/c*t*d* /cdrom #cd /cdrom #install 选5 HP9000_800回车 选2 HP_UX 11.0软件安装后，分别在两台机器上建立/usr/openv目录，其下存放上述所安装的程序。三、 ORACLE数据库的重新连接（gyang_bf）1、 停掉当前正在运行的数据库：svrmgrl connect internal shutdown2、 对当前的动态库及oracle内核文件做备份：$cd $ORACLE_HOME/lib64$mv libobk.sl libobk.sl.orig$cd $ORACLE_HOME/bin$cp oracle oracle.orig3、 链接文件，重编译oralce:$cd $ORACLE_HOME/lib64$ln s /usr/openv/netbackup/bin/libobk.a64 libobk.sl$cd $ORACLE_HOME/rdbms/lib$make f ins_rdbms.mk ioracle LLIBMM=”$ORACLE_HOME/lib64/libobk.sl” LIBMM=注意：上述命令要在一行内完成。四、几个文件的配置：1、NOSHM文件的生成Netbackup不支持共享内存模式，所以要#cd /usr/openv/netbackup#touch NOSHM2、编辑server的 bp.conf文件(/usr/openv/netbackup目录下)，加入 SERVER=gyang_bf CLIENT=gyang_yy 编辑client的 bp.conf文件，加入 SERVER=gyang_bf CLIENT=gyang_yy五、RMAN数据库的建立：1、 在gyang_bf机上建立一个实例名为rman的数据库：用orainst工具，建立一个数据库，存放路径为/u04、/u03、/u02.2、 启动该数据库，为其建立一名为rcvcat的表空间。3、 建立一用户：名为rman ,口令为rman，缺省的表空间为rcvcat.4、 赋予用户rman 相应的权限：SVRMGRgrant connect,resource to rman;SVRMGRgrant recovery_catalog_owner to rman;5、 建立rman所属的表：$cd $ORACLE_HOME/rdbms/adminSVRMGRcatrman.sql6、 在gyang_yy及gyang_bf上配置监听：修改两个机器上的tnsnames.ora 、listener.ora 文件，加入实例rman.7、 注册数据库：在gyang_yy上： $rman target system/manager rcvcat rman/rmanrman RMANregister database 六、 备份脚本的修改：编辑gyang_yy主机上$ORACLE_HOME/scripts目录下的脚本，几个重要文件的内容分别是：1、 hot_database_backup.sh文件：#!/bin/sh# $Header: hot_database_backup.sh,v 1.3 2000/02/17 21:40:04 integ Exp $#bcpyrght#*#* $VRTScprght: Copyright 1993 - 2000 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 you should remove the switch user logic.# -# -# Put output in .out. Change as desired.# Note: output directory requires write permission.# -OUTF=$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 $OUTF thenrm -f $OUTFfi # output blockecho date -Beginning of Script-echo Script name: $0# -# Replace /db/oracle/product/8.0.5, below, with the Oracle home path.# -ORACLE_HOME=/u01/oracle/app/oracle/product/oracle/8.0.6export ORACLE_HOME# -# Replace ORA805, below, with the Oracle SID of the target database.# -ORACLE_SID=lasexport ORACLE_SID# -# Replace ora805, below, with the Oracle DBA user id (account).# -ORACLE_USER=oracle# -# Replace $ORACLE_HOME/scripts, below, with the NetBackup Oracle script# path. Since subsequent installs or deinstalls will remove this file,# you will want to move this script from its installed location before# making updates.# -NB_ORA_SCRIPTS=$ORACLE_HOME/scripts# -# Set the Oracle Recovery Manager name.# -RMAN=rman# -# Print out the value of the variables set by this script.# -echo echo RMAN: $RMANecho ORACLE_SID: $ORACLE_SIDecho ORACLE_USER: $ORACLE_USERecho ORACLE_HOME: $ORACLE_HOMEecho NB_ORA_SCRIPTS: $NB_ORA_SCRIPTS# -# Print out the value of the variables set by bphdb.# -echo echo NB_ORA_FULL: $NB_ORA_FULLecho NB_ORA_INCR: $NB_ORA_INCRecho NB_ORA_CINC: $NB_ORA_CINCecho NB_ORA_SERV: $NB_ORA_SERVecho NB_ORA_CLASS: $NB_ORA_CLASSecho NB_ORA_PC_SCHED: $NB_ORA_PC_SCHEDecho NB_ORA_SCHEDULED: $NB_ORA_SCHEDULEDecho NB_ORA_USER_INITIATED: $NB_ORA_USER_INITIATED# -# This script assumes that the database is properly opened. If desired,# this would be the place to verify that.# -echo if $NB_ORA_INCR = 1 thenecho hot database differential incremental backup requestedCMDFILE=$NB_ORA_SCRIPTS/hot_database_backup_level1_differential.rcvelif $NB_ORA_CINC = 1 thenecho hot database cumulative incremental backup requestedCMDFILE=$NB_ORA_SCRIPTS/hot_database_backup_level1_cumulative.rcvelse # defaultecho hot database backup requested (incremental level 0)CMDFILE=$NB_ORA_SCRIPTS/hot_database_backup_level0.rcvfi# -# Call Recovery Manager to initiate the backup. This example does not use a# Recovery Catalog. If you chose to use one, remove the option, nocatalog,# from the rman command line below and add a connect rcvcat statement to# the corresponding command file ($CMDFILE). An alternative to putting the# connect statements in the command file would be to add them to the rman# command line. # Note: Any environment variables needed at run time by RMAN or $CMDFILE# must be set and exported within the switch user (su) command.# -echo echo % $ORACLE_HOME/bin/$RMAN cmdfile $CMDFILEecho su - $ORACLE_USER -c ORACLE_SID=$ORACLE_SIDexport ORACLE_SID$ORACLE_HOME/bin/$RMAN cmdfile $CMDFILERETURN_STATUS=$?echo echo date -End of Script-echo echo exit $RETURN_STATUSexit $RETURN_STATUS $OUTF2、hot_database_backup_level0.rcv文件： # $Header: hot_database_backup_level0.rcv,v 1.5 2000/02/17 21:40:06 integ Exp $#bcpyrght#*#* $VRTScprght: Copyright 1993 - 2000 VERITAS Software Corporation, All Rights Reserved $ *#*#ecpyrght# -# hot_database_backup_level0.rcv# -# 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 want to perform a level 0 backup# 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 want to archive the current log and then back up all the # archive logs, putting a maximum of 20 logs in a backup set and# deleting them once the backup is complete.# o you are using a TNS alias name for the target database# Note that the format string is constructed to guarantee uniqueness and# to enhance NetBackup for Oracle backup and restore performance. # The connect statements could be part of the rman command line in the# Oracle script file that calls this script. They were put here so that# the passwords could be protected by setting file permissions to only# allow the Oracle dba access.# Add the following connect statement if using a Recovery Catalog.# connect rcvcat /# Modify the target connect statement according to the following syntax:# connect target /# Script run by:# rman nocatalog cmdfile hot_database_backup_level0.rcv# -#connect target internal/oracleproductionDBconnect target system/managerconnect rcvcat rman/rmanrmanrun # Hot database level 0 whole backupallocate channel t1 type SBT_TAPE; #allocate channel t2 type SBT_TAPE; backup incremental level 0 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 skip inaccessible filesperset 20 format al_%s_%p_%t (archivelog all delete input);3、hot_database_backup_level1_cumulative.rcv文件：# $Header: hot_database_backup_level1_cumulative.rcv,v 1.5 2000/02/17 21:40:09 integ Exp $#bcpyrght#*#* $VRTScprght: Copyright 1993 - 2000 VERITAS Software Corporation, All Rights Reserved $ *#*#ecpyrght# -# hot_database_backup_level1_cumulative.rcv# -# Backs up only the blocks which have been modified since the last# level 0 backup was performed. (note, the controlfile is always backed# up in its entirety i.e. control file backups are never compressed).# Typically, a level 1 backup would be done at least once in between# level 0 backups.# The scenario assumes:# o you want to perform a cumulative level 1 backup# 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 already have valid backups of read-only tablespaces, and# offline datafiles so we skip backing up these files# o you want the backup to continue if any files are inaccessible.# o you are not using a Recovery Catalog# o you want to archive the current log and then back up all the # archive logs, putting a maximum of 20 logs in a backup set and# deleting them once the backup is complete.# o you are using a TNS alias name for the target database# Note that the format string is constructed to guarantee uniqueness and# to enhance NetBackup for Oracle backup and restore performance. # The connect statements could be part of the rman command line in the# Oracle script file that calls this script. They were put here so that# the passwords could be protected by setting file permissions to only# allow the Oracle dba access.# Add the following connect statement if using a Recovery Catalog.# connect rcvcat /# Modify the target connect statement according to the following syntax:# connect target /# Script run by:# rman nocatalog cmdfile hot_database_backup_level1_cumulative.rcv# -#connect target internal/oracleproductionDBconnect target system/managerconnect rcvcat rman/rmanrmanrun # Hot database level 1 cumulative incremental backupallocate channel t1 type SBT_TAPE; #allocate channel t2 type SBT_TAPE; backup incremental level 1 cumulative skip offline skip readonly skip inaccessible tag hot_db_bk_level1_cum filesperset 5 # recommended format format bk_%s_%p_%t (database); sql alter system archive log current; # backup all archive logs backup skip inaccessible filesperset 20 format al_%s_%p_%t (archivelog all delete input);4、hot_database_backup_level1_differential.rcv文件：# $Header: hot_database_backup_level1_differential.rcv,v 1.5 2000/02/17 21:40:12 integ Exp $#bcpyrght#*#* $VRTScprght: Copyright 1993 - 2000 VERITAS Software Corporation, All Rights Reserved $ *#*#ecpyrght# -# hot_database_backup_level1_differential.rcv# -# Backs up only the blocks which have been modified since the last# level 0 backup was performed. (note, the controlfile is always backed# up in its entirety i.e. control file backups are never compressed).# Typically, a level 1 backup would be done at least once in between# level 0 backups.# The scenario assumes:# o you want to perform a differential level 1 backup# 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 already have valid backups of read-only tablespaces, and# offline datafiles so we skip backing up these files# o you want the backup to continue if any files are inaccessible.# o you are not using a Recovery Catalog# o you want to archive the current log and then back up all the # archive logs, putting a maximum of 20 logs in a backup set and# deleting them once the backup is complete.# o you are using a TNS alias name for the target database# Note that the format string is constructed to guarantee uniqueness and# to enhance