Restore Exchange failed error 2810 and 5.

[Bryan_Sousa]

Hi

I'm trying restore de mailbox without successfuly. when start the job restore it failed..

I tryed restore in original location and alternative location too, both failed.

Master server and Media server windows server 2008 R2

Exchange 2010 using DAG

Netbackup 7.6.0.4

JOB RESTORE

04/01/2016 14:05:14 - begin Restore
04/01/2016 14:05:14 - restoring image DAG1_1451648394
04/01/2016 14:05:14 - requesting resource @aaaat
04/01/2016 14:05:15 - Info bprd(pid=31972) Restoring from copy 1 of image created 01/01/16 09:39:54 from policy EXCHANGE_TREE 
04/01/2016 14:05:15 - Info bprd(pid=31972) Granular restore has started, this may take a while....    
04/01/2016 14:05:15 - granted resource MediaID=@aaaat;DiskVolume=vol_su;DiskPool=DataDomain_DP;Path=vol_su;StorageServer=datadomain.contoso.com;MediaServer=MEDIA
04/01/2016 14:05:26 - Error bpbrm(pid=17572) bpcd on CAS.CONTOSO.COM exited with status 59: access to the client was not allowed
04/01/2016 14:05:26 - Info tar32(pid=0) done. status: 59: access to the client was not allowed   
04/01/2016 14:05:26 - Error bpbrm(pid=17572) client restore EXIT STATUS 59: access to the client was not allowed 
04/01/2016 14:05:27 - restored image DAG1_1451648394 - (access to the client was not allowed(59)); restore time 0:00:13
04/01/2016 14:05:27 - end Restore; elapsed time: 0:00:13
MS-Exchange-Server policy restore error(2810)

JOB SECUNDARY

04/01/2016 14:04:59 - begin Restore
04/01/2016 14:05:02 - Info bprd(pid=52448) starting BPRESOLVER           
04/01/2016 14:05:03 - Info bprd(pid=52448) BPRESOLVER has executed on server (SERVERX02)       
04/01/2016 14:05:27 - Error bprd(pid=52448) Cannot process target restore path        
04/01/2016 14:05:28 - end Restore; elapsed time: 0:00:29
the restore failed to recover the requested files(5)

[Will_Restore]

bpcd on CAS.CONTOSO.COM exited with status 59: access to the client was not allowed

NetBackup status code: 59
Message: access to the client was not allowed
Explanation: The master or the media server tries to access the client, but the
client does not recognize the server as a valid server.
Recommended Action: Do the following, as appropriate:
■ If the server is a valid server, verify that it is in the server list on the client. If
necessary add it as follows:
■ On Windows clients: Add the server on the Server to use for backups and
restores drop-down in the Specify NetBackup Machines and Policy Type
dialog box. To display this dialog box, start the Backup, Archive, and Restore
interface on the client. Then click Specify NetBackup Machines and Policy
Type on the File menu.

[Marianne]

Which DAG member did you select as destination client? Have you added Distributed Application Restore Mapping" entries for all DAG members? And Server entries for media server on all DAG members?

[Bryan_Sousa]

Hi Will,

In my Environment is configured exchange in DAG with two servers in dag EX01 and EX02. And I have a VIP (IP) that directs for EX01, EX02, EX04 or EX05.

I verifyed the server list on four servers. Add the full and short name of the master and media.

[Bryan_Sousa]

Hi Marianne,

In BAR the source client and destination client, both are DAG1.

Have you added Distributed Application Restore Mapping" entries for all DAG members? I dont know how to do this
And Server entries for media server on all DAG members? Yes, i add in all members of the dag the full and short name of master and media

[Bryan_Sousa]

Hi Marianne,

Add the Application Restore Mapping as bellow:

Application Host                            Component Host

dag1                                             CAS

dag1                                             EX01

dag1                                             EX02

CAS                                             EX04

CAS                                             EX05

it's correct?

[Bryan_Sousa]

i need add the Granular proxy host name?

[Marianne]

See the Solution section of this TN : http://www.veritas.com/docs/000083328 (also documented in NBU for Exch manual ). Add shortname as well as FQDN. We see FQDN being used in 1st restore attempt: CAS.CONTOSO.COM To troubleshoot status 59 error, create bpcd log folder on CAS.CONTOSO.COM. This log will show connection request from media server IP address and how the client is resolving IP address to hostname, followed by comparing resolved hostname with Server. For further troubleshooting, ensure all of these log folders exist on all DAG members : bpresolver, tar.

[Bryan_Sousa]

Marianne,

bellow is the log in BAR:

16:10:34 05/01/2016: Restore Started

16:10:50 (146966.001) Restoring from copy 1 of image created 05/01/2016 06:12:16 from policy EXCHANGE_TREE
16:10:50 (146966.001) Granular restore has started, this may take a while....
16:11:02 (146966.001) Status of restore from copy 1 of image created 05/01/2016 06:12:16 = access to the client was not allowed

16:11:02 (146966.001) The following files/folders were not restored:
16:11:02 (146966.001) UTF - /Microsoft Exchange Database Availability Groups/DAG1.contoso.com/Microsoft Information Store/USUARIOS-K-P/Database/User Barros [user.barros]/Top of Information Store/Inbox/Confirmações Enviadas/

16:11:02 INF - Server status = 2810
16:11:02 INF - Server status = 5
16:11:02 (146965.xxx) INF - Status = the restore failed to recover the requested files.

16:11:02 (146966.xxx) INF - Status = MS-Exchange-Server policy restore error.

[Marianne]

.....access to the client was not allowed

Please read through my previous post again regarding status 59.

You need bpcd log on the DAG node where restore is directed to.

[Bryan_Sousa]

Marianne,

The dag has two servers: ex01 and ex02

[nbutech]

Is telnet for bpcd port working...?

is there a firewall enabled ?

Did you clear host cache ?

Have you tried No.Restrictions file

[Bryan_Sousa]

Yes, telnet in bpcd port is connecting.

The firewall is off

I run the command clear_host_cache

I dont tried the No.Restrictions how to do this?

[Marianne]

Your opening post shows another hostname: bpcd on CAS.CONTOSO.COM exited with status 59: access to the client was not allowed Restore to the CAS server is failing with status 59. This is where you need to create and check bpcd log and where you need to update Server entries.

[Marianne]

The problem is NOT with port connectivity. The problem is with reverse lookup that does not find a Server entry that matches. You need bpcd log on the CAS server. Please see my post below.

[Bryan_Sousa]

Hi Marianne

this are the logs of CAS.

[Marianne]

I cannot open zip files on my phone. Can you copy the log to bpcd.txt and upload? Else I will have a look tomorrow.

[Marianne]

I cannot open zip files on my phone. Can you copy the log to bpcd.txt and upload? Else I will have a look tomorrow.

[Will_Restore]

Problem with name resolution

10:35:46.561 [18424.11524] <8> retry_getnameinfo: [vnet_addrinfo.c:1149] getnameinfo() failed 11001 0x2af9
10:35:46.561 [18424.11524] <8> vnet_cached_getnameinfo: [vnet_addrinfo.c:1891] retry_getnameinfo() failed RV=11001 IPSTR=172.20.200.11 PORT=9103
10:35:46.561 [18424.11524] <2> bpcd peer_hostname: vnet_cached_getnameinfo() failed: 6 11001
10:35:46.561 [18424.11524] <2> bpcd peer_hostname: Connection from host 172.20.200.11 (172.20.200.11) port 9103
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing master_server and 172.20.200.11
10:35:46.561 [18424.11524] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen() failed ERRNO=2 FILE=C:\Program Files\Veritas\NetBackup\var\host_cache\14c\82283b4c+0,1,a,0,1,0+172.20.200.11.txt
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing ex04 and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing media_server and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing ex05 and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing ex01 and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing ex02 and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing CAS and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing cas and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing cas.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing CAS.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing master_server.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing media_server.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing media_server and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing dag1 and 172.20.200.11
10:35:46.561 [18424.11524] <4> bpcd valid_server: 172.20.200.11 is not a master server
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing master_server.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <2> bpcd valid_server: comparing media_server.contoso.com and 172.20.200.11
10:35:46.561 [18424.11524] <16> bpcd valid_server: 172.20.200.11 is not a media server either

[Bryan_Sousa]

bpcd log attached.