数据存储产业服务平台

私人笔记:NetBackup6.0 Beta3 升级安装步骤

    注:文章出自“DOSTOR论坛”之VERITAS存储技术专业社区,全文为个人经验总结,不代表DOSTOR观点


    更多信息可访问:http://bbs.dostor.com/viewthread.php?tid=26417&extra=page%3D1


    由于在NBU6.0中有了一个EMM(Enterprise Media Manager )的概念,NBU的升级不像以前那么简单了。需要将globDB,volDB,MediaDM 等一些信息导入EMM的数据库中。


    升级需要按照下面的顺序作才行:


    1.Global Device Host
    2.Master server
    3.Volume Database Host
    4.Media servers
    5.Clients


    NBU6.0支持混合环境,但是media server的版本不能低于NBU5.X。Client 的版本不能低于NBU4.5。NBU6.0只支持NBU5.X升级到NBU6.0。如果想使用NBU4.5 or NBU3.X升级到NBU6.0,需要先升级到NBU5.X。


    假设目前我们的环境是:


    Master server: host1, NBU5.1+MP2, Solaris 9
    Media server: host2, NBU5.1+MP2, Win2000 server+SP4.
    Client: host3, NBU5.1, Solaris 9
    Client: host4, NBU5.1, Win2000 server+SP4


    我们要将Master server and Media server 从5.1升级到6.0。


    升级的步骤如下:


    1.升级Master Server


    a)备份catalog(注意要加上media server 的路径……), 最好备两份一个用磁带,一个备份到硬盘上面。
    b)卸载NBU的包,卸载的时候注意“Are you doing this pkgrm as a step in an upgrade process? [y,n,?,q] “的提示,选择y
    Pkgrm VRTSnetbp
    c)安装PBX 和NBU6.0, 详情请看<< NetBackup6.0 Beta3  For Unix安装步骤>>
    d)注意当安装教本询问是否有其他Media server 的时候,一定要将以有的media server  名字加上,否则在以后添加的时候过程比较麻烦。
    e)注意提示的EMM server 的名字,最好就用master server。NBU6.0支持EMM server 装在其他Media server上,这中情况不再这次的讨论范围。
    f)检查包是否装上


# pkginfo |grep -i vrts
system      VRTSicsco   VERITAS Infrastructure Core Services Common
application VRTSnetbp     VERITAS NetBackup and Media Manager
system      VRTSpbx    VERITAS Private Branch Exchange


    g)用bpps ?Cx检查一下进程时候都起来了。
    h)运行如下命令,再运行的时候要确认其他media server 的进程都再。


# nbpushdata -add
Validating configured host names.
Successfully validated configured host names.


Host information found in the EMM Database
NetBackup 5.x Global Device Database host:
  host1
Masters:
  host1
Volume Database hosts:
  host1


Starting to add host1 records to EMM.


Processing: /usr/openv/netbackup/bp.conf
Pushed 4 records to EMM.


Processing: /usr/openv/volmgr/vm.conf
Pushed 0 records to EMM.


Processing: /usr/openv/netbackup/DONT_USE_SLAVE
Optional file does not exist.


Processing: /usr/openv/netbackup/DRIVE_ERROR_THRESHOLD
Optional file does not exist.


Processing: /usr/openv/netbackup/MEDIA_ERROR_THRESHOLD
Optional file does not exist.


Processing: /usr/openv/netbackup/TIME_WINDOW
Optional file does not exist.


Processing: /usr/openv/volmgr/NO_STANDALONE_UNLOAD
Optional file does not exist.


Processing: /usr/openv/volmgr/database/globDB
Estimated time remaining will be displayed every 5 minutes.
Pushed 3 records to EMM.


Processing: /usr/openv/volmgr/database/.namespace.chksum
Optional file does not exist.


Processing: /usr/openv/volmgr/database/robotic_def
Pushed 1 records to EMM.


Processing: /usr/openv/volmgr/database/ltidevs
Pushed 2 records to EMM.


Processing: /usr/openv/volmgr/database/poolDB
Pushed 0 records to EMM.


Processing: /usr/openv/volmgr/database/ruleDB
Optional file does not exist.


Processing: /usr/openv/volmgr/database/volDB
Estimated time remaining will be displayed every 5 minutes.
Pushed 0 records to EMM.


Processing: /usr/openv/netbackup/db/media/mediaDB
Optional file does not exist.


Processing: /usr/openv/netbackup/db/config/storage_units
Pushed 1 records to EMM.


Processing: /usr/openv/netbackup/db/config/stunit_groups
Optional file does not exist.


Searching for media that requires a robot type conversion.
Successfully completed media robot type conversion.


Searching for storage units that require a robot type conversion.
Successfully completed storage units robot type conversion.


Successfully added host1 records to EMM.
Starting to process legacy images on disk.
Converting images on /stu
Completed processing legacy images on disk.


    i)确认master 数据已经导入。


#nbpushdata -show_flags
NBPUSHDATA_G_HOST_1 = 1:1:1:1:0:600000:host1


    j)重启NBU的进程


# netbackup stop
stopping the NetBackup Service Monitor
stopping the NetBackup Service Layer
stopping the NetBackup Policy Execution Manager
stopping the NetBackup Job Manager
stopping the NetBackup request daemon
stopping the NetBackup compatibility daemon
stopping the NetBackup database daemon
stopping the Media Manager volume daemon
stopping the NetBackup Resource Broker
stopping the NetBackup Enterprise Media Manager
stopping the NetBackup Notification Service
stopping the NetBackup Database Server


# netbackup start
NetBackup Database Server started.
NetBackup Notification Service started.
NetBackup Enterprise Media Manager started.
NetBackup Resource Broker started.
Media Manager daemons started.
NetBackup request daemon started.
NetBackup compatibility daemon started.
NetBackup Job Manager started.
NetBackup Policy Execution Manager started.
NetBackup Service Layer started.
NetBackup Service Monitor started.


# bpps -x
NB Processes
————
    root  9780  9762  0 03:21:58 ?0:00 sh -c “/usr/openv/netbackup/bin/nbproxy” dblib nbpem_email
    root  9783     1  0 03:21:59 ?0:00 /usr/openv/netbackup/bin/nbsvcmon
    root  9713     1  0 03:21:40 ?0:01 /usr/openv/netbackup/bin/nbrb
    root  9781  9780  0 03:21:58 ?0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
    root  9707     1  0 03:21:37 ?0:00 /usr/openv/netbackup/bin/nbnos
    root  9774  9773  0 03:21:54 ?0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
    root  9704     1  0 03:21:30 ?0:02 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
    root  9729     1  0 03:21:43 ?0:00 /usr/openv/netbackup/bin/bprd
    root  9757  9756  0 03:21:50 ?0:01 /usr/openv/netbackup/bin/nbproxy dblib nbjm
    root  9756  9750  0 03:21:50 ?0:00 sh -c “/usr/openv/netbackup/bin/nbproxy” dblib nbjm
    root  9750     1  0 03:21:48 ?0:01 /usr/openv/netbackup/bin/nbjm
    root  9739     1  0 03:21:45 ?0:00 /usr/openv/netbackup/bin/bpcompatd
    root  9762     1  0 03:21:52 ?0:01 /usr/openv/netbackup/bin/nbpem
    root  9738     1  0 03:21:45 ?0:00 /usr/openv/netbackup/bin/bpdbm
    root  9710     1  0 03:21:38 ?0:02 /usr/openv/netbackup/bin/nbemm
    root  9773  9762  0 03:21:54 ?0:00 sh -c “/usr/openv/netbackup/bin/nbproxy” dblib nbpem
    root  9778     1  0 03:21:56 ?0:00 /usr/openv/netbackup/bin/nbsl
    root  9740  9738  0 03:21:45 ?0:00 /usr/openv/netbackup/bin/bpjobd


MM Processes
————
    root  9747  9718  0 03:21:48 ?0:00 avrd
    root  9755     1  0 03:21:49 ?0:00 tldcd
    root  9718     1  0 03:21:41 ?0:00 /usr/openv/volmgr/bin/ltid
    root  9742  9718  0 03:21:46 ?0:00 tldd
    root  9726     1  0 03:21:43 ?0:00 vmd


Shared VERITAS Processes
————————
root  6351     1  0 01:10:03 ?0:04 /opt/VRTSpbx/bin/pbx_exchange


    k)jnbSA进入java界面,界面和原来的基本相同,测试一下本机的备份,看是否成功。


    提示:如果成功,开始升级media server。没成功的话只能卸了重做吧……


    2.升级Media Server


    a)从系统中卸载NBU5.1。注意在 “Add or Remove Programes” 选择VERITAS Netbackup 后,要选择Change,这时候会出现VERITAS NetBackup 的卸载程序的界面,继续选择remove。注意在卸载的过程中会有一个提示“Remove All NetBackup configuration,catalogs,and log files”,千万不要选这个选项。这样NBU将被卸载,但是其他配置信息将被保留。
    b)重新启动服务器。这点非常重要千万别偷懒,否则会碰到一些莫名其妙的问题。
    c)放入NBU6.0 ICS的光盘,安装PBX。(在安装NBU6.0主程序的时候会检测,如果没有发现PBX,NBU6.0会自动安装它的。)
    d)放入NBU6.0 for Windows 32bit 的光盘,开始安装NBU6.0,过程省略……
    e)进到NBU的安装路径,运行下面的命令将Media server 上的数据迁移到EMM。
    Cd < NBU install path >veritas
etbackupin
    Nbpushdata ?Cadd
    f)重新启动NBU的服务,进入NBU的GUI,使用master server 和本级的STU进行备份,如果备份成功说明成功。


    如果不想升级media server 到NBU6.0,只是将原有的配置迁移到EMM上,就需要如下方法:


    a)登陆到NBU6.0的master server 上面。
    b)运行如下命令:
    Cd /usr/openv/netbackup/bin
    nbpushdata -add_5x_vmhost host2


    3.升级Clients


    NBU客户端的升级和以前4.5,5.X的差不多。Unix 的可以通过命令update_clients或者jnbSA升级。


    Windows的客户端就直接安装NBU6.0就可以了。

未经允许不得转载:存储在线-存储专业媒体 » 私人笔记:NetBackup6.0 Beta3 升级安装步骤