restore error code 5

Hi ,
    We are using netbackup 6.5.3.1 as master server.Somedays before I have upgraded my Remote administration console from 6.5 to 6.5.3.1. But My remote restore console is upgraded only to 6.5.3.While restoring I am getting the error code 5. I have degraded my remote administration console and again started to restore still I am getting the same error.can u help me resolve this?
1 Solution

Accepted Solutions
Accepted Solution!

Hi ,            For the above

Hi ,

 

         For the above issue is due to network connectivity.

        As we configured the backup VLAN using private VLAN concepts. Master and media servers we in master VLAN and clients are in community VLAN.

        From windows administration console need have direct connctivity to client to store the backup in diffrent path.

       But in private VLAN concepts it is not possible. We got this solution from CISCO.

       Finally I configured JAVA administartion console. Now I can restore the backups using this to diffrent clients ..

    Thank you for all your support.

 

 

 

 

 

 

 

   

 

 

25 Replies

We'll need more information.


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 E...

HCART


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

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

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.

Hi, I am just trying to

Hi,

I am just trying to restore in the /tmp directory . There is no need of permission to restore in the /tmp directory. Any way let me create the log before I restore again, then I will get u.

Just wondering, from the little snippet of info you've just


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

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.

Are you trying something like this?


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

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 No.Restrictions

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 ....


Hi,   I have tried the above

Hi,

  I have tried the above still I am getting the same error.

Before we troubleshoot the

Before we troubleshoot the status 25 (Can't connect to client vps-prd-05) please give us a run-down of the host names that are involved in this restore process:
Master server name
Admin Console name
Source client name
Destination client name

Next, find this section in bprd log file on master and post output.
.... <2> restorefiles: browse_client =
.... <2> restorefiles: requesting_client =
.... <2> restorefiles: destination_client =
.... <2> restorefiles: requesting_client_hostname =
.... <2> restorefiles: destination_client_hostname =
.... <2> restorefiles: requesting_user =
.... <2> restorefiles: requesting_group =
.... <2> restorefiles: progress_file =
.... <2> restorefiles: rename_file =
.... <2> restorefiles: policy =
.... <2> restorefiles: client_type =


Please also post about 5 lines above/before this:
= SS93VPAP01-NB requesting_client = vps-prd-05 user = root): cannot connect on socket


Please have a look at your


Please have a look at your post a couple of months ago regarding restore problems:
https://www-secure.symantec.com/connect/forums/restoring-problem-gui

Probably the same issue?

Hi,     I am maintaining

Hi,

    I am maintaining vps-prd-05 hostname of remote administration console in netbackup client properties.

Master server:SS93VPBK01-01

Sourse client Name :SS93VPAP01-NB

Destination client Name :SS93VPAP01-NB

I ahve checked my old posts too. the configuration are correct as per my old post.

We can see that there is an

We can see that there is an attempt to connect to your Admin Console:
requesting_client = vps-prd-05 user = root): cannot connect on socket

Please post this section in your bprd log:
find this section in bprd log file on master and post output.
.... <2> restorefiles: browse_client =
.... <2> restorefiles: requesting_client =
.... <2> restorefiles: destination_client =
.... <2> restorefiles: requesting_client_hostname =
.... <2> restorefiles: destination_client_hostname =
.... <2> restorefiles: requesting_user =
.... <2> restorefiles: requesting_group =
.... <2> restorefiles: progress_file =
.... <2> restorefiles: rename_file =
.... <2> restorefiles: policy =
.... <2> restorefiles: client_type =

We also have not yet seen your tar log on the destination client?

Hi, Below you can see the

Hi,

Below you can see the logs while restoring the to other location.


08:29:39.820 [2536] <2> process_request: requesting_clnt_hostname = ccname vps-prd-05
08:29:39.821 [2536] <2> restorefiles:    mpx_restore_possible = 1
08:29:39.821 [2536] <2> restorefiles:    browse_client = SS93VPAP01-NB
08:29:39.821 [2536] <2> restorefiles:    requesting_client = vps-prd-05
08:29:39.821 [2536] <2> restorefiles:    destination_client = SS93VPAP01-NB
08:29:39.821 [2536] <2> restorefiles:    requesting_client_hostname = vps-prd-05
08:29:39.821 [2536] <2> restorefiles:    destination_client_hostname = SS93VPAP01-NB
08:29:39.821 [2536] <2> restorefiles:    requesting_user = root
08:29:39.821 [2536] <2> restorefiles:    requesting_group = root
08:29:39.847 [2536] <2> add_image_to_list: open restore job params /usr/openv/netbackup/db/jobs/restart/17804.parms for w
08:29:39.847 [2536] <2> get_long: (2) premature end of file (byte 1)
08:29:39.851 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:39.861 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:40.881 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:40.891 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:42.911 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:42.921 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:46.941 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:46.951 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:54.971 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:54.981 [2536] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 146 0x00000092
08:29:54.981 [2536] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3570: vnet_async_connect failed: 18 0x00000012
08:29:54.981 [2536] <2> nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 18
08:29:54.981 [2536] <2> local_bpcr_connect: nb_connect_to_vnetd_service(vps-prd-05) failed: 25
08:29:54.981 [2536] <2> local_bpcr_connect: Can't connect to client vps-prd-05
08:29:54.981 [2536] <2> ConnectToBPCD: bpcd_connect_and_verify(vps-prd-05, vps-prd-05) failed: 25
08:29:54.982 [2536] <2> add_msgs_to_progress_file: connection refused by host vps-prd-05
08:29:54.999 [2536] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2043: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
08:29:54.999 [2536] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpcd
08:30:12.761 [2536] <2> start_brm: /usr/openv/netbackup/bin/bpbrm bpbrm -restore -mt 0 -k 0 -c SS93VPAP01-NB -hostname SS93VPAP01-NB -rclnt vps-prd-05 -rclnt hostname vps-prd-05 -browse_clnt SS93VPAP01-NB -ru root -firstblk 3810359 -cl APPLICATIONS_01 -bt 1275757233 -st 4 -secure 1 -b SS93VPAP01-NB_1275757233 -cn 1 -rst 1275784164 -to 0 -mud 180 -ct 0 -S SS93VPBK01-01 -masterversion 650000 -backup_copy 0 -latest_image -flport 0 -flipc /tmp/vnet-02536275784197482487000000 002-Qvaa9e -p /APP_BKP/APP_BACKUP -rg root -L /D/Inst_veritas/NetBackup/logs/user_ops/yal1933/logs/NBWIN018 -R /D/Inst_veritas/NetBackup/logs/ALTPATH/ALTPATH.016 -clnt_lc_messages en -clnt_lc_time en -clnt_lc_ctype en -clnt_lc_collate en -clnt_lc_numeric en -no_callback -connect_options 0x01010100 -jobid 17804 -restoreid 17804.001 -job_total 1
 
08:30:12.621 [2536] <2> local_bpcr_connect: nb_connect_to_vnetd_service(vps-prd-05) failed: 25

08:30:12.621 [2536] <2> local_bpcr_connect: Can't connect to client vps-prd-05
08:30:12.621 [2536] <2> ConnectToBPCD: bpcd_connect_and_verify(vps-prd-05, vps-prd-05) failed: 25

08:30:12.621 [2536] <2> add_msgs_to_progress_file: connection refused by host vps-prd-05
08:30:12.621 [2536] <2> start_brm: backup restore server = SS93VPBK03
08:30:12.638 [2536] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2043: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
08:30:12.638 [2536] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpcd



 

You have not yet shared the


You have not yet shared the tar log on the destination client?

Comms with the Admin Console is required to create the restore log under ...\NetBackup\logs\user_ops\<user-name>\logs  as well as the AltPath file (...\NetBackup\logs\AltPath\ALTPATH.###) where info about the alternate restore location is written.

Is there a possibility that the Windows Firewall was enabled? It seems that your Admin Console (vps-prd-05) is rejecting comms attempt from the master server.
Troubleshoot comms with your admin console:
Create bpcd log on vps-prd-05 under ...\NetBackup\logs and test from master server:
bptestbpcd -verbose -host vps-prd-05

It seems a connectivity issue


It seems a connectivity issue with NetBackup , most  of the time this sort of restore error occurs when media servers entries are different or not present . Please check if all the media server entries are correct to correct the issue.

Hi,         Sorry for the

Hi,

        Sorry for the late reply. In tar log I am not seeing any log messages. There is a single line only. That is retore stared.But i came to know that I am getting an deny message in the firewall, when my master server is trying to connect the my local pc(where my emote administration console is installed). Can u suggest me what are the port to be opened for master server to connect my local pc. (13724,13782)