Netbackup 7.7.1 Installation

[motabost]

Good day

I am trying to install Netbackup 7.7.1 on a Linux Debian server from the "CLIENTS2" download, however I get the error below"

/software/netbackup7/NetBackup_7.7.1_CLIENTS2/NBClients/catalog/anb/client.inst: 540: [: Illegal number: 16-2-amd64

ERROR:   Detected an attempt to install incorrect platform and/or
         operating system and version client binaries on vctxmpro.

From the server:

root@vctxmpro:/software/netbackup7/NetBackup_7.7.1_CLIENTS2# cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Which version works on this OS?

Regards

[Marianne]

There must be something else in *release files that will tell you if this is 32-bit or 64-bit OS.

Only 64-bit is supported.

You can download OS SCL here: http://www.veritas.com/docs/000025229

[motabost]

Thank you Marianne

It is a 64 bit installation. What else can I look for?

root@vctxmpro:~# uname -a

Linux vctxmpro 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux

[Marianne]

It seems that there is something wrong with 'uname -a' output.

NetBackup is unhappy with this:

Illegal number: 16-2-amd64 

I cannot tell you what uname output is supposed to look like or what NBU is expecting.

Do you have another Debian server?
Can you compare uname output?

Hopefully someone else with Debian clients will see this and respond.

Or else log a Support call with Veritas.

[Matt123]

Problem

The output from `uname -r` should be of the format:

3.16.0-23-generic

Looking at the client.inst script, it parses the three dot separated digits with this code:

oslevel_f1=`uname -r | cut -f1 -d"."`
oslevel_f2=`uname -r | cut -f2 -d"."`
oslevel_f3=`uname -r | cut -f3 -d"." | cut -f1 -d"-"`

client.inst expects these variables to be numbers. Based on my above input (output from `uname -r`)

oslevel_f1 gets set to 3

oslevel_f2 gets set to 16

oslevel_f3 gets set to 0

In your case, f2 is getting set to 16-2-amd64 because your `uname -r` output is "3.16-2-amd64" and it is missing the second dot.

Untested Solution 1

If there is something you can fix to make the output of uname something like "3.16.0-2-amd64" then the script should work.

Untested Solution 2

You can edit /software/netbackup7/NetBackup_7.7.1_CLIENTS2/NBClients/catalog/anb/client.inst to get around this just for this system since the uname output is unexpected.

Make a backup of the file and then open the original in vi/vim and go to line 528.

Change where the oslevel_f variables are being set to the following code:

oslevel_f1=`uname -r | cut -f1 -d"."`
oslevel_f2=`uname -r | cut -f2 -d"."` | cut -f1 -d"-"`
oslevel_f3=0