(39) client name mismatch

[Swaraj_Bhalerao]

Exchange DAG backup is failing with error code 39.client name mismatch.

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  (39)
 

Exhange 2010, Netbackup Version:7.1.0.4

Please find the output of bppllist vrm-c-exchange -U

Policy Name:       vrm-c-exchange

  Policy Type:         MS-Exchange-Server
  Active:              yes
  Effective date:      11/21/2012 03:31:49
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     90000
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Exchange Source passive db if available: yes
  Exchange 2010 Preferred Server:  phx-exch-mbx-01 phx-exch-mbx-02  Application Discovery:      no
  Discovery Lifetime:      0 seconds

  Granular Restore Info:  no
  Ignore Client Direct:  no
  HW/OS/Client:  Windows-x64   Windows2008   dag1

  Include:  Microsoft Exchange Database Availability Groups:\

  Schedule:          Differential-Inc
    Type:            Differential Incremental Backup
    Frequency:       every 1 day
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:

  Schedule:          Full
    Type:            Automatic Backup
    Frequency:       every 7 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       std-full-1mo
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     1
    Daily Windows:

Please suggest.

Thanks & Regards,

Ganesh Bhalerao

[Mark_Solutions]

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&pmv=print&impressions=&viewlocale=&id=TE...

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]

Hi Mark,

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).  I am able to resolved all the hostnames from media server by running command bpclntcmd.

I need clarification on this point :  1.Ensure that hostname and IP of all Exchange nodes in DAG is set in local host files

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]

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 \netbackup\logs\)