Backup failed with EC 58

[shreek]

Hello All,

Kindly help me to deal with the client netbackup installation issue, I have installed netbackup on windows 2008 R2 *64 bit  client, previously the backup was running successfully, Just yesterday onwards backup failed with EC 58, Also i can see there is no bpps services available on the client. All the  host entries and port connection are mentioned and opened respectively, Even after repair and successfull  reinstallation I am facing the same problem, Kindly advice how to overcome this issue asap. 

Thanks,

shreek

[#2]

Shreek, 

1) kinldy create a separate post for any issues :)

2) always mention OS, Netbackup version of Master, media, client.

3) Please create bpcd folder on client @ install path\Program Files\VERITAS\NetBackup\logs and set verbosity to 5. Then try bptestbpcd command from your master & media server and post logs.

Technicians on this forum are always happy to help :)

[Marianne]

Which NBU version on the client?

Which NetBackup and Symantec services are running on the client?

On NBU 7.x client all of these services should be running:

NetBackup Legacy Client Service
NetBackup Client Service
NetBackup Legacy Network Service
Symantec Private Branch Exchange
 

To troubleshoot, ensure bpcd log folder exists on the client.
Check that Windows Firewall is disabled on the client.

[sdo · Accepted solution]

Basic Checks...

On the master:

1) Can the master server ping the client?

master> ping client.name

2) Can the master resolve the client name?

master> nslookup clent.name

3) Is port 1556 open from the master to the client?

master> telnet client.name 1556

.

On the client:

1) Can the client ping the master name?

client> ping master.name

2) Can the client resolve the master name?

client> nslookup master.name

3) Is port 1556 open from the client to the master?

client> telnet master.name 1556

.

Failure of the above is the most typical cause of status 58.

If you can prove the above works - then we may be able to give you some NetBackup CLI commands to dig further.

[Michael_G_Ander]

Have often seen similar problems in connection with security patches, antivirus updates and firewall rules reconfiguration.

When I have these kinds of issues, I always go through the application & system event log on the client to see if there is an indication of what could cause the problem besides doing the checks already mentioned.

If your company is using change log, then go through that too.

Could be worth doing traceroute (tracert) between client and netbackup server(s), especially if the client have multiple interfaces.

Have also seen this when the firewall had crashed on a windows machine, so that firewall showed as not running but still stopped incoming traffic from the backup server.