VERITAS NetBackup体系架构及环境简述

一、简介:

NetBackup 是 Symantec 公司提供的企业级备份管理软件,它支持多种操作系统,包括 UNIX、Microsoft Windows、OS/2 以及 Macintosh 等。NBU 是目前使用最广的备份软件。

NBU 采用全图形的管理方式,同时提供命令行接口,适应不同的用户需求。它提供了众多的性能调整能力,从管理角度看,其高性能特征十分明显。如提供多作业共享磁带机、大作业并行数据流备份、完善的监控报警、动态备份速度调整等能力,为用户的集中式存储管理提供了灵活和卓有成效的手段。

通过管理界面,管理员可以设置网络自动备份策略,这些备份可以是完全备份,也可以是增量备份。同时, NBU 还管理存储设备。如果采用磁带库,它可以驱动机械手(磁带库使用机械手作为磁带自动加载工具),管理磁带

它是于2004年被symantec收购veritas公司的一款产品,该产品功能强大,分为初级的NetBackup EXEC和高级的NetBackup产品。目前最新版本为8.0

二、体系架构

现有数百种产品可以为开放系统环境执行备份与恢复,但为处理现代数据中心的大量数据而专门设计的却少之又少。NetBackup Enterprise拥有一个核心三层体系架构。它整合了尖端介质管理功能和高性能,能够适应最大规模数据中心的需求。

 

NetBackup Enterprise的三层体系结构包含三类主要的组件,即Master Server(主服务器),Media Servers(介质服务器),Clients(客户端)。典型的NetBackup Enterprise的备份管理系统是由一个Master Server,一个或多个Media Servers,以及多个Clients组成;这样的一个备份管理系统就构成一个NetBackup的存储备份域(NetBackup Storage Domain)。比较大的备份管理系统,特别是跨地域的备份系统,则包含可能包括多个备份域。(注:在此NetBackup Enterprise本身是三层体系结构,再加上集中管理工具Global Data Manager,则构成了四层体系结构)

 

wKiom1lcXCnAtZgnAAE3Q4vROSw461.png-wh_50

 

NetBackup Master Server

NetBackup Master Server是NetBackup Enterprise第一层的部件。Master Server是管理一切数据保护工作的“大脑”,是最核心的部件。它所管理的工作包括:任务调度、客户端备份、介质管理、设备管理等等。Master Server本身也可以挂接一个或多个备份设备,来直接对客户端进行备份。

 

NetBackup Media Server

当需要备份的数据属于不同分组(如不同部门、子系统、应用等)或数据量比较大的时候,我们需要使用多个Media Servers来做分组备份管理和分担备份任务。Media Server代表第二层,备份设备挂接在Media Server上,以本地方式备份大型应用,同时还可以备份网上的其它客户机系统。Media Server可以和Master Server或其他的Media Server共享磁带库,也可以配置其自己的磁带设备。在有多个Media Servers的情况下,一个Media Server因故障停止数据保护工作的时候,可以由Master Server把这个Media Server的数据保护工作转移到另外的Media Servers上。

阅读更多

NBU备份oracle全备脚本注释(非常实用)

root@gzzynbu1 # more hot_database_backup.sh

#!/bin/sh

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

#

#bcpyrght

#*********************************************************************

#* $VRTScprght: Copyright 2014 Symantec 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/ora102, below, with the Oracle home path.

# —————————————————————————

ORACLE_HOME=/db/oracle/product/ora102 #oracle目录

export ORACLE_HOME

# —————————————————————————

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

# —————————————————————————

ORACLE_SID=ora102 #备份的数据库

export ORACLE_SID

# —————————————————————————

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

# —————————————————————————

ORACLE_USER=ora101备份使用的系统用户

# —————————————————————————

# Set the target connect string.

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

# —————————————————————————

TARGET_CONNECT_STR=sys/manager ### sys/manager 改为 / ###

 

# —————————————————————————

# Set the Oracle Recovery Manager name.

# —————————————————————————

RMAN=$ORACLE_HOME/bin/rman #NBU中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.

# —————————————————————————

阅读更多