Video Screencast Help
Backup and Recovery Community Blog

NetBackup - Upgrade from 6.5.1 to 6.5.4 (a.k.a. "A Job Well Done?")

Created: 21 Jul 2009 • 9 comments
Andy Welburn's picture
0 0 Votes
Login to vote

The Hustle

Our requirement:   to ensure we have the latest available NetBackup version installed, essentially to cater for Win2008 servers but also for any other benefits with the latest release.

We initially intended to upgrade to 6.5.2 shortly after its release during the first half of 2008, however this idea was soon binned due to the number of bugs reported in the GA version & 6.5.2A (having only fixed the scheduling issue) was not deemed to be acceptable either. Deciding to monitor the release of 6.5.3 we waited & waited and to all intents & purposes it looked like this was an acceptable version to upgrade to - & then the security hotfix meant! However, we did still have every intention of upgrading to this version. But time wore on and then 6.5.4 was on the horizon so it was deemed appropriate to await developments & monitor the forums for possible issues.

There are, so far, only a couple or three new issues with 6.5.4 (e.g. VSS & system state issues and NDMP direct copy), but, as our number of 2008 servers is starting to increase & as yet no backups thereof, it was decided that it’s now time to upgrade. So, with this in mind, I thought I may as well detail what is (or should be!) a relatively straightforward process documented in the following Blog updates.

Please be patient with me as I intend to do this as best I can in a step-by-step, logical (me?) or chronological order as I get the chance to update it, but as things change, issues arise ...... ?

Also note that this is how I carried out the upgrade & it may, or may not, be correct for every (or any!!) other environment.

Comments 9 CommentsJump to latest comment

Andy Welburn's picture

Solaris 9 Master/Media server running NB6.5.1

120+ Windows clients (2K, 2K3 either physical or virtual) running NB5.1MPx & NB6.5.x

30+ Solaris clients (Solaris 7 thru’ Solaris 10) running NB5.1MPx & NB6.5.x

2 NetApp filers (ONTAP version 7.2.4)

Plus, a couple or three Win2K8 servers currently ‘unsupported’ (by us that is!).

Login to vote
Andy Welburn's picture

Upgrade the Master/Media server to 6.5.4 (Client, Server, Agents & Options as appropriate)

Upgrade clients on a piecemeal basis as & when the need or opportunity arises. Windows clients (other than W2K) only up to due to the VSS/system state issues.

Install on the ‘new’ Win2K8 clients & get them backed up!

Login to vote
Andy Welburn's picture

Various downloads were required to achieve our aims:

For the Solaris Master/Media

For the Solaris clients
Will utilise ‘update_clients’ once Master upgraded.

For the Windows clients (Win2K)
NB_6.5.4.Winx64_CD_326387.exe (for new installs only)

For the Windows clients (other than W2K)

Aiders & Abetters
Late Breaking News (LBN) bulletin for NetBackup 6.5.3
Late Breaking News (LBN) bulletin for NetBackup 6.5.4
NDMP Direct Copy feature is broken in NetBackup 6.5.4
List of links to the NetBackup Enterprise Server 6.5.4 Release Update downloads
List of links to the NetBackup Enterprise Server 6.5.3 Release Update downloads
List of links to the NetBackup Enterprise Server 6.5.3 Hotfix 1 ( downloads

Login to vote
Andy Welburn's picture

All of the above packages downloaded centrally & then distributed as necessary: tar packages to filesystem on Master server & Windows executables to a CIFS share on one of the two filers.

All files ‘extracted’ awaiting window of opportunity:
eg: on Solaris Master
tar  xvf  NB_CLT_6.5.4_326396.tar
tar  xvf  NB_6.5.4.solaris_326381.tar
tar  xvf  NB_DMP_6.5.4_326403.tar
tar  xvf  NB_JAV_6.5.4_326406.tar

Did not perform NBCC before performing upgrade - maybe I should've?

Login to vote
Andy Welburn's picture

Ensured that all jobs finished & Catalog Backup run to ensure ‘clean’ restore point if required.

To ensure no activity at all on the Master server all NetBackup services were stopped:
/opt/openv/netbackup/bin/goodies/netbackup stop

PBX: leave this daemon running as it is required for the install (so I found out after initially stopping it – the install script does check & prompts for starting PBX if it’s not running)

From within the directory containing the extracted tar files the install command was run:
/bin/sh NB_update.install

This prompted:

There are 4 packs available in /netbackup/654upgrade:
(* denotes installed pack)


Enter pack name (or q) [q]:

Chose NB_6.5.4 as I knew it would install the client itself first automatically. It also installed the Java package as per the following extract:
Pack NB_6.5.4 requires pack NB_CLT_6.5.4 or a later.

Pack NB_6.5.4 requires the following pack levels(s) :

Pack NB_6.5.4 will not be installed at this time.

Installing required pack, NB_CLT_6.5.4, now.

Pack NB_CLT_6.5.4 co-requires the following pack level(s) :
NB_6.5.4 NB_JAV_6.5.4.

Install pack NB_CLT_6.5.4 Monday July 20 11:29:55 BST 2009 Rev.
The pbx_exchange daemon is not running and is required for this installation.
Do you want to restart this daemon? (y/n) [y]
Started Symantec Private Branch Exchange

The install then went on to extract & install the necessary binaries for NB_CLT_6.5.4 followed by NB-6.5.4 & then NB-JAV-6.5.4.

When complete propmpted with:

There are 4 packs available in /netbackup_logs/654upgrade:
(* denotes installed pack)

NB_6.5.4 *
NB_CLT_6.5.4 *
NB_JAV_6.5.4 *

Enter pack name (or q) [q]:

So the NDMP option (NB_DMP_6.5.4) was selected. Once installed the process was exitted [q].

So, all the packs have now been successfully installed & no errors reported. All that remained was to start NetBackup & monitor!

First appearances seemed to indicate there were no problems, all jobs previously suspended or cancelled prior to the upgrade were either manually re-started or picked up & restarted by nbpem. They also all finished ok.

Will continue to monitor & report any issues, so watch this space ...

Login to vote
Andy Welburn's picture

W2K - upgrades pending to 6.5.4

W2K3 - selected one x86 client so far & installed 6.5.3 & hotfix. Backups running ok.

W2K8 - have installed on two 32-bit clients & upgraded to After fiddling around with the clients firewall (connectivity issues) & also the WOFB/multi-streaming settings (EC49 issues) for these clients, backups appear to be running ok.
cannot connect (Status 25) & WIN2008         thanks Rajeev (rj_nbu)
issue with 6.5.3 and 2 of my 2008 servers    thanks Judy.

Login to vote
Karthikeyan Sundaram's picture

Great Andy ! Upgrade going in Fibre Speed...

Thanks, Karthikeyan Sundaram.

Login to vote
Andy Welburn's picture

1) Was using 6.5.1 Windows Admin Console on my PC for monitoring & changes etc. After upgrade of Master to 6.5.4 whenever we made 2 changes to a policy, e.g. deactivate/activate the second change would fail with the following error:

"The policy, blah-blah-blah, could not be modified, status: 238
the database contains conflicting or erroneous entries"

This happened on more than one PC (altho’ did appear to be ok using the Java console), so upgraded to to see if it would fix the problem – only to be told when trying to launch the application that “Administration Console cannot be run at when the Master server is running 6.5.4” or some such error. Not sure if this is a problem with the hotfix (Did I read this somewhere? Can’t remember, think I’m suffering from brain-fade!) so instead of removing same I upgraded 'Admin Console' to 6.5.4 & this resolved the issue.

[[ Aside: To compound matters, when trying out 2008 Windows Clients for the first time we had a “shuttle error” on our robot, which entailed a re-boot of the library & master server – not what you want having just upgraded an application!!! ]]

2) 6.5.1 used to ignore SSO paths for inactive (i.e. switched off) media servers (probably a bug on our system!) – not so 6.5.4. The Admin Console is showing all SSO drives, where the media server is off, as partially up & also Image Cleanup is reporting “could not connect to host” error which may also be related? I need to re-visit this as the media server in question was set up using an eval.licence which has now expired, so somehow I need to decommission it. Get the distinct feeling things have been tightened up somewhat since 6.5.1!!
Decommissioning 'expired' Media Server in SSO environment.
"Problems" with Image Cleanup since upgrade to 6.5.4

May need to update this page from time-to-time ....

***EDIT #1***

3) Admin Console bug? - tape drive control seen to 'flip' between TLD and AVR modes altho' no issues manifested with respect to failures.

Login to vote