OK, first rule...forget the documentation Symantec gives you for this
process..unfortunately it is not great. Here is what we use to get http going
for lu for either Windows or Unix. We have had no problem with it now that we
have the process down..and have been able to patch application clusters...so
not sure what other people have seen there. Hope this helps:
OK, we usually use http. The disk share method is for Windows only and Unix
clients can't get to the patches, which kind of defeats the purpose in my
opinion. So, we stick with http...here is the process we use:
For unix live update server http access:
1. Pull down patches to lu server/dir, unzip all in same dir (no subdirs
for each patch bundle)
2. turn on http on lu server
/etc/init.d/apache start (first copy /etc/apache/httpd-example.conf
--> httpd.conf)
3. ln -s <liveupdate dir> /var/apache/htdocs/<liveupdate dir name> or
where ever www root is, above is default, this setting can be determined from
the apach.conf file in /etc/apache/apache.conf
4. install nblu on any
/usr/openv/netbackup/bin/install_nblu
when prompted type in:
url=http://<liveupdateserver</<liveupdatedir>
5. Create lu policies per normal documentation and go
For windows live update server http access:
1. Install IIS, need windows install cd, control panel/add remove
programs/windows components/application services/IIS (must go into details at
each level to unselect and select components you want for IIS and www)
2. Start www service
3. Launch IIS manager, highlight default web site, right click, new
virtual dir.
4. Put all patches in wwwroot\liveupdate (c:\inetpub\wwwroot\create
virtual dir in IIS for liveupdate
5. Unzip all in same dir (no subdirs)
6. SET LU_SERVER=http://<luserver>/liveupdate (in
installdir/symantec/liveupdate/LU_install.bat, then run it, make sure you have
3 exe's in there with it, LUCheck, LU_Registration LUSetup, all 4 files on NBU
windows install cd)
**NOTES: keep all dir names and servernames lower case for unix/windows
Renee Carlisle
ServerWare Coporation
From: [email protected]
[mailto:[email protected]] On Behalf Of Ed Wilts
Sent: Thursday, February 12, 2009 12:10 PM
To: Michitsch, John
Cc: [email protected]
Subject: Re: [Veritas-bu] Netbackup Live Update.
On Wed, Feb 11, 2009 at 12:56 PM, Michitsch, John
<[email protected]<mailto:[email protected]>> wrote:
Is anyone using this to upgrade client agents. All things I've seen/read are
negative about the product. We wasted many hours trying to get it to work on
version 6.5 when it first came out. 6.5.3 is supposed to fix some issues, I
don't want to go down the LU road again without the possibility of success!
Anyone have it up and running successfully?
There are many caveats to getting this going properly and some are severe
enough that we're not able to implement it for us for some of the clients. We
had a lengthy discussion with the developers of the client deployment packages
at the last Symantec Tech Day in December so they're aware of the restrictions.
One of the biggest gotchas for us is that it's pretty much unusable in a
cluster environment. One of its checks is to see if the client is actually
doing a backup before it tries to upgrade itself. If you have multiple names
for your hosts - and this is the case for close to 100% of the cluster users -
this check can fail and your backup and/or upgrade job will fail.
In general, the NetBackup support for cluster clients is pretty poor. Yeah,
Symantec has hacked "support" in there but it's simply the case of not breaking
in a cluster but that's about it. LiveUpdate is just another example of where
Symantec's cluster "support" fails to solve the problems properly.
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
[email protected]<mailto:[email protected]>
_______________________________________________
Veritas-bu maillist - [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
