client name mismatch  (39) DAG exchange

In addition to the basic information requested by Marianne...

• What are the versions of NetBackup on servers and clients? What Exchange-related EEBs do you have installed?
• What is the version of Exchange?
• If Exchange is 2013 or later, is the DAG name resolvable in the DNS to an IP address? Seems to be yes, since the error came from bpcd on the DAG.
• As always, when job details or bpbrm log reports an error from a client process, look at the client log.

The links Marianne provided are a little old. One thing you should not have to do if you have NetBackup 7.7.3 or later, is to define your DAG and Exchange servers in any hosts files to compensate for an IP-less DAG.

By the time a backup job gets to bpbrm, the client name should not be a DAG name anymore. And it isn't:

>Info nbjm (pid=14779) starting backup job (jobid=754) for client SIMAOSVMBX01

>bpbrm (pid=72535) [PROXY] Connecting host: simaobkp01

Why two different client names, and why an apparent DAG name in the error?

>bpbrm (pid=72535) bpcd on DAG-SIMAO exited with status 39: client name mismatch.

There's a lot to be confused about here. Please provide the requested details.

hi Marianne

Names of DAG members

SIMAOSVMBX01, SIMAOSPMBX03, SIMAOSVMBX04.

Name of Virtual (DAG) 

DAG-SIMAO

bppllist vrm-c-exchange -U

olicy Name: EXCHANGE_BKP_FM

Policy Type: MS-Exchange-Server
Active: yes
Effective date: 05/05/2018 07:43:36
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: stu_disk_simaobkp01
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 DAG Preferred Server: (none defined)
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)

Granular Restore Info: yes
Ignore Client Direct: no
Use Accelerator: no
HW/OS/Client: Windows-x64 Windows DAG-SIMAO

Include: NEW_STREAM
Microsoft Exchange Database Availability Groups:\

Schedule: Full
Type: Automatic Backup
Calendar sched: Enabled
Included Dates-----------
Saturday, Week 5
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 25 (expires immediately)
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:
Saturday 20:00:00 --> Friday 00:00:00

yes NBU is stalled on all DAG member , all firewall are off and resolution work fine