Backup failing with error code 58

[Jecintha]

Hello,

I see that backup for a particular windows host is failing with error code 58.  The server is reachable, however, in host properties, I see that the status of the server is Cannot connect to Socket (25).  I tried stopping and restarting the services running bpdown and bpup.  This has also not been of much help.

Appreciate any help in this regard.

Regards,

Jecintha

[K33]

Hi

Kindly look the technote

http://www.symantec.com/business/support/index?page=content&id=TECH68832

Check this fourms.

https://www-secure.symantec.com/connect/forums/backup-failing-server-error-code-58

[Jecintha]

Hello Kashish,

Thanks for the reply.  I went through the forum link attached.  There was an update that the below mentioned services should be running in the client:

NetBackup Client Service
NetBackup Legacy Client Service
NetBackup Legacy Network Service

I can see only the Netbackup Client Service running not the other services.

How do I proceed here.  Please guide.

Regards,

Jecintha 

[Marianne]

Stopping and starting won't help.

You need to confirm that client can resolve the Server's IP address to valid hostname that appears in client's Server list.

As per above-mentioned forum post, bpcd log on client will tell us if client can resolve Server's IP address.

If not, add Server to client's hosts file.

PS: PLEASE always mention OS on server and client as well as NBU version on server and client?
Different ports are used across different NBU versions.
Location of commands and logs are different for Windows and Unix/Linux.

[Taqadus_Rehman]

Is there a media server involved? Or do you only  have a master/media?

What version of NetBackup?

When you say you've tested comms, did you use bptestbpcd?

Are there multiple IP's configured on the client/master?

[Marianne]

Jecintha, you have not told us OS or NBU version on the client?

Please do so as this information is always relevant.

[Jecintha]

Hello Marianne,

The master server is a unix server and the client is a windows server.  The version of Netbackup is 7.1.

We have media servers which are again unix servers.

There are no multiple IPs configured in either the client or the master server.

With regards to testing the communication, I could not check bptestbpcd due to limited rights to the unix server (master server).  I had simply checked if the client server is up and running fine and if the Netbackup Client Service is running. 

Regards,

Jecintha

[mph999]

You need to get admin permissions then.  I don't understand how 'backup admins' are expected to run a backup environment without full permissions - it's madness.

Martin

[Jecintha]

I am currently working with the concerned team to either get the required permission or check bptestbpcd from their end.  Once bptestbpcd is tested, will proceed further.

Regards,

Jecintha

[mph999]

... see if you can make it the former ...

In order to be a backup admin, I would argue that you need permissions to run ALL of the NetBackup commands, and a very good selection of OS commands.

Martin

[Marianne]

Please remember to create bpcd log folder on client before doing betestbpcd.

Run bptestbpcd from master as well as all media servers that can backup this client.

In the meantime, find out if the Unix server(s) are on DNS.
If not, add hosts entries for master and all media servers on the Windows client.
Check that names used in hosts file correspond with SERVER entries on the Client.

About Services on the Client:
Please confirm that all of the following services are running on the client:

NBU 7.x:
NetBackup Client Service
NetBackup Legacy Client Service
NetBackup Legacy Network Service
Symantec Private Branch Exchange

NBU 6.x:
NetBackup Client Service

PS: While you are waiting for permission to run bptestbpcd, ensure that bpcd log folder exists on client, then try to connect to client from master.
To test media server connectivity, run a testbackup with media server STU in test policy.
Please copy client's bpcd log file to bpcd.txt and post as attachment.