03-09-2009 04:19 AM
1) Does it work?
2) Is it any good?
3) The examples in the manual are particularly weak, and the recent tech note for configuraing a Windows LU server is not at all secure. Does anyone have any tips on how to do it properly?
Master: Solaris 10, VCS, NBU ES v6.5.3.1
Medias x 4: Solaris 10, NBU ES v6.5.3.1
Medias x 2: Win2003 R2 SP2, NBU ES v6.5.3.1
03-09-2009 09:38 AM
"Does anyone have any tips on how to do it properly"
Download and install manually.
03-10-2009 01:45 AM
Use a web server if your environment does not allow the use of LAN protocol and using null shares. Check documentation on 6.5 release notes from page 115. ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/290198.pdf
03-10-2009 08:44 AM
...weak documentation. The knowledge base has already accepted that the referenced manual is at best weak, and that the documented example (in the manual) for a LAN based distribution is incorrect/incomplete - but the tech note's suggested (recommended) solution is to create a totally vulnerable/open server share, which is just plain ridiculous - I can't believe that Symantec (a supposedly security concious organization) would recommend this, it just beggars belief - and doesn't help me anyway because we don't install an SMB client on our Unix servers and thus cannot map to UNC paths on Windows servers.
I've read all the docs several times already. The best examples/notes so far have come from the web, and an http based solution seems to be the way to go.
Thanks though Bob - if anyone was going to have any useful feedback - it would be you.
The more I use this "glossy" new site, the more I realise that the design purpose is not to help users but to quickly roll real issues out of the public gaze.
09-25-2009 10:17 AM
09-26-2009 03:00 AM
09-28-2009 07:36 AM
09-28-2009 12:57 PM
10-20-2009 10:02 AM
Whenever a new client agent for NetBackup is installed, it is most important to make sure that the name within the ‘etc/hosts’ file for the client agent is exactly what is typed in during the installation. It is also imperative that the name typed in during the installation is the same name (case sensitive) that is shown by using the ‘hostname’ command.
Normally Windows is not case sensitive when resolving the hostname, but the NetBackup system requires that the case is correct for a number of key reasons:
1) Hostname is used by the NetBackup product to communicate with the client agent from the Master Server.
2) Clientname is used by the Backup, Restore and Archive program, allowing restores, to communicate with the NetBackup catalog and locate backup history
There are other reasons, but I am not an expert (ex as in was, spert as in drip under pressure)
Installation planning and process are the key to success with any product, not just NetBackup LiveUpdate...
Trevor