Video Screencast Help

Loss of netbackup databases, services like bprd, bpdbm disappeared from master, and we are not able to open the GUI to monitor the console, or to restore the data. Getting error " cannot connect on socket".

Created: 04 Dec 2012 • Updated: 10 Dec 2012 | 6 comments
This issue has been solved. See solution.

Hello Gurus,

Master Server Version 7.1.

We are facing issue on NBU Master Server  due to loss of netbackup databases, services like bprd, bpdbm disappeared from master, and we are not able to open the GUI to monitor the console, or to restore the data. Getting error " cannot connect on socket".

Issue happens because there were four disks pieces that were used to create the volume used by netbackup databases.One of those striped non-mirrored volume is affected by the c2t1 disk failure. Disks is now replaced.

Now need to know what steps we should perform to resolve the issue......

 

 

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

2013's picture

Processes running on Master Server:

 

NB Processes
------------
    root 26109     1   0 12:53:49 ?           0:01 /usr/openv/netbackup/bin/vnetd -standalone
    root 26112     1   0 12:53:50 ?           0:00 /usr/openv/netbackup/bin/bpcd -standalone
    root 26403     1   0 12:54:18 ?           0:01 /usr/openv/netbackup/bin/nbsl
    root 26181     1   0 12:53:58 ?           0:01 /usr/openv/netbackup/bin/nbaudit
    root 26168     1   0 12:53:53 ?           0:34 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
    root 26381     1   0 12:54:15 ?           0:03 /usr/openv/netbackup/bin/nbrmms
    root 26319 26315   0 12:54:10 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbjm
    root 26329     1   0 12:54:13 ?           0:08 /usr/openv/netbackup/bin/nbstserv
    root 26315     1   0 12:54:09 ?           0:04 /usr/openv/netbackup/bin/nbjm
    root 22553 26310   0 13:30:17 ?           0:00 /usr/openv/netbackup/bin/bpcompatd
    root 26310     1   0 12:54:08 ?           0:01 /usr/openv/netbackup/bin/bpcompatd
    root 26178     1   0 12:53:56 ?           0:01 /usr/openv/netbackup/bin/nbevtmgr
    root 26271     1   0 12:54:06 ?           0:01 /usr/openv/netbackup/bin/nbrb
    root 26407     1   0 12:54:20 ?           0:01 /usr/openv/netbackup/bin/nbars
    root 26268     1   0 12:54:04 ?           0:08 /usr/openv/netbackup/bin/nbemm
    root 26474     1   0 12:54:24 ?           0:01 /usr/openv/netbackup/bin/nbsvcmon
    root 22557 26310   0 13:30:21 ?           0:00 /usr/openv/netbackup/bin/bpcompatd

MM Processes
------------
    root 26288     1   0 12:54:07 ?           0:01 vmd -v
    root 26332 26282   0 12:54:13 ?           0:01 avrd -v
    root 26325 26282   0 12:54:11 ?           0:01 tldd -v
    root 26384     1   0 12:54:15 ?           0:00 tldcd -v
    root 26282     1   0 12:54:06 ?           0:00 /usr/openv/volmgr/bin/ltid
 

Marianne's picture

Create bprd and bpdbm folders under /usr/openv/netbackup/logs

Start bprd as follows:

/usr/openv/netbackup/bin/initbprd

This should attempt to start bprd as well as bpdbm

If they 'die' again, please see if any logs were created in above 2 folders.
If so, copy them to text files that reflect process names (e.g. bprd.txt) and post as File attachments.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

I do not know what was on the disk that was lost, but clearly it was part of NBU.

Is this fixable, no idea - it will take possible a lot of investigation to find out, and then time to fix, and you are still left not knowing if someting is broken that you don;t find out about until next week.

Personally, I would't mess about with this, reinstall NBU (about an hour) and then using the catalog DR file, recover the catalog but do not delete the files in /usr/openv/netbackup/db/images (copy them somewhere safe).

Then, once back up, log a call with Symantec to run NBCC, to see what backups that ran after the last catalog backup, but before the crash, can be saved.

I would estimate (in my experience) that the majority of cases like this end up reinstalling, sometimes after several days of investigation.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
Marianne's picture

Please mark Martin's (mph999) post as Solution?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links