Showing results for 
Search instead for 
Did you mean: 

Exchange Backup - CU13

Level 2

We are taking Exchange backup in one of our customers. But when taking backup, we get error as below. What could be the solution?


Our Os Info : Windows Server 2019 Standard

Our Exchange Info : Version 15.2 ( Build 1258.12 ) - Standard Edition

Error Code : 

  • Jun 21, 2023 6:17:52 PM - Info bpresolver (pid=19628) done. status: 41: network connection timed out
  • Operation Status: 26
  • Jun 21, 2023 6:17:52 PM - end Exchange14 Resolver: Resolver Discovery; elapsed time 0:05:04
  • Jun 21, 2023 6:17:52 PM - begin Exchange14 Resolver: Stop On Error
  • Operation Status: 0
  • Jun 21, 2023 6:17:52 PM - end Exchange14 Resolver: Stop On Error; elapsed time 0:00:00
  • Operation Status: 26
  • Jun 21, 2023 6:17:52 PM - end Parent Job; elapsed time 0:05:04
  • client/server handshaking failed(26)



Add more client_read_timeout on your media server. Also please share full detailled status

Level 4

@tarikk  Most likely this error code occurs for following situations

1. Name resolution failure for Exchange DAG & Node names on NetBackup Master/Media or vise versa.

2. Check Exchange VSS Writer status. All writers should not display status as "Error or Waiting for Completion". check command --> "vssadmin list writers"

3. Check communication between NetBackup Master/Media and Exchange DAG Nodes. Check command from Master/Media to Exchange Nodes

/usr/openv/netbackup/bin/admincmd/bptestbpcd -host ExchangeNode / DAG

Run above command for all exchange nodes participating in DAG.

If you can post more errors from detailed job status. additional troubleshooting steps can be suggested.


Level 6
Partner    VIP    Accredited Certified

Do regular "MS-Windows" Policy backups work fine? Try it for all the hosts and the DAG virtual name too. If that fails then you will need to check name resolution (either through DNS or hosts table).

Partner    VIP    Accredited Certified

Hello @tarikk ,

three people took some time to give you advice and there is no response from you.

You also did not mention how the stated CU13 is relevant and if the error is related to its applying.


Level 2
I was on leave and now I see what you wrote. I will try these and get back to you.

Level 2

The problem was solved by itself. When I had the problem, I rebooted the exchange servers. It gave the same error again for 2 days and then it resolved itself.