Video Screencast Help

Client binaries version on master is mismatched with master version

Created: 26 Oct 2012 • Updated: 13 Nov 2012 | 7 comments
This issue has been solved. See solution.

Hello Forum

Managed to find a hole in the NB installation, so well done me!

I've upgraded my MASTER to 7504 including CLT7504 (since its mandatory) but neglected to run the CLT 7.5 to add misc client binaries along the way.

I then ran CLT 7.5 afterwards (yes it let me) thinking this would give me client binaries and indeed it did, the 7.5 ones (confirmed via version files)

But now I cant run 7504 CLT because its already installed.

 

Hence master is 7504, client binaries are 7.5 but it thinks client binaries are 7504.

Is there a simple exit from this conundrum?

Three options:

-rerun 7504 with -p to force 7504 on again: it warns

Unless you are installing a new platform
type for a previously installed package,
it is strongly recommended that this package,
be uninstalled before reinstalling.

cd /usr/openv/pack/PACK_NAME/save
./NB_update.uninstall

-uninstall 7504 via pack/CLT7504/save (but will it work? and will it affect my live system?), reinstall 7504

(Doing this worries me : its the master , I dont want to downrev the master really just the client bins.)

-copy up the tars and untar in the client dirs, they will then be 7504 and the system will agree

Its a live system, the only issue is the mismatch between the client bins as far as I can see.

TIA,jim

 

 

Comments 7 CommentsJump to latest comment

Marianne's picture

Run 'NB_update.install -p' to force-install 7.5.0.4 Client patch.

 

*** Command edited by MvdB ****

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jim dalton's picture

Hello MVDB( once again )

Youve confused me slightly: you say 'Run NB_update.uninstall -p' to force install, I think you meant NB_update.install -p ie the first of the three options I laid out? There is no NB_update.uninstall... 

Just clarifying! I dont want to upset my running master server, as you will appreciate.

Thanks,Jim 

Marianne's picture

Apologies - not concentrating today! blush

NB_update.install -p

I will edit my previous post and fix it.

'NB_update.install -p' works - done it at a customer about a month ago.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
jim dalton's picture

Its never easy...went for the -p and its insisting that netbackup needs stopping...you can see my concern now: why would it need to stop netbackup to copy a few files? We're getting into the details of the patch here, I appreciate its more of a Symantec issue than a forum one.

Unless you are installing a new platform
type for a previously installed package,
it is strongly recommended that this package,
be uninstalled before reinstalling.

cd /usr/openv/pack/PACK_NAME/save
./NB_update.uninstall

Do you want to continue the install? [y,n] (n) y

Install pack NB_CLT_7.5.0.4 Fri Oct 26 11:28:09 BST 2012 Rev. 1.46.8.8
Can not install pack when NetBackup daemons are running.
    Do you want to kill all NetBackup daemons? [y,n] (y) n
Pack NB_CLT_7.5.0.4 install terminated, stop daemons and try again.

 

If you are certain it will do the business I can find a quiet time: you have ultimate confidence it worked for you, this very patch?

TIA,Jim

Marianne's picture

Yes. It REALLY works. We also had to stop NBU at big customer where we did this. Unfortunately no work-around....

After force-install, we verified 'version' files in Client folders - all good (was 7.5.0.3 at the time).

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jim dalton's picture

OK MVDB, I'm taking a little input from Symantec support on this, I'm pretty sure you'll be right, will update when I know (or otherwise)...meanwhile my other issue might keep you busy for a while...DR recovery, I'm sure you'll spot it!

Thanks so far,Jim

jim dalton's picture

MvdB solution was the preferred one. Support suggested uninstall which meant a whole heap of extra work and downgrade of the db then upgrade. A whole lot of going round the houses.

Jim