Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error 58 - Backup Fail

Created: 17 Sep 2012 | 11 comments

Recieved error 2006 - drives were down.  Put them up again and ran backup and got error 58.  Was able to ping network and is live.

Please help ?

Comments 11 CommentsJump to latest comment

Marianne's picture

The two errors are completely unrelated.
Since you post title says status 58, I guess that is what we need to troubleshoot.
Ping is not the only network test. You need to ensure forward and reverse lookup between media server and client as well as port connectivity.
Please do the following to troubleshoot:
On client, create bpcd log folder.
On media server, run this command from command:
bptestbpcd -client 'client-name' -verbose -debug

Plese post output as well as client's bpcd log file.

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

LGSC4900's picture

Getting the same error message. See my post.

salcedoj's picture

Hi Marianne,

Thank you for reply back to my post.  I am very new to this application and have no idea where the log file on the client is or where I run the command in the media server :( I have the netbackup gui that I am using as well as the netbackup adic scalarai500 robot panel.

Please advise.

Mouse's picture

Here is a guide how to run bptestbpcd  http://www.symantec.com/docs/TECH42657

Marianne's picture

You need to create bpcd folder on the client under the netbackup\logs folder.

Unix client: create bpcd folder in /usr/openv/netbackup/logs

Windows client: create bpcd folder <install-path>\veritas\netbackup\logs

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

Mouse's picture

See what Marianne is saying, you may have issue on DNS layer, not with network connectivity

salcedoj's picture

Thank Mouse!

I ran bptestbpcd -client 45524 and it stall.. nothing comes back?

Mouse's picture

Well, is the 45524 is your client's host name?

Marianne's picture

Your command is trying to connect to Client name 45524.

You did not add '-verbose -debug', so connecion actions/attempts are not displayed on the screen.

Server will keep on trying until 'Client Connect Timeout' period expires.
The default is 5 minutes, but it may have been increased on your server.

If your client name is really 45524, hopefully you have created bpcd log on client before issuing bptestbpcd command?

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

badri's picture

provide the output for the full command which Marianne has asked that will help in understand where the problem is

chandrasekarmp's picture

If you have proper routing and DNS entries / host file entries in the client, then you should not have any issues with connectivity.

As Marianne said.. send us the output with bptestbpcd -client 45524 -verbose -debug output along with bpcd logs to get an idea about the issue