Forum Discussion

j_mendes's avatar
j_mendes
Level 3
4 years ago

Backups failing with status 59

Hello, I am getting this 59 error when performing MS-Windows backups. It started recently. I've seen other VOX posts with this issue discussed, but none of the suggested troubleshooting actions worked, such as checking DNS resolution, reinstalling the Netbackup Client, clearing host cache, renewing certificates, adding the server hostname to the SERVER variable.

I uploaded logs from bprd, bpcd, and bptestbpcd. In our scenario, tcm-mst-01.tcm.go is the Master Server and tcm-dados01.tcm.go is the client. In the logs, you will see that bpcd thinks that tcm-dados01.tcm.go is the SERVER itself which is a behavior I've never seen before. The command I ran was bptestbpcd -client tcmdados01.tcm.go -verbose -debug

  • From what server you run bptestbpcd?
    what netbackup installation you perform on TCMDADOS01.tcm.go (media or client)?

    please post a screenshot from the servers list from the client properites

    • j_mendes's avatar
      j_mendes
      Level 3

       

      tcm-media-01.tcm.go is another Media Server. I tried adding TCMDADOS01.tcm.go to this registry variable, but bptestbpcd gives me status code 23 - socket read failed.

      • j_mendes's avatar
        j_mendes
        Level 3

        I tried bptestbpcd to a Linux client, and it worked. Then I tried bptestbcd to another Windows client, but got the same error. Maybe this is somehow related to Windows?

  • From the client run (if the IP matches to what the client has):

    echo REQUIRED_INTERFACE = 10.10.110.4 | nbsetconfig

    And restart the NetBackup Services at the client.

    This should force NBU to use the 10.10.110.4 for incoming and outgoing comms. There is no reason why it should be wondering around to 127.0.0.1.

     

  • Also, 127.0.0.1 should always resolve to localhost, your CONNECT_OPTIONS rely on that.