07-03-2020 05:27 AM
Greetings All,
We have a "strange" problem regarding SQL backup.
the job fails with error code 2 : none of the requested files were backed up
But in the logs we have certificate errors :
nbpxyhelper:
27/06/2020 21:55:00.838 [ValidatePeerHostProtocol::handle_exception] Something serious happened with async library curl functions, will fail state machine (../machines/LibNbPxyValidatePeerHost.cpp:1205)
27/06/2020 21:55:00.838 [ValidatePeerHostProtocol::setState] Transitioning state from: VALIDATE_PEER_HOST_PROTOCOL_RUNNING to: VALIDATE_PEER_HOST_PROTOCOL_ERROR (../machines/LibNbPxyValidatePeerHost.cpp:1520)
27/06/2020 21:55:00.838 [ValidatePeerHostProtocol::setState] Error in curl async library., nbu status = 7643, severity = 2, Additional Message: [PROXY] Encountered error (VALIDATE_PEER_HOST_PROTOCOL_RUNNING) while processing(ValidatePeerHostProtocol)., nbu status = 1, severity = 1 (../machines/LibNbPxyValidatePeerHost.cpp:1539)
the strange thing is, when it fails, we re-run the job and it may work and it may not..
sometimes it works for 3-4 consecutive days and then it fails.
I have redeployed the certificate again (revoke+ reset host attributes) but still, the problem occurs.
these errors led me to this technote:
https://www.veritas.com/support/en_US/article.100044566
and as our version is 8.2, we don't need an EEB because it is already included in the version (per the TN), so I just did the first & second steps and by doing that, the backup stopped working! (same error every time) so I guess we touched something in here !! I did a rollback and the backup worked again for 2-3 times then fails intermittently.
my guessing then is that the problem comes from this but the solution provided by that technote isn't working.
Now, I am trying to install this EEB: 3998268_3 and I will do the 1-2 steps from the technote and cross fingers :)
so if anyone had this error before please advise :)
I will get back to you asap.
NBU version 8.2 (master, media & sql server)
Best regards.
Solved! Go to Solution.
09-03-2020 02:06 PM
I came back to mark this as a solution because the problem was resolved after discovering that the client 'sometimes' tries to reply back to the master server on the wrong IP address..
The master server has 2 IP addresses (one for production and one for backup) so when we try the bptestbpcd all is fine (even ping used to work..) but sometimes it gets failing because the client chooses the wrong IP address to resolve the master's name. which explains why it works sometimes and also why we have certificate errors in the logs.
So the solution was to add the entry in the host's file on the client to force it to reply on the right ip address.
07-07-2020 03:24 AM
Any help guys? :)
Thanks,
07-08-2020 07:55 AM
@HH can you verify if the client is validated with both fully qualified name & shortname? I see error 7643 in the message.
Please check under "Security Management => Host Management => Mappings for Approval" for this client. Using bptestbpcd make sure proper communication is established between client & master or media servers.
07-08-2020 03:02 PM
07-14-2020 04:06 PM
Hi @Hamza_H ,
As you already created and recreated the certificate I think that problem can be the master server, but i cant confirm..
Did you already check this TN??
https://www.veritas.com/support/en_US/article.100043900
Hope this help.
Thiago
07-14-2020 04:29 PM
07-14-2020 04:34 PM
09-03-2020 02:06 PM
I came back to mark this as a solution because the problem was resolved after discovering that the client 'sometimes' tries to reply back to the master server on the wrong IP address..
The master server has 2 IP addresses (one for production and one for backup) so when we try the bptestbpcd all is fine (even ping used to work..) but sometimes it gets failing because the client chooses the wrong IP address to resolve the master's name. which explains why it works sometimes and also why we have certificate errors in the logs.
So the solution was to add the entry in the host's file on the client to force it to reply on the right ip address.