03-04-2015 07:16 PM
We (CenturyLink/Qwest Communication) just purchase a NetBackup 5230 Appliance and we were told that we would be able to backup our FreeBSD systems. NetBackup Client does work on FreeBSD 10 more specifically FreeBSD 10.1.
Guadalupe
Solved! Go to Solution.
03-04-2015 08:07 PM
03-04-2015 08:07 PM
03-05-2015 04:33 AM
Know that some earlier version of FreeBSD required certain libraries to be installed for the Netbackup Client to work.
Think it was something like the compat libraries, pretty sure there was a technote about it
03-05-2015 04:53 AM
Yep. The TN is listed in the OS CL but has been removed in the meantime.
Info was for older versions of FreeBSD.
03-05-2015 10:47 AM
The idea of using backward comptabile libraries is probably still valid ...
03-05-2015 10:57 AM
Guess this could be solved by installing compat9x libraries, as FreeBSD 9.3 is supported by Netbackup 7.6.0.3
Would use ldd on bpcd and pbx_exchange to see which libraries was expected/needed
04-15-2015 08:54 AM
Hi,
I've got the same problem.
Originally, I installed 7.6.0.1 on a (blank) FreeBSD 8 VM and justed packed anything the installer (and the patch-installer) installed in a .tar.gz.
It was only 200-something GB then, as opposed to multiple GBs for the "raw" download...
This works under FreeBSD 10, but it does not work with FreeBSD 10.1.
I only realized this just this week, after upgrading the first non-virtual system to 10.1.
When I ktrace the above command, I get this:
50726 vnetd RET read 11/0xb
50726 vnetd CALL close(0x3)
50726 vnetd RET close 0
50726 vnetd CALL stat(0xffffb310,0xffffb160)
50726 vnetd NAMI "/usr/openv/var/host_cache/1ff"
50726 vnetd STRU struct stat {dev=111, ino=38, mode=040755, nlink=2, uid=0, gid=2, rdev=5105, atime=1429096293, stime=1429106245, ctime=1429106245, birthtime=1429094123, size=512, blksize=32768, blocks=8, flags=0x0 }
50726 vnetd RET stat 0
50726 vnetd CALL open(0xffffbb70,0<O_RDONLY>,<unused>0x1b6)
50726 vnetd NAMI "/usr/openv/var/host_cache/1ff/ffffffff+vnetd,1,1,0,1,0+.txt"
50726 vnetd RET open 3
50726 vnetd CALL fstat(0x3,0xffffac70)
50726 vnetd STRU struct stat {dev=111, ino=42, mode=0100644, nlink=1, uid=0, gid=2, rdev=5109, atime=1429108927, stime=1429106245, ctime=1429106245, birthtime=1429106245, size=396, blksize=32768, blocks=8, flags=0x0 }
50726 vnetd RET fstat 0
50726 vnetd CALL read(0x3,0x8062000,0x8000)
50726 vnetd GIO fd 3 read 396 bytes
",vnetd,1,1,0,1,0
1429106245
0
1
ADDRINFO_NEXT
BASICS=1;1;6;1;_NULL_CANONNAME_
SOCKADDR=28;28;1c1c359c000000000000000000000000000000000000000000000000
CACHED_FLAGS=0;0;0;0;0;0;-2;-2;-2;-2;-2
HOST_UUIDS=0;0
UUID_HOSTS=0;0
ADDRINFO_NEXT
BASICS=1;1;6;1;_NULL_CANONNAME_
SOCKADDR=2;16;1002359c000000000000000000000000
CACHED_FLAGS=0;0;0;0;0;0;-2;-2;-2;-2;-2
HOST_UUIDS=0;0
UUID_HOSTS=0;0
ADDRINFO_END
"
50726 vnetd RET read 396/0x18c
50726 vnetd CALL close(0x3)
50726 vnetd RET close 0
50726 vnetd CALL gettimeofday(0xffffbf08,0)
50726 vnetd RET gettimeofday 0
50726 vnetd CALL geteuid
50726 vnetd RET geteuid 0
50726 vnetd CALL umask(0<><invalid>0)
50726 vnetd RET umask 18/0x12
50726 vnetd CALL open(0x80507c8,0x202<O_RDWR|O_CREAT>,0x180<S_IRUSR|S_IWUSR>)
50726 vnetd NAMI "/usr/openv/var/vnetd/vnetd.lock"
50726 vnetd RET open 3
50726 vnetd CALL __sysctl(0xffffc078,0x2,0xffffc070,0xffffc074,0,0)
50726 vnetd SCTL "kern.osreldate"
50726 vnetd RET __sysctl 0
50726 vnetd CALL fcntl(0x3,F_OSETLK,0xffffc0f0)
50726 vnetd RET fcntl -1 errno 14 Bad address
50726 vnetd CALL close(0x3)
50726 vnetd RET close 0
50726 vnetd CALL umask(0x12<S_IWGRP|S_IWOTH>)
50726 vnetd RET umask 0
50726 vnetd CALL gettimeofday(0xffffacd0,0xffffacd8)
50726 vnetd RET gettimeofday 0
50726 vnetd CALL issetugid
50726 vnetd RET issetugid 0
50726 vnetd CALL open(0xffffa7a0,0<O_RDONLY>,<unused>0)
50726 vnetd NAMI "/usr/share/zoneinfo/Europe/Zurich"
To me, it looks a bit as if the software checks kern.osreldate and then does something wrong according to it. But I may be wrong because I just realized that I have a newly installed server with FreeBSD 10.1 that I can backup successfully.
But it runs my "re-packed" version of 7.6.0.1
All servers are AMD64 only.
Technically, there should not be any reason for a software to run on 10.0 but not on 10.1. Both are identical in terms of the ABI.
Lastly, the only supported version of FreeBSD currently are:
- 10.1
- 9.3
- 8.4
As such, I always found it strange that Symantec supports mostly outdated releases.
04-15-2015 11:24 PM
Curious about what ldd of vnetd on the failing machine shows
04-16-2015 04:49 AM
Only up to FreeBSD 9.3 is supported as NBU Client.
See OS SCL: http://www.symantec.com/docs/TECH76648
Unfortunately nothing that can be done about compatibility in a Community Forum.
Reach out to Symantec Product Management via your local reseller or Symantec office.
04-16-2015 04:54 AM
The interesting thing is I re-installed 7.6.0.4 in a FreeBSD 9.3 VM - and get the exact same error from trying to run vnetd with -standalone -debug.
My backup-team will have to open a support request on behalf of me...
ldd /usr/openv/netbackup/bin/vnetd
/usr/openv/netbackup/bin/vnetd:
libnbclientST.so => /usr/openv/lib/libnbclientST.so (0x28072000)
libnbbaseST.so => /usr/openv/lib/libnbbaseST.so (0x280c9000)
libvrtsLogReadST.so.3 => /usr/openv/lib/libvrtsLogReadST.so.3 (0x28209000)
libvxexticuST.so.3 => /usr/openv/lib/libvxexticuST.so.3 (0x28218000)
libvrtsLogFormatMsgST.so.3 => /usr/openv/lib/libvrtsLogFormatMsgST.so.3 (0x2821e000)
libvrtsLogSLST.so.3 => /usr/openv/lib/libvrtsLogSLST.so.3 (0x2822f000)
libvxulST.so.3 => /usr/openv/lib/libvxulST.so.3 (0x28236000)
libvxlisST.so.3 => /usr/openv/lib/libvxlisST.so.3 (0x28254000)
libvxicuioST.so.6 => /usr/openv/lib/libvxicuioST.so.6 (0x2825b000)
libvxicui18nST.so.6 => /usr/openv/lib/libvxicui18nST.so.6 (0x28264000)
libvxicuucST.so.6 => /usr/openv/lib/libvxicuucST.so.6 (0x2846d000)
libvxicudataST.so.6 => /usr/openv/lib/libvxicudataST.so.6 (0x285b9000)
libvxcPBXST.so => /usr/openv/lib/libvxcPBXST.so (0x2972a000)
libvxACEST.so.6 => /usr/openv/lib/libvxACEST.so.6 (0x29731000)
libkvm.so.3 => /usr/local/lib32/compat/libkvm.so.3 (0x298b5000)
libstdc++.so.5 => /usr/local/lib32/compat/libstdc++.so.5 (0x298bd000)
libm.so.4 => /usr/local/lib32/compat/libm.so.4 (0x29992000)
libc.so.6 => /usr/local/lib32/compat/libc.so.6 (0x299a8000)
uname -iKmprsUv
FreeBSD 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 amd64 GENERIC 1001000 1001000
04-22-2015 04:41 AM
Interesting, had excepted some missing or wrong library versions showing up in the ldd on the 10.1 machine
EDIT found this note in the HCL
FreeBSD compat 6x-I386 libraries are required for support of FreeBSD 7.x and later.
So I was mistaking about the compat9x libraries