NetBackup-OEBU-RedHat2.6 6.5.1

[skt_skt]

Any one have "NetBackup-OEBU-RedHat2.6 6.5.1" working well with below verison.

[root@tneld52n share]# uname -a
Linux tneld52n 2.6.18-53.1.13.el5 #1 SMP Mon Feb 11 13:27:27 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
[root@tneld52n share]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.1 (Tikanga)
[root@tneld52n share]# getconf LONG_BIT
64

I have the following error while upgrading

This package will install NetBackup client 6.5.
/root/nbkp/nbu6.5/HP/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat2.6/tar: error while loading shared libraries: libacl.so.1: cannot open shared object file: No such file or directory
tar failed unpacking client_bin.tar.Z on tneld52n.
Cannot complete the client install.

A failure was detected running /root/nbkp/nbu6.5/HP/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat2.6/cp_to_client tnbkms1 tneld52n

[Jeeshan]

check you have installed libacl rpm in your machine.

find here

www.rpmfind.net

[Steven E. Protter · Accepted solution]

Shalom,

This appears to be a 64 bit encryption library.

http://afs.caspur.it/afs/italia/project/mirrors/suse/update/9.2/patches/coreutils-52729

Makes sure that the version of Veritas you are using is rated and certified to run on 64 bit Linux.

I suspect, based on this link that the missing package is libacl.

http://osdir.com/ml/linux.redhat.fedora.maintainers/2006-05/msg00062.html

You may want to update this system to REHL 5.2 if that version of the OS is certified by Veritas.

SEP

[skt_skt]

Here is the support matrix.

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/279048.pdf

5.1 is not in the list at all?
But i see 5.0 listed as 32bit(x86). Is that right?

[Matti_Kurkela]

RHEL 5.1 is the same thing as RHEL 5(.0) Update 1, so anything that's supported on RHEL 5.0 should be supported on RHEL 5.1 too.

But as Santhosh noticed, it looks like the NetBackup-OEBU component might not have native x86_64 support in your version yet. This should not be a problem, unless you need to backup multi-terabyte files: even the 32bit version can handle rather large files just fine.

You'll just need to remember that a x86_64 system may require two sets of library packages: one set for the 64-bit programs, and another for the legacy 32-bit programs. As the libacl.so.1 is a very basic library in RHEL 5.1, I don't think it is possible to install a system without it.

What the NetBackup-OEBU module is missing is probably the _32-bit_ version of the libacl.so.1 library. Check the list of available packages using the standard package management tools: there should be two versions of the libacl package available for your system. One with a x86_64 tag in its name is probably already installed. The other, with a tag like i386 or i686 might be not installed yet: if so, install it.

To verify whether any executable is 32-bit or 64-bit, run the "file" command on it.
For example, run "file /root/nbkp/nbu6.5/HP/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat2.6/tar". If it says something like "ELF 32-bit LSB executable", you'll know this is a 32-bit application and requires 32-bit versions of all the libraries it is going to use.

To see which libraries a given executable needs, run the "ldd" command on it. The error message that appears when trying to run the executable will reveal only the _first_ missing library. If two or more libraries are missing, installing just the one library mentioned in the error message will only reward you with a different error message when trying to run the executable again.

MK

[skt_skt]

have you done similar thing practiucally??

[Matti_Kurkela]

As a matter of fact, yes.

When we got our first x86_64 systems, even the basic Veritas NetBackup client did not yet have native x86_64 support. Our backup systems admin checked with Veritas and got back an answer saying essentially "running the 32-bit version on x86_64 systems works just fine if the 32-bit versions of all the required libraries are installed".

Essentially the same thing happened with the BMC Patrol monitoring agent.

We soon learned three things:
1.) In a x86_64 system, it usually helps to install both 64-bit and 32-bit versions of *all* library packages available in the distribution, if the system must run legacy 32-bit software.

2.) The use of "file" and "ldd" commands to determine whether an executable or a library is 64-bit or 32-bit, and what other libraries it needs.

3.) If you don't do 1) at the OS installation time, you'll need to be able to do 2) when trying to install any 32-bit software, or any software that does not explicitly say it's a 64-bit x86_64 version.

All operating systems I've encountered have required the sysadmin to learn something new when transitioning from 32-bit to 64-bit: this was true in HP-UX and Solaris, and it still is true with Linux and Windows.

MK