cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

problem installing NetBackup 6.5.3 client on Red Hat 4.8

Hi,

I have a very weird problem and I'm hoping somebody can help me because I have pretty limited experience with Netbackup.

Here's the scenerio: I have a Red Hat Linux box that I'd like to backup in my Netbackup 6.5.3 environment.  So I grabbed NetBackup_6.5_CLIENTS2.tar.gz, unpacked it and ran the install script.  Here's the problem.

The install script runs, unpacks some files and puts them in the usual spot (/usr/openv) but that's it.  It doesn't create anything in /etc/xinetd.d so they agents never start.  Consequently nothing's listen on 13782 and my server can't connect.


But the script runs fine - there's no error.

So pulling through the install script (I'm better at scripting than I am at netbackup so I went this route) I see that this install script calls 2 other scripts.

First it calls ${MY_CD_PATH}/NBClients/catalog/anb/client.inst ${Trace_File} 

and then it can call /usr/openv/netbackup/bin/install_bp

Now it looks like the install_bp script is what does the real meat of the installation - it creates the services at least.  However that script never runs.  It never runs because it's in an if block that looks like this:

if [ -f ${TMPDIR}/do_install_bp.$$.status ]

So I go hunting for what creates that file and you find a block higher up that looks like this:

if [ "${client_CD}" = "no" ]

so I go looking for what controls that and I find another if block that looks like this:

if [ ! -d "${MY_CD_PATH}/NBClients" ]

So - what we see if, if I have a folder in my install directory named NBClient then it doesn't install the services and I do have that folder so my services don't get installed.  I can follow that

What doesn't make sense is the logic behind the scenes.  The reason I have this folder is because the tarball put it there - I didn't do that.  So the install process is creating a folder that ruins the install process.

 

I'd be happy to run install_bp by hand but i'm not sure what else I might be missing - who knows what could happen - recursive rm as part of the cleanup?  Who knows.  I'd rather not risk it and I'd rather have this install make sense.

 

So has anybody had this problem?  It looks to me like this script would never ever work but maybe I'm missing something.

 

Thanks in advance for any help.

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

I found the problem - the

I found the problem - the install script runs a check to see if the machine is a server or not.  It's just an if [-f] statement - so it's only checking for the existance of a file, not if the service is running or anything.

 

The first time through the install somebody used the wrong software and installed the server files.  They weren't setup to run and they weren't in xinetd or using ports or anything but the files were there and so I failed that check.

Because I failed that check it assumed I wanted to install the client software for  the purpose of remote installation to other clients (which makes sense if this had actually been a server)

Once I found that line in the install script and saw what it was doing I completely removed the openv folder and did a fresh install which worked as expected.

View solution in original post

7 Replies
Highlighted

I guess install_bp script

I guess install_bp script will run only if you are installing the Netbackup Server.

Please check if xinetd installed and running?

And also can you please paste install_trace ( should be located in the /tmp directory) log for the specific intallation.

Highlighted

Ok that could be right

Ok that could be right actually.  The script to install the server component also contains similar logic for calling the same script.  It seems weird to me that the client would even care to check for stuff like that but perhaps they reused their code - which wouldn't be that unusual. 

 

So I guess I'm stumped - I don't see anything in the script that would do things like install services in xinetd so I'm not sure how this would work.  Here's a copy of an install log.  As you can see it's terribly boring but it doesn't end in error.  It just shows a lot of files getting unpacked and that's it - then it ends.  So it didn't give me anything to go on.  Maybe you'll see something I didn't.

 

 Symantec Installation Script
Copyright 1993 - 2007 Symantec Corporation, All Rights Reserved.

        Installing NetBackup Client Software

 NOTE:  To install NetBackup Server software, insert the appropriate
        NetBackup Server cdrom.

Do you wish to continue? [y,n] (y) y

        Choose the Platform Client Options you wish to install.

        Platform Client Options
        -----------------------
         1. Linux
         2. Linux-IA64
         3. MACINTOSH
         4. All UNIX client platforms
         q. quit selecting

        Enter Choice(s) [1 - 4] 1

 Linux

        Enter Choice(s) [1 - 4] q

        You have chosen to install:

        Linux

Is this the list you wish to use? [y,n] (y) y

Reading client binaries for /usr/openv/netbackup/client/Linux
Linux/
Linux/RedHat2.6/
Linux/RedHat2.6/client_bin.tar.Z
Linux/RedHat2.6/ftp_to_client
Linux/RedHat2.6/install_client
Linux/RedHat2.6/fsanalyze
Linux/RedHat2.6/ssh_to_client
Linux/RedHat2.6/JRE.tar.Z
Linux/RedHat2.6/cp_to_client
Linux/RedHat2.6/tar
Linux/RedHat2.6/client_config
Linux/RedHat2.6/extract_java
Linux/RedHat2.6/.sizes
Linux/RedHat2.6/version
Linux/RedHat2.6/nbj.conf
Linux/RedHat2.6/move_libs
Linux/RedHat2.6/sftp_to_client
Linux/IBMzSeriesLinux2.4.21/
Linux/IBMzSeriesLinux2.4.21/client_bin.tar.Z
Linux/IBMzSeriesLinux2.4.21/ftp_to_client
Linux/IBMzSeriesLinux2.4.21/install_client
Linux/IBMzSeriesLinux2.4.21/ssh_to_client
Linux/IBMzSeriesLinux2.4.21/cp_to_client
Linux/IBMzSeriesLinux2.4.21/tar
Linux/IBMzSeriesLinux2.4.21/client_config
Linux/IBMzSeriesLinux2.4.21/extract_java
Linux/IBMzSeriesLinux2.4.21/.sizes
Linux/IBMzSeriesLinux2.4.21/version
Linux/IBMzSeriesLinux2.4.21/move_libs
Linux/IBMzSeriesLinux2.4.21/sftp_to_client
Linux/IBMpSeriesRedHat2.6/
Linux/IBMpSeriesRedHat2.6/client_bin.tar.Z
Linux/IBMpSeriesRedHat2.6/ftp_to_client
Linux/IBMpSeriesRedHat2.6/install_client
Linux/IBMpSeriesRedHat2.6/ssh_to_client
Linux/IBMpSeriesRedHat2.6/cp_to_client
Linux/IBMpSeriesRedHat2.6/tar
Linux/IBMpSeriesRedHat2.6/client_config
Linux/IBMpSeriesRedHat2.6/extract_java
Linux/IBMpSeriesRedHat2.6/.sizes
Linux/IBMpSeriesRedHat2.6/version
Linux/IBMpSeriesRedHat2.6/move_libs
Linux/IBMpSeriesRedHat2.6/sftp_to_client
Linux/IBMzSeriesSuSE2.6/
Linux/IBMzSeriesSuSE2.6/client_bin.tar.Z
Linux/IBMzSeriesSuSE2.6/ftp_to_client
Linux/IBMzSeriesSuSE2.6/install_client
Linux/IBMzSeriesSuSE2.6/ssh_to_client
Linux/IBMzSeriesSuSE2.6/cp_to_client
Linux/IBMzSeriesSuSE2.6/tar
Linux/IBMzSeriesSuSE2.6/client_config
Linux/IBMzSeriesSuSE2.6/extract_java
Linux/IBMzSeriesSuSE2.6/.sizes
Linux/IBMzSeriesSuSE2.6/version
Linux/IBMzSeriesSuSE2.6/move_libs
Linux/IBMzSeriesSuSE2.6/sftp_to_client
Linux/SuSE2.6/
Linux/SuSE2.6/client_bin.tar.Z
Linux/SuSE2.6/ftp_to_client
Linux/SuSE2.6/install_client
Linux/SuSE2.6/fsanalyze
Linux/SuSE2.6/ssh_to_client
Linux/SuSE2.6/JRE.tar.Z
Linux/SuSE2.6/cp_to_client
Linux/SuSE2.6/tar
Linux/SuSE2.6/client_config
Linux/SuSE2.6/extract_java
Linux/SuSE2.6/.sizes
Linux/SuSE2.6/version
Linux/SuSE2.6/nbj.conf
Linux/SuSE2.6/move_libs
Linux/SuSE2.6/sftp_to_client
Linux/IBMpSeriesSuSE2.6/
Linux/IBMpSeriesSuSE2.6/client_bin.tar.Z
Linux/IBMpSeriesSuSE2.6/ftp_to_client
Linux/IBMpSeriesSuSE2.6/install_client
Linux/IBMpSeriesSuSE2.6/ssh_to_client
Linux/IBMpSeriesSuSE2.6/cp_to_client
Linux/IBMpSeriesSuSE2.6/tar
Linux/IBMpSeriesSuSE2.6/client_config
Linux/IBMpSeriesSuSE2.6/extract_java
Linux/IBMpSeriesSuSE2.6/.sizes
Linux/IBMpSeriesSuSE2.6/version
Linux/IBMpSeriesSuSE2.6/move_libs
Linux/IBMpSeriesSuSE2.6/sftp_to_client
Linux/RedHat2.4/
Linux/RedHat2.4/client_bin.tar.Z
Linux/RedHat2.4/ftp_to_client
Linux/RedHat2.4/install_client
Linux/RedHat2.4/fsanalyze
Linux/RedHat2.4/ssh_to_client
Linux/RedHat2.4/JRE.tar.Z
Linux/RedHat2.4/cp_to_client
Linux/RedHat2.4/tar
Linux/RedHat2.4/client_config
Linux/RedHat2.4/extract_java
Linux/RedHat2.4/.sizes
Linux/RedHat2.4/version
Linux/RedHat2.4/nbj.conf
Linux/RedHat2.4/move_libs
Linux/RedHat2.4/sftp_to_client
Linux/IBMzSeriesRedHat2.6/
Linux/IBMzSeriesRedHat2.6/client_bin.tar.Z
Linux/IBMzSeriesRedHat2.6/ftp_to_client
Linux/IBMzSeriesRedHat2.6/install_client
Linux/IBMzSeriesRedHat2.6/ssh_to_client
Linux/IBMzSeriesRedHat2.6/cp_to_client
Linux/IBMzSeriesRedHat2.6/tar
Linux/IBMzSeriesRedHat2.6/client_config
Linux/IBMzSeriesRedHat2.6/extract_java
Linux/IBMzSeriesRedHat2.6/.sizes
Linux/IBMzSeriesRedHat2.6/version
Linux/IBMzSeriesRedHat2.6/move_libs
Linux/IBMzSeriesRedHat2.6/sftp_to_client

LiveUpdate is not installed, skipping registration step... 

 

And that's it.  So I'm not sure where to go from here.

Highlighted

Try this

Getting a Linux box to work with netbackup.

If you cannot get the master to connect to the client try this command

[root]# telnet localhost bpcd

Trying 127.0.0.1...

Connected to localhost.localdomain (127.0.0.1).

Escape character is '^]'.

bpcd: error while loading shared libraries: /usr/openv/lib/libnbmangle.so: cannot restore segment prot after reloc: Permission denied

Connection closed by foreign host.

 

If you get that error

Do these commands

These are the commands to pass to SELinux

chcon -t textrel_shlib_t /usr/openv/lib/libnbmangle.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBXCommon.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBX.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBXVxSS.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxVxSSIOP.so
chcon -t textrel_shlib_t /usr/openv/lib/libnbservice.so

Run these commands as root then restart xinetd
/etc/init.d/xinetd stop
/etc/init.d/xinetd start

 

 

You should now be able to connect. 

Highlighted

No my problem is more basic

No my problem is more basic than that.  I can't connect because nothing is listening on port 13782.  Nothing is listening on port 13782 becasue the entries to start the services haven't been added to xinetd.d so they don't get started.

 

So the install is skipping the parts that perform those actions (and maybe lots of other actions - this is all I know to check)

Highlighted

What's your O/S?

NetBackup may be having trouble figuring out just which script it's supposed to be running.  Could you please post your /etc/redhat-release or a `uname -a` output?  I'm not sure what "4.8" means.

You're not trying to install a client on a 32-bit system, are you?  We dropped 32-bit client support for Linux in 7.x.

The "magic" should happen when client_config is called.  You can find it in /usr/openv/netbackup/client/Linux/(something) where (something) will be the correct corresponding client name depending on what you're running.

All this assumes you're running a version supported by NetBackup 7.x:
NetBackup (tm) 7 Operating System Compatibility List (Updated March 21, 2011)
 http://www.symantec.com/docs/TECH76648

See pages 40-41 and 51.

Highlighted
Accepted Solution!

I found the problem - the

I found the problem - the install script runs a check to see if the machine is a server or not.  It's just an if [-f] statement - so it's only checking for the existance of a file, not if the service is running or anything.

 

The first time through the install somebody used the wrong software and installed the server files.  They weren't setup to run and they weren't in xinetd or using ports or anything but the files were there and so I failed that check.

Because I failed that check it assumed I wanted to install the client software for  the purpose of remote installation to other clients (which makes sense if this had actually been a server)

Once I found that line in the install script and saw what it was doing I completely removed the openv folder and did a fresh install which worked as expected.

View solution in original post

Highlighted

By an amazing coincidence...

...I notice this TechNote was *very* recently published:

Red Hat Linux client software installs successfully but no services are listening after installation
 http://www.symantec.com/docs/TECH159342

(I promise I didn't see this yesterday!)