NetBackup LiveUpdate

[mbodsch]

Hi,

After a successful upgrade of my master and media servers to 7.5.0.4 I would like to push the new client to the hosts.
For this I installed a LiveUpdate Server on a Linux with Apache.

Because I was able to update my admin workstation (Windows 7) using a LiveUpdate policy, I can confirm that the LU server is running fine.

On most of the other hosts is SEP with an existing LiveUpdate agent running.
On these machines I ran the batch "LU_Install.bat" from within the "Addons\LiveUpdate" folder to register Netbackup with LU.

Unfortunately LU fails updating the NBU client:

26.10.2012, 06:40:53 GMT -> EVENT - SERVER SELECTION SUCCESSFUL EVENT - LiveUpdate connected to server 10.72.192.72 at path  via a HTTP connection. The server connection connected with a return code of 200, Successfully download TRI file
26.10.2012, 06:40:53 GMT -> LiveUpdate is connected to a server with Mini-TRI file support.  LiveUpdate will download and process the remaining Mini-TRI files.
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: Automatic LiveUpdate, Version: 3.3.0.115, Language: English.  Mini-TRI file name: automatic$20liveupdate_3.3.0.115_english_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: Decomposer, Version: 1.0.0, Language: SymAllLanguages.  Mini-TRI file name: decomposer_1.0.0_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: Symevent64x86 Installer, Version: 12.8, Language: SymAllLanguages.  Mini-TRI file name: symevent64x86$20installer_12.8_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: MS Light, Version: 5.0, Language: SymAllLanguages.  Mini-TRI file name: ms$20light_5.0_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: SESC Virus Definitions Win64 (x64) v11, Version: MicroDefsB.CurDefs, Language: SymAllLanguages.  Mini-TRI file name: sesc$20virus$20definitions$20win64$20$28x64$29$20v11_microdefsb.curdefs_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: SESC Virus Definitions Win64 (x64) v11, Version: MicroDefsB.Mar, Language: SymAllLanguages.  Mini-TRI file name: sesc$20virus$20definitions$20win64$20$28x64$29$20v11_microdefsb.mar_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: SESC Submission Control Data, Version: 11.0, Language: SymAllLanguages.  Mini-TRI file name: sesc$20submission$20control$20data_11.0_symalllanguages_livetri.zip
26.10.2012, 06:40:53 GMT -> Check for updates to:  Product: SESC AntiVirus Client Win64, Version: 11.0, Language: English.  Mini-TRI file name: sesc$20antivirus$20client$20win64_11.0_english_livetri.zip
...
...
...
26.10.2012, 06:40:54 GMT -> LiveUpdate did not find any new updates for the given products.
26.10.2012, 06:40:54 GMT -> EVENT - SESSION END SUCCESSFUL EVENT - The LiveUpdate session ran in Silent Mode. LiveUpdate found 0 updates available, of which 0 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 100, LiveUpdate ran successfully.  There are no new updates to your products.

To my understanding LU only tries to update the SEP products bunt not for NBU.

Because I have little knowledge of the internals of LU I don't know how to fix this problem.
Of course, I would like to avoid updating the client on every single machine (6.5.6 -> 7.5 -> 7.5.0.4 on about 20 machines).

Could someone please point me in the right direction?

Thanks,
Matt

[Mark_Solutions]

The Live Update Admin Guide warns about this but doesn't give much guidance:

If you have a local dedicated LiveUpdate server for other Symantec products like Symantec Endpoint Security or Symantec AntiVirus, be aware of potential conflicts.
To avoid conflicts, take one of the following actions:
■ Download NetBackup Release Updates to a different directory on your local Symantec LiveUpdate server.
■ Designate a different computer as your NetBackup LiveUpdate server.

There is a little more detail further on in the Appendix A References section which may help you in adding mutiple live update servers - or perhaps you just use your existing Live Update Server?

Hope this helps

[mbodsch]

Thank you for these hints.

Our local NBU LiveUpdate server is completely dedicated from the SEP LiveUpdate server.
Therefore a conflict between both repositories shouldn't be a problem.

Using the existing LiveUpdate server is no option unfortunately because it's located at our company's data center in London and very restricted - our local environment is in Germany.

I'll take a closer look at the mentioned Appendix A - maybe there's another option.

But it's really a shame that two products of the same company are conflicting each other.
I even need to disable the temper protection of SEP to install the NBU client on each host, because otherwise (according to the SEP logs) an "external process" tries to disable SEP services, which is blocked.