cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Restore Exchange failed error 2810 and 5.

so what is 172.20.200.11 supposed to be? 

Re: Restore Exchange failed error 2810 and 5.

Bryan,

 

Restart Netbackup on Client should resolve this issue.

Re: Restore Exchange failed error 2810 and 5.

As you can see - Connection request is from IP address 172.20.200.11. The CAS server cannot resolve this IP address to a hostname that appears in the Server list. You need to check name resolution on the CAS server. Either DNS or local hosts file. When this has been fixed, clear host cache on the CAS server and retry the restore.

Re: Restore Exchange failed error 2810 and 5.

Hi,

The IP 172.20.200.11 is a new interface configured in the Network Load Balancer.

I add this IP in the regedit server list and now the restore operation is fine ,But i'm cann't pinging the dag from master server.

In Netbackup Console, host properties > Clients, the dag show status 25 cannot connect on socket.

The backup operation is faililng with code error 26

 

1/11/2016 10:49:17 AM - Info nbjm(pid=54564) starting backup job (jobid=159986) for client DAG1, policy EXCHANGE_TERCEIROS, schedule Full_Semanal  
1/11/2016 10:49:17 AM - Info nbjm(pid=54564) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=159986, request id:{D776CB2A-4E74-42BE-B2AB-BC239EAB2F4A})  
1/11/2016 10:49:17 AM - requesting resource DataDomain
1/11/2016 10:49:17 AM - requesting resource master.contoso.com.NBU_CLIENT.MAXJOBS.DAG1
1/11/2016 10:49:17 AM - requesting resource master.contoso.com.NBU_POLICY.MAXJOBS.EXCHANGE_TERCEIROS
1/11/2016 10:49:17 AM - requesting resource EXCHANGE_RESOLVER.master.contoso.com.EXCHANGE_TERCEIROS.DAG1
1/11/2016 10:49:17 AM - granted resource master.contoso.com.NBU_CLIENT.MAXJOBS.DAG1
1/11/2016 10:49:17 AM - granted resource master.contoso.com.NBU_POLICY.MAXJOBS.EXCHANGE_TERCEIROS
1/11/2016 10:49:17 AM - granted resource EXCHANGE_RESOLVER.master.contoso.com.EXCHANGE_TERCEIROS.DAG1
1/11/2016 10:49:17 AM - estimated 177903490 Kbytes needed
1/11/2016 10:49:17 AM - begin Parent Job
1/11/2016 10:49:17 AM - begin Exchange 14 Resolver, Start Notify Script
1/11/2016 10:49:17 AM - Info RUNCMD(pid=8684) started            
1/11/2016 10:49:17 AM - Info RUNCMD(pid=8684) exiting with status: 0         
Status 0
1/11/2016 10:49:17 AM - end Exchange 14 Resolver, Start Notify Script; elapsed time: 0:00:00
1/11/2016 10:49:17 AM - begin Exchange 14 Resolver, Step By Condition
Status 0
1/11/2016 10:49:17 AM - end Exchange 14 Resolver, Step By Condition; elapsed time: 0:00:00
1/11/2016 10:49:17 AM - begin Exchange 14 Resolver, Read File List
Status 0
1/11/2016 10:49:17 AM - end Exchange 14 Resolver, Read File List; elapsed time: 0:00:00
1/11/2016 10:49:17 AM - begin Exchange 14 Resolver, Resolver Discovery
1/11/2016 10:49:18 AM - started process bpbrm (14472)
1/11/2016 10:53:01 AM - Info bpbrm(pid=14472) connect failed STATUS (18) CONNECT_FAILED        
1/11/2016 10:53:01 AM - Info bpbrm(pid=14472)     status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG1 172.20.201.125 bpcd VIA pbx
1/11/2016 10:53:01 AM - Info bpbrm(pid=14472)     status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG1 172.20.201.125 bpcd VIA vnetd
1/11/2016 10:53:01 AM - Info bpbrm(pid=14472)     status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO DAG1 172.20.201.125 bpcd
1/11/2016 10:53:01 AM - Error bpbrm(pid=14472) Cannot connect to DAG1         
1/11/2016 10:53:01 AM - Info (pid=0) done. status: 58: can't connect to client      
Status 26
1/11/2016 10:53:01 AM - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 0:03:44
1/11/2016 10:53:01 AM - begin Exchange 14 Resolver, Stop On Error
Status 0
1/11/2016 10:53:01 AM - end Exchange 14 Resolver, Stop On Error; elapsed time: 0:00:00
1/11/2016 10:53:01 AM - begin Exchange 14 Resolver, End Notify Script
1/11/2016 10:53:02 AM - Info RUNCMD(pid=3436) started            
1/11/2016 10:53:02 AM - Info RUNCMD(pid=3436) exiting with status: 0         
Status 0
1/11/2016 10:53:02 AM - end Exchange 14 Resolver, End Notify Script; elapsed time: 0:00:01
Status 26
1/11/2016 10:53:02 AM - end Parent Job; elapsed time: 0:03:45
client/server handshaking failed(26)

 

 

Backup Specialist
Accepted Solution!

Re: Restore Exchange failed error 2810 and 5.

Hi all,

The problem with the backup operation was resolved after restart the master server machine.

The solution for the restore i find in the link:

https://www.veritas.com/support/en_US/article.TECH163033

Thanks for all

Backup Specialist

View solution in original post