cancel
Showing results for 
Search instead for 
Did you mean: 

Regarding backup is failed with error code 58

Rohit_Singh_Nay
Level 4
Hi All,

We are using the Netbackup 6.5.4 Backup enviorment in our master and clinet server.The client is Windows Box hosted on  ESX server and Master is a SUN box .All the configartion is fine from Client side the BPCLNTCMD -pn command gives the desired output.

While trying to connected from Master Server error is found. tracert command is also working fine.

please suggest


Warm Regards,

Rohit Singh Nayal 
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Rohit, as from NetBackup 6.x, communication between server (master/media) and client uses vnetd ONLY (13724). No need to test any other port.
13720 is bprd, which runs on the master server only.
The TechNote that I mentioned in my previous post explains how bpclntcmd -pn forwards the connection request from the client to the bprd on the master. The request is sent via vnetd.

I see these errors in the client's bpcd log:

bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038

The TCP error code 10038 indicates a problem at TCP/IP level which prevents socket setup on the client. There are a number of TechNotes that list some possible reasons for this problem and ways to troubleshoot.

http://seer.entsupport.symantec.com/docs/321172.htm
http://seer.entsupport.symantec.com/docs/257698.htm
http://seer.entsupport.symantec.com/docs/275200.htm

Although not all of these TechNotes describe status 58, the common factor is the 10038 TCP error.

View solution in original post

13 REPLIES 13

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Please have a look at this TechNote on Troubleshooting procedures for Status 58 errors:
http://seer.entsupport.symantec.com/docs/321172.htm

SteveYu
Level 4
Employee Accredited Certified
On the client
==========

1. Go to the Netbackup install directory typically c:\program files\veritas\netbackup\
2. Go to the logs directory
3. Create a directory called "bpcd" (no qutoes) if it does not already exist
4. Go into the bpcd directory and delete, rename or move the log for todays date.
5. Open a command prompt and type in "telnet localhost bpcd" no qutoes
6. Still in the bpcd directory check to see if a log file was created for todays date.

Was it created?
When you did the telnet did the connection connect and hold or did it connect and drop?

7. After you make those notes again delete the log file for todays date
8. Go to the master servers administration console
9. Click on host properties -> clients -> host properties. This operation should fail as you describe
10.  Go back on the client and back into the bpcd directory

do you see a new log file that should have been created from the connection attempt made from the gui?
If there is a log file here from the connection made from the gui. Post it here

Rohit_Singh_Nay
Level 4
Hi All,


Thanks for your reply

to Marianne:-  As per your reffred document  all the steps are taken by me and the only problem which I suspect is that Master server is not able to telnet the client :- 

telnet cseloukpiisv03_b 13720
Trying 172.17.147.133...
telnet: Unable to connect to remote host: Connection refused

I have also followed the follwing change also:-

Administration Console:
1. Launch the NetBackup Administration Console, connecting to the master server
2. Expand Host Properties in the left pane
3. Select Master Server in the left pane
4. Click the name of the master server in the right pane
5. Select the Client Attributes section
6. Add the name of the client in question if it isn't listed
7. In the Connect Options tab for the client, make the following changes:
BPCD connect back -> "Random port"
Ports ->  "Reserved port"
Daemon connection port -> "Daemon port only"


But the problem is still persist . and we donot use DNS in our backup Network all work is done by host file .


To Steve:- here is the BPCD log



12:21:41.749 [5928.5480] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

12:21:41.749 [5928.5480] <2> bpcd main: ReadKeyfile failed
12:21:41.749 [5928.5480] <2> bpcd main: offset to GMT 0
12:21:41.749 [5928.5480] <2> bpcd main: Got socket for input -1
12:21:41.749 [5928.5480] <2> logconnections: getsockname(-1) failed: 10038
12:21:41.749 [5928.5480] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
12:21:41.749 [5928.5480] <2> bpcd main: setup_sockopts complete
12:21:41.749 [5928.5480] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
12:21:41.749 [5928.5480] <16> bpcd main: authentication failed: 17
12:22:40.450 [2492.6012] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

12:22:40.450 [2492.6012] <2> bpcd main: ReadKeyfile failed
12:22:40.450 [2492.6012] <2> bpcd main: offset to GMT 0
12:22:40.450 [2492.6012] <2> bpcd main: Got socket for input -1
12:22:40.450 [2492.6012] <2> logconnections: getsockname(-1) failed: 10038
12:22:40.450 [2492.6012] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
12:22:40.450 [2492.6012] <2> bpcd main: setup_sockopts complete
12:22:40.450 [2492.6012] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
12:22:40.450 [2492.6012] <16> bpcd main: authentication failed: 17
20:02:13.359 [2940.6004] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

20:02:13.359 [2940.6004] <2> bpcd main: ReadKeyfile failed
20:02:13.359 [2940.6004] <2> bpcd main: offset to GMT 0
20:02:13.374 [2940.6004] <2> bpcd main: Got socket for input -1
20:02:13.374 [2940.6004] <2> logconnections: getsockname(-1) failed: 10038
20:02:13.374 [2940.6004] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
20:02:13.374 [2940.6004] <2> bpcd main: setup_sockopts complete
20:02:13.374 [2940.6004] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
20:02:13.374 [2940.6004] <16> bpcd main: authentication failed: 17
20:03:10.872 [4840.5840] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

20:03:10.872 [4840.5840] <2> bpcd main: ReadKeyfile failed
20:03:10.872 [4840.5840] <2> bpcd main: offset to GMT 0
20:03:10.872 [4840.5840] <2> bpcd main: Got socket for input -1
20:03:10.872 [4840.5840] <2> logconnections: getsockname(-1) failed: 10038
20:03:10.872 [4840.5840] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
20:03:10.872 [4840.5840] <2> bpcd main: setup_sockopts complete
20:03:10.872 [4840.5840] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
20:03:10.872 [4840.5840] <16> bpcd main: authentication failed: 17
20:15:02.490 [4888.4984] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

20:15:02.490 [4888.4984] <2> bpcd main: ReadKeyfile failed
20:15:02.490 [4888.4984] <2> bpcd main: offset to GMT 0
20:15:02.490 [4888.4984] <2> bpcd main: Got socket for input -1
20:15:02.490 [4888.4984] <2> logconnections: getsockname(-1) failed: 10038
20:15:02.490 [4888.4984] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
20:15:02.490 [4888.4984] <2> bpcd main: setup_sockopts complete
20:15:02.490 [4888.4984] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
20:15:02.490 [4888.4984] <16> bpcd main: authentication failed: 17
20:16:02.645 [6064.5012] <2> ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist

20:16:02.645 [6064.5012] <2> bpcd main: ReadKeyfile failed
20:16:02.645 [6064.5012] <2> bpcd main: offset to GMT 0
20:16:02.645 [6064.5012] <2> bpcd main: Got socket for input -1
20:16:02.645 [6064.5012] <2> logconnections: getsockname(-1) failed: 10038
20:16:02.645 [6064.5012] <16> bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038
20:16:02.645 [6064.5012] <2> bpcd main: setup_sockopts complete
20:16:02.645 [6064.5012] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.307: Function failed: 17 0x00000011
20:16:02.645 [6064.5012] <16> bpcd main: authentication failed: 17
---------------------------------------------------------------------------------------------------------------------------------------------------------------



Kindly provide your views as my problem is still persist if any thing is neede from my side please let me know.

SteveYu
Level 4
Employee Accredited Certified
And they are important. Thanks for providing the log. When you get a chance review the questions below and let me know if you have any questions/comments.

1. When you did the telnet did the connection connect and hold or did it connect and drop? (If you are not sure compare this behavior by telnetting to a client that does work)
2. Do you have other virtual hosts on that ESX host that fail as well? or just 1 VM in particular?
3. Has this ever worked?

Rohit_Singh_Nay
Level 4
HI Steve ,

Thanks for your reply,

Client is able to connect with Master server through Telnet Master server Name 13720

But the Master is not able to connect with the client through that command. I have checked with other serevr also but they are also showing the same result even their backup is runnng fine.

Its hard for us to say cause we didn't take a look on this.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Rohit, as from NetBackup 6.x, communication between server (master/media) and client uses vnetd ONLY (13724). No need to test any other port.
13720 is bprd, which runs on the master server only.
The TechNote that I mentioned in my previous post explains how bpclntcmd -pn forwards the connection request from the client to the bprd on the master. The request is sent via vnetd.

I see these errors in the client's bpcd log:

bpcd setup_sockopts: setsockopt 2 failed: h_errno 10038

The TCP error code 10038 indicates a problem at TCP/IP level which prevents socket setup on the client. There are a number of TechNotes that list some possible reasons for this problem and ways to troubleshoot.

http://seer.entsupport.symantec.com/docs/321172.htm
http://seer.entsupport.symantec.com/docs/257698.htm
http://seer.entsupport.symantec.com/docs/275200.htm

Although not all of these TechNotes describe status 58, the common factor is the 10038 TCP error.

SteveYu
Level 4
Employee Accredited Certified
She is right. Short summary you will want to check is. Telnet from master to client on port 13724. Then compare this against a working client

Francis_Doran
Level 4
Hi Rohit

Can you ping the client from your master server? Maybe you have an issue with the defaultrouter setting on your master server.

Stumpr2
Level 6
The media server needs to connect to the client.
Check communication between the client and its media server.

Twinkle_Sapra
Level 5
Certified

Hi rohit

1. Send bpcd logs of client . and test

2. bpclntcmd -pn from client

3. bpclntcmd -hn <client_name> from master server.

4. Run netstat -a on client, check bpcd is in listening state.

Rohit_Singh_Nay
Level 4

 

HI All,

Thanks for Posting your suggestion on my querry.

One of our Software 
Interwoven OpenDeploy 61 service is blocking our port in the TCP/IPstack in windows.

But I wondered while running the command netstat -a the vnetd port is showing in the listening status and its not showing anything which attract our concern. After removing the software completely  the backup is  running  fine and problem is resolved.

Anonymous
Not applicable

this link is not working 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Anonymous 


@Anonymous wrote:

this link is not working 


This is because you are tagging onto a 10-year-old post.

Symantec and Veritas have split ways, so, Symantec links will no longer work. 

If NOTHING in this post has helped you, then please start a new discussion with details of your environment and tell us what you have done thus far to troubleshoot.