(39) client name mismatch

Question

Exchange DAG backup is failing with error code 39.client name mismatch.
&nbsp;
Please find the error mesage below.
11/21/2012 07:44:53 - Info nbjm (pid=10474) starting backup job (jobid=6749) for client PHX-EXCH-MBX-01, policy vrm-c-exchange, schedule Full
	11/21/2012 07:44:53 - estimated 0 kbytes needed
	11/21/2012 07:44:53 - Info nbjm (pid=10474) started backup job for client PHX-EXCH-MBX-01, policy vrm-c-exchange, schedule Full on storage unit dstu_sco1sp01
	11/21/2012 07:44:53 - started process bpbrm (pid=25634)
	11/21/2012 07:45:04 - Error bpbrm (pid=25634) bpcd on dag1 exited with status 39: client name mismatch
	11/21/2012 07:45:05 - Error bpbrm (pid=25634) cannot send mail because BPCD on dag1 exited with status 39: client name mismatch
	11/21/2012 07:45:05 - Info bpbkar (pid=0) done. status: 39: client name mismatch
	11/21/2012 07:45:05 - end writing
	client name mismatch&nbsp; (39)
	&nbsp;
Exhange 2010, Netbackup Version:7.1.0.4
&nbsp;
Please find the output of bppllist vrm-c-exchange -U
Policy Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vrm-c-exchange
&nbsp; Policy Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MS-Exchange-Server
	&nbsp; Active:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	&nbsp; Effective date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11/21/2012 03:31:49
	&nbsp; Mult. Data Streams:&nbsp; no
	&nbsp; Client Encrypt:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Checkpoint:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Policy Priority:&nbsp;&nbsp;&nbsp;&nbsp; 90000
	&nbsp; Max Jobs/Policy:&nbsp;&nbsp;&nbsp;&nbsp; Unlimited
	&nbsp; Disaster Recovery:&nbsp;&nbsp; 0
	&nbsp; Collect BMR info:&nbsp;&nbsp;&nbsp; no
	&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NetBackup
	&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *ANY*
	&nbsp; Keyword:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (none specified)
	&nbsp; Data Classification:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp; no
	&nbsp; Exchange Source passive db if available: yes
	&nbsp; Exchange 2010 Preferred Server:&nbsp; phx-exch-mbx-01 phx-exch-mbx-02&nbsp; Application Discovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Discovery Lifetime:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 seconds
&nbsp; Granular Restore Info:&nbsp; no
	&nbsp; Ignore Client Direct:&nbsp; no
	&nbsp; HW/OS/Client:&nbsp; Windows-x64&nbsp;&nbsp; Windows2008&nbsp;&nbsp; dag1
&nbsp; Include:&nbsp; Microsoft Exchange Database Availability Groups:\
&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Differential-Inc
	&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Differential Incremental Backup
	&nbsp;&nbsp;&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; every 1 day
	&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Retention Level: 1 (2 weeks)
	&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Daily Windows:
&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Full
	&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Automatic Backup
	&nbsp;&nbsp;&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; every 7 days
	&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Retention Level: 0 (1 week)
	&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; std-full-1mo
	&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Daily Windows:
&nbsp;
Please suggest.
&nbsp;
Thanks &amp; Regards,
Ganesh Bhalerao
&nbsp;
&nbsp;

mark_solutions · Answer

Make sure that the host names of each DAG member is resolvable correctly by the Media Servers - use hosts files is neccesary - see this tech note:
http://www.symantec.com/business/support/index?page=content&amp;pmv=print&amp;impressions=&amp;viewlocale=&amp;id=TECH176473
This should include CAS servers etc. (they all need a NBU client installing too)
Also complete the distributed Appliacation Mapping under the Master Servers Host Properties (DAG to CAS and DAG to MBX Servers)
Hope this helps

swaraj_bhalerao · Answer

Hi Mark,
&nbsp;
Thankx for the information. I have completed the distributed Appliacation Mapping under the Master Servers Host Properties (DAG to CAS and DAG to MBX Servers).&nbsp; I am able to resolved all the hostnames from media server by running command bpclntcmd.
&nbsp;
I need clarification on this point :&nbsp;&nbsp;1.Ensure that hostname and IP of all Exchange nodes in DAG is set in local host files
&nbsp;
So i need to check and confirm the /etc/hosts entries of each DAG member has the entry of each DAG member??
or its related to media servers /etc/hosts file

mark_solutions · Answer

Make sure your media server can resolve them all correctly - so add to the host files on the Media Servers to be sure of things
You can setup and check the bpresolver log file on the DAG members to check further (usual place 
etbackup\logs\)

Forum Discussion

(39) client name mismatch

3 Replies

Related Content

Client Name mismatch(39) with EV agent

client name mismatch (39) DAG exchange

network protocol error (39)

LLT connections mismatch

DA client server mismatch 10SP4CHF1