Highlighted

Restore NBDB Files (STATUS 54)

Hy gaise.

I need to restore my NBDB files to perform a recevory from staging.

I have an backup image like you can see at the attachements, but when I start the restore I have status 54 followed by status 25.

 

12/11/2013 22:15:16 - begin Restore

12/11/2013 22:15:16 - restoring image nbup1_1380857193

12/11/2013 22:15:17 - Info bpbrm(pid=5232) snbumasterp2.sp.local is the host to restore data

12/11/2013 22:15:17 - Info bpbrm(pid=5232) reading file list from client

12/11/2013 22:15:17 - Info bpbrm(pid=5232) listening for client connection

12/11/2013 22:16:17 - Error bpbrm(pid=5232) listen for client timeout during accept from data listen socket after 60 seconds

12/11/2013 22:16:22 - Info tar32(pid=0) done. status: 54: timed out connecting to client

12/11/2013 22:16:22 - Error bpbrm(pid=5232) client restore EXIT STATUS 54: timed out connecting to client

12/11/2013 22:31:17 - restored image nbup1_1380857193 - (cannot connect on socket(25)); restore time 00:16:01

12/11/2013 22:31:18 - end Restore; elapsed time: 00:16:02 Sybase policy restore error(2803)

 

Can you help me?

 

7 Replies
Highlighted

Hi Please find attached one

Hi Please find attached one doc fro the Indepth troubleshooting for the EC 25.

 

Hope it helps

Highlighted

To recover NBDB, follow the

To recover NBDB, follow the instructions described in NetBackup 7.5 Troubleshooting Guide. Recovery steps from staging files is in page 237.

http://www.symantec.com/docs/DOC5180

Highlighted

More info please... Are you

More info please...

Are you trying to restore to a different hostname?

restoring image nbup1_1380857193

 snbumasterp2.sp.local is the host to restore data

Why the different names?

NBDB can only be restored to same hostname, same location, same NBU version.

Hi Marianne, It's a clustered

Hi Marianne,

It's a clustered masterserver

NBUP1 is a cluster name

SNBUMASTERP2 is a node name.

Highlighted

What version are you on? If

What version are you on?

If you're on 7.1 we do not keep a copy of the database in the staging directory so you would have to do a recovery using the standard DR procedures.

 

If you are 7.5 or later, we keep a copy there.

 

Simply complete the following:

shutdown netbackup

rename netbackupdb\data to netbackupdb\data.corrupt

COPY netbackupdb\staging to a newly created data directory.

Start netbackup and keep your fingers crossed.

 

Note that you will not have any information in the database about any backups since the last hot catalog backup was taken.

 

Good luck!


Deb

 

Highlighted

mmmm - policy type sybase ...

mmmm - policy type sybase ... that may try to do something different when it restores it

I assume that this is a Catalog backup that you are looking at?

If so try the policy type of NBU-Catalog or even Windows-NT to see if you can see the files

If you are just restoring the conf file you should be able to direct that to any available client if you are having name resolution issues.

Hope this helps

Highlighted

Hopefully you have logged a

Hopefully you have logged a call with Symantec Support and have this fixed by now?

It seems to me as if NBU is getting 'confused' between virtual and nodename and is having problems connecting to itself.

Was NBU correctly installed as clustered master server?

Does 'nbclntcmd -self' resturn the virtual hostname?

Was Windows firewall disabled on master?

Do you have log folders in place?
on master: bpcd and tar
on media server: bpbrm