Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

NOM chicken & egg situation

Updated: 21 May 2010 | 11 comments
RichardXClark's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Which to upgrade 1st?

NOM Server or Clients?

http://seer.entsupport.symantec.com/docs/295597.htm

If you are at 6.0 MP4, like me, the official answer is both!

I had hoped to do a phased upgrade to 6.5.4.
I had hoped to 1st upgrade NOM server and our AIX master on the same day, then our various Win32 masters over the course of a month or so.

I cant take the risk of a big bang approach.

If I go for a phased rollout, how will NOM fail? If its minor, I can accept a risk.
If it just plain cannot work at all, I may have to run 2 NOM variants.
Or maybe run 2 upgrade waves.
A skinny upgrade to MP5.
Then the 'full fat' upgrade to 6.5.4

Anyone gone through this headache?

Thanks
Rich

discussion Filed Under:

Comments

Abesama's picture
23
Jun
2009
0 Votes 0
Login to vote

I have not run NOM server myself

I have not run NOM server myself

But I think higher version of NOM server will work fine with lower version of NBU master servers.

If I were you, I'd upgrade the NOM server first.

Abe

Anger Management

RichardXClark's picture
24
Jun
2009
0 Votes 0
Login to vote

I hope it will work but the

I hope it will work but the link I posted above states that it is not supported.

Stumpr's picture
24
Jun
2009
0 Votes 0
Login to vote

NOM supports multiple versions

I don't quite understand the dilemma.
NOM supports multiple versions of NetBackup masters.

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

Abesama's picture
24
Jun
2009
0 Votes 0
Login to vote

You are right

Yes, you are right - the documentation you quoted does say this...

= = =
NOM 6.5 release updates also have backward compatibility with NetBackup 6.0 MP5 and above. See the table below.
= = =

I'm not sure how critical your NOM operation is to your organization, but if you can't afford NOM downtime at all, then yes it will be a good idea to do the "skinny upgrade" of the master to MP5, then upgrade NOM to 6.5 and upgrade master again.

Well, all backup admins (you and me, all of us) are encouraged to apply latest MP anyway.

:-)

Abe

Anger Management

hammers09's picture
24
Jun
2009
0 Votes 0
Login to vote

NOM etc

Thinking about this logically

NOM has to sit on a netbackup client (can be on a media server but not recommended due to performance issues)

A netbackup client should never be a higher version than its master

Therefore you should upgrade the master first and then the client on the NOM server and then NOM 

All other clients can then be upgraded when convenient

RichardXClark's picture
25
Jun
2009
0 Votes 0
Login to vote

6.0 MP4 not backward compatible 6.0 MP5 onwards is

The key part to my dilema is that backward compatibility starts from 6.0 MP5 onwards.
My whole environment is 6.0 MP4.

100% uptime is not critical as such but I have worked hard to get NOM useful, with a dozen or so daily reports going out to various managers and remote site support staff.

If the upgrades to 6.5.4 take a few weeks, having NOM fail for this duration reflects badly on my team.

I have virtualised NOM. I am testing the upgrade. Using VM snapshots, I can roll back in time in an instant. This way I can determine if the backward compatibility issues are minor or major & then make a risk management decision from this.

thx
Rich

hammers09's picture
25
Jun
2009
0 Votes 0
Login to vote

backwards compatabilty

Its only the masters that need to be at mp5 or above as you are extracting info from the masters databases

if you only have one master then that needs to be at 6.5.4 if thats the version the NOM server will be at

RichardXClark's picture
25
Jun
2009
0 Votes 0
Login to vote

I have 1x AIX master & 9x Win32 masters in remote locations

yes i know this

I have 1x AIX master & 9x Win32 masters in remote locations

thats too much effort to go 6.5.4 in a big bang

a skinny MP is much less effort

hammers09's picture
25
Jun
2009
1 Vote +1
Login to vote

recommendation

DAY 1

In that case upgrade all master servers to 6.0 mP7 as that is the lates 6.0 service pack - easily done in a couple of  hours
Upgrade NOM server to same netbackup client version 6.0 mp7 and upgrade nom to same version take about 30 - 40 mins

DAY 2

Upgrade the NOM servers master to 6.5.4
Upgrade NOM server to 6.5.4 including the relevant NOM upgrades

All other masters can then be upgraded as required over time

Abesama's picture
25
Jun
2009
0 Votes 0
Login to vote

I'd follow hammers09's advice

Yep that sounds like the best option for you Richard.

All of your 10 masters are managed by the same one NOM server right.

Then the first line and the third line in the DAY 2 will need to be merged in to one line.

Abe

Anger Management

RichardXClark's picture
26
Jun
2009
0 Votes 0
Login to vote

MP7

Thx guys.

Yes 1 NOM for all masters.
Agreed. MP7 it is.
We have a plan!