restore error code 5

Error Code 5 is just a generic error code saying it failed to recover the requested files - there could be a multitide of underlying reasons as to why the restore actually failed.

See the following T/N:

In-depth Troubleshooting Guide for Exit Status Code 5 in VERITAS NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0

Hello, I hat this problem a few months ago, and Andy helped me,

look for the HCART type of the tape and the HCART type on drives configuration.

If it help you.. give the solution for Andy.


see ya

Hi,

  While restoring to the same location the restore completes successfully. If I try to restore different location of the server then the restore fails with error code 5

As Andy pointed out - status 5 is a generic restore error. We need more info. Two places to look:
Activity monitor Details tab and the 'View Status' tab of the BAR Gui.

If you only have problems restoring to a different folder,  check ownership and permission on directories where files are restored. Also create a tar log directory on the client before you attempt the next restore.

provided (i.e. /tmp destination folder), after upgrading/downgrading etc did you ensure that the destination client for the restore (which must be a *NIX box) is pointing to the correct client & not to the (Windows?) PC that I presume you are running the restore from?

As I say, it was just a thought so we will await your log extracts!

Hi,

I am using the same PC to restore from whcih I am monitoring the the netbackup using remote administration console. i dont think the probelm is with upgrading or downgrading. I am trying to restore the same server from which backup is taken to the different path and I am sure that I am pointing the client. I am working to provide the tar log and I guess that will help all to understand the error.

This is also run on my PC, to restore a file from a UNIX client (in this example the file /etc/motd) to the same UNIX client but a different location (in this example /tmp):

First ensure correct Master, Source and Destination client (same) and policy type (this will be right otherwise you wouldn't get any further!)



Then, after selecting the file(s) you wish to restore, when you click on the "Start restore of marked files" button, you can select where you wish to restore the file(s):

Hi,


I am getting the below error messages in the logs


= SS93VPAP01-NB requesting_client = vps-prd-05 user = root): cannot connect on socket
12:18:05.996 [26756] <2> mail_msg_and_set_exit_status: entered; status = 0
12:18:05.996 [26756] <2> mail_msg_and_set_exit_status: Attempting to send mail to root on vps-prd-05
12:18:06.006 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:06.016 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:07.026 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:07.026 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:09.036 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:09.036 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:09.843 [24063] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2043: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
12:18:09.843 [24063] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpdbm
12:18:09.843 [24063] <2> logconnections: BPDBM CONNECT FROM 10.125.25.16.39915 TO 10.125.25.16.13724
12:18:09.875 [24063] <2> listen_loop: select() interrupted
12:18:13.055 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:13.065 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:21.085 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:21.095 [26756] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
12:18:21.095 [26756] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3570: vnet_async_connect failed: 18 0x00000012
12:18:21.095 [26756] <2> nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 18
12:18:21.095 [26756] <2> local_bpcr_connect: nb_connect_to_vnetd_service(vps-prd-05) failed: 25
12:18:21.095 [26756] <2> local_bpcr_connect: Can't connect to client vps-prd-05
12:18:21.095 [26756] <2> ConnectToBPCD: bpcd_connect_and_verify(vps-prd-05, vps-prd-05) failed: 25
12:18:21.095 [26756] <2> mail_msg_and_set_exit_status: Connection refused for host vps-prd-05
12:18:21.095 [26756] <2> mail_msg_and_set_exit_status: Couldn't close CLIENT_CMD_SOCK: Bad file number
12:18:21.095 [26756] <2> mail_msg_and_set_exit_status: Couldn't close CLIENT_STAT_SOCK: Bad file number
12:18:21.096 [26756] <2> mail_msg_and_set_exit_status: RESTORE EXIT STATUS = 5

Create the touch file No.Restrictions on the NBU Master Server and then try the redirect restore.

Follow this tech note...
http://support.veritas.com/docs/280742

The No.Restrictions touch file can be implemented so that the peer name of the requesting client for a restore does not need to match the NetBackup client name setting.

In Chapter 8 of the NetBackup 6.0 System Administrator's Guide for Windows, Volume 1, the manual implies that the No.Restrictions touch file is applicable only to restores made using the command line. However, this touch file has also been known to apply to the Backup, Archive, and Restore client GUI in the same manner.

This file affects the following user directed command line operations:
bplist
bprestore


The No.Restrictions touch file is processed by bprd whenever it receives a user-directed browse or restore request.  Such a request can be issued not only from the NBU client GUI and bplist/bprestore commands, but also from database extensions such as DB2, Informix, SQL-Server, Oracle, SAP, SQL-Backtrack, Sybase, and Teradata.

For a UNIX master alternate client recovery, create the following touch file:
usr/openv/netbackup/db/altnames/No.Restrictions

Fow Windows :
install location\veritas\netbackup\db\altnames\No.Restrictions

If altnames folder is not there create it.

And then try the restore again...
Once the restore is completed successfully.
Delete the No.Restrictions file.

I am sure this will work..

Thankyou and Regards ....