cancel
Showing results for 
Search instead for 
Did you mean: 

not able to start netbackup services ..need solution to start netbackup

symsonu
Level 6

 

 

I am trying to start netbackup and getting below error

 

# ./netbackup start
ld.so.1: vnetd: fatal: relocation error: file /nbu_data/netbackup/bin/vnetd: symbol log_set_pid: referenced symbol not found
Killed
NetBackup network daemon started.
ld.so.1: bpcd: fatal: relocation error: file /nbu_data/netbackup/bin/bpcd: symbol log_set_pid: referenced symbol not found
Killed
NetBackup client daemon started.
NetBackup SAN Client Fibre Transport daemon started.
Killed
Killed
NetBackup Database Server started.
ld.so.1: nbevtmgr: fatal: relocation error: file /nbu_data/netbackup/bin/nbevtmgr: symbol __1cINBLoggerMsetVerbosity6Mi_v_: referenced symbol not found
Killed
NetBackup Event Manager started.
ld.so.1: nbaudit: fatal: relocation error: file /nbu_data/netbackup/bin/nbaudit: symbol NB_read_master_config: referenced symbol not found
Killed
NetBackup Audit Manager started.
NetBackup Deduplication Manager started.
NetBackup Deduplication Engine started.
ld.so.1: nbemm: fatal: relocation error: file /nbu_data/netbackup/bin/nbemm: symbol __1cHVeritasDDalLVxDBMS_ConfPReadVxDBMS_Conf6Mb_i_: referenced symbol not found
Killed
NetBackup Enterprise Media Manager started.
NetBackup Resource Broker started.
Media Manager daemons started.
Killed
NetBackup request daemon started.
ld.so.1: bpcompatd: fatal: relocation error: file /nbu_data/netbackup/bin/bpcompatd: symbol vnet_enable_resilient_socket: referenced symbol not found
Killed
NetBackup compatibility daemon started.
ld.so.1: nbjm: fatal: relocation error: file /nbu_data/netbackup/bin/nbjm: symbol __1cISymantecJNetBackupDNcfGXmlStrTDEFAULT_XML_VERSION_: referenced symbol not found
Killed
NetBackup Job Manager started.
ld.so.1: nbpem: fatal: relocation error: file /nbu_data/netbackup/bin/nbpem: symbol restore_errmsgstr: referenced symbol not found
Killed
NetBackup Policy Execution Manager started.
ld.so.1: nbstserv: fatal: relocation error: file /nbu_data/netbackup/bin/nbstserv: symbol NB_read_master_config: referenced symbol not found
Killed
NetBackup Storage Lifecycle Manager started.
ld.so.1: nbrmms: fatal: libVimpmgrcomm.so: open failed: No such file or directory
Killed
NetBackup Remote Monitoring Management System started.
NetBackup Key Management daemon started.
NetBackup Service Layer started.
NetBackup Agent Request Server started.

 

can somone please help ?

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

Start again - install NBU 7.5 plus what ever patch and restore the most recent catalog you have as long as it was also a 7.5 one

View solution in original post

19 REPLIES 19

pri3006
Level 4
Certified

Is this a new install? Seems like the installation may have gone corrupt. Have you tried a clean re-install, using a fresh set of downloaded binaries?

Mark_Solutions
Level 6
Partner Accredited Certified

Sounds like a linux issue - where was it installed?  /nbu_data/netbackup/bin/ doesn't sound like a normal location for the installation as it would link as /usr/openv/netbackup nromally

We really need to know a lot more about your system:

NBU version / patch level

Has it ever work

O/S and version

Tell us as much as you can

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I have the same question.... 

Is this a new install that has never worked before?

Which Solaris version?
And architecture?  Sparc or x86?

Sure the right binaries were used to install NBU? Sparc/x86?
Which NBU 7.5 patch level?

Please show us output of these commands:

  • uname -a
  • file /nbu_data/netbackup/bin/vnetd
  • cat /nbu_data/netbackup/version
  • cat /nbu_data/netbackup/bin/version

 

symsonu
Level 6

 

Hello ,

Actually I upgraded the system couple of moths back to 7.5 and it was working fine...

and now the system was corrupted and we lost the directories under /usr/openv.

Luckily I have a tar of /usr/openv and I extracted it  .....

there is a space constraint under / so i moved netbackup to other filesystem /nbu_data and made the link

Now, when i try to restart nbu services , getting the error

 

 

# cd /usr/openv

# ls -l netbackup
lrwxrwxrwx   1 root     root          19 May 12 16:24 netbackup -> /nbu_data/netbackup
# cd netbackup
# ls
NET_BUFFER_SZ                 help                          remote_versions
baremetal                     logs                          sec
bin                           nblog.conf                    vault
bp.conf                       nblog.conf.02-19-14.17:16:04  version
client                        nblog.conf.03-29-12.19:46:58  version_master
db                            nblog.conf.template           vfm.conf
dbext                         nblu.conf.template            vfm_master.conf
ext                           nbsvcmon.conf
#

 

 

# file /nbu_data/netbackup/bin/vnetd
/nbu_data/netbackup/bin/vnetd:  ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not stripped
# cat /nbu_data/netbackup/version
HARDWARE SOLARIS
VERSION NetBackup 7.5.0.4
RELEASEDATE Sun Sep 16 09:06:39 CDT 2012
BUILDNUMBER 20120916
# cat /nbu_data/netbackup/bin/version
NetBackup-Solaris10 7.5.0.4
#

 

symsonu
Level 6

# uname -a
SunOS hydmas1o-bck 5.10 Generic_144488-17 sun4u sparc SUNW,SPARC-Enterprise
#
 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Hopefully you have a recent catalog backup?

Seems you only linked the netbackup part of the installation.
What about other directories under openv such as volmgr? db? var? etc...
What about pbx? (Installed in /opt)

A tar of /usr/openv is only useful if NBU was completely shutdown at the time.
But we know that your NBU installation was previously in /opt. Not in /usr. 
https://www-secure.symantec.com/connect/forums/netbackup-asa-db-issue

Best to remove this installation, do a fresh installation to exact same installation path, patch to previous level (7.5.0.4), then recover catalogs.

Mark_Solutions
Level 6
Partner Accredited Certified

Sounds like something is wrong with the link to me - not great with unix but that was my first suspicion when i saw it - i would have expected if linked it would not give that path in the error .. or you cab file has not extracted with all required permissions on the file to let it actually run

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

One more thing - please tell us more about this:

... and now the system was corrupted ....

 

It actually seems that you need to reinstall more than just NBU.
The  ld.so.1 errors seem to point to OS corruption.

Complete OS re-install followed by NBU install and catalog recovery will probably be the correct steps that need to be followed...

symsonu
Level 6

Hello Marianne

 

all other directories like openv , volmgr   are there under /usr/openv

only netbackup is been made as link  as shown below


# cd /usr/openv
# ls
NB-Java.tar.gz
db
java
kms
lib
logs
man
msg
netbackup
openv
pack
pack.6.5.5
pdde
pddeserver.tar.gz
regid.1992-11.com.symantec,Enterprise_netbackup-7.0.0.0_1.swidtag
regid.1992-11.com.symantec,Enterprise_netbackup-7.0.1.0_1.swidtag
resources
share
swidtag.xml
tmp
var
volmgr
#

/opt/openv is actually a link to /usr/openv

# ls -ld /opt/openv
lrwxrwxrwx   1 root     root          10 Mar 29  2012 /opt/openv -> /usr/openv

Mark_Solutions
Level 6
Partner Accredited Certified

When was you tar from?

You say you recently upgraded to 7.5 but the file system now has:

regid.1992-11.com.symantec,Enterprise_netbackup-7.0.0.0_1.swidtag

Looks like that is still 7.0.....

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Mmmm.... Not good.

Have a look - you have openv inside of openv:

# cd /usr/openv
# ls
...
netbackup

openv
pack
...

 

Best to start from scratch and recover catalog.

symsonu
Level 6

I used the netbackup folder that was there in the tar....

and I can start the netbackup services ......

however  I can not see backups for last two months ....be cause the tar was taken two months back.

should I restore catalog and will I be geeting backups for last two months back..

 

 

 

Mark_Solutions
Level 6
Partner Accredited Certified

Start again - install NBU 7.5 plus what ever patch and restore the most recent catalog you have as long as it was also a 7.5 one

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, how did you get past the 'ld.so.1' errors?

... be cause the tar was taken two months back. 

Then you will only see backups up to 2 months back.

As per previous advice - start over.
Perform clean NBU install to same location, patch, then recover from most recent catalog backup.


 

 

symsonu
Level 6

can we add SYMCnetbp/ VRTSnetbp package manually?

 

 Processing Netbackup 7.5 Enterprise Server MP4
****************************************************
 
<- [VRTSnetbp SYMCnetbp] not installed [ok].
<- So we don't need NB [ok]
 

upgrading to 7.5 is skipping as there is no 7.1 package

 

trying to add pkgadd of SYMCnetbp 7.5

got erro

Starting with NetBackup 7.5, SYMCnetbp is no longer a

standalone package that can be installed via pkgadd directly.

Therefore, the installation of SYMCnetbp must occur via

the install script provided on the media

 

===========

 

is it possible to add 7.0.1 version of SYMCnetbp and then upgrading ?

 

any workaround?

 

 

 

Mark_Solutions
Level 6
Partner Accredited Certified

Just run the ./install rather than try and package add them

symsonu
Level 6

can you please tell complete path ?

 

Mark_Solutions
Level 6
Partner Accredited Certified

I was assuming that you would be starting again as advised and doing a fresh install - in that case downlaod the 7.5 software and run the ./install script to install it.

Then patch to the same version as it was before the crash and do a catalog restore

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You can find 'install' in the root of installation media (either dvd or download from FileConnect).

So, again.... 

As per previous advice - start over.
Perform clean NBU install to same location, patch, then recover from most recent catalog backup.