NetBackup Microsoft Exchange "Standalone" Server Backup fails with Status Code 2.

Problem

NetBackup Exchange "Standalone" Server Backup fails with Status Code 2

Error Message

The following errors are shown in the NetBackup Job details :-

Sep 14, 2020 11:38:43 PM - Info nbjm (pid=20048) starting backup job (jobid=1812431) for client XXXXXX, policy Test_rdc_exch_dag1, schedule Full
Sep 14, 2020 11:38:43 PM - Info nbjm (pid=20048) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=1812431, request id:{53824470-F6B5-11EA-8478-B6552B3EC118})
Sep 14, 2020 11:38:43 PM - requesting resource  XXX
Sep 14, 2020 11:38:43 PM - requesting resource XXXX.NBU_CLIENT.MAXJOBS.XXXX
Sep 14, 2020 11:38:43 PM - requesting resource

 EXCHANGE_RESOLVER. XXXXXX
Sep 14, 2020 11:38:43 PM - granted resource  XXXXX.NBU_CLIENT.MAXJOBS. XXXXXXX
Sep 14, 2020 11:38:43 PM - granted resource  EXCHANGE_RESOLVER.XXXXXXXX
Sep 14, 2020 11:38:44 PM - estimated 0 kbytes needed
Sep 14, 2020 11:38:44 PM - begin Parent Job
Sep 14, 2020 11:38:44 PM - begin Exchange14 Resolver: Start Notify Script
Sep 14, 2020 11:38:44 PM - Info RUNCMD (pid=23070) started
Sep 14, 2020 11:38:44 PM - Info RUNCMD (pid=23070) exiting with status: 0
Operation Status: 0
Sep 14, 2020 11:38:44 PM - end Exchange14 Resolver: Start Notify Script; elapsed time 0:00:00
Sep 14, 2020 11:38:44 PM - begin Exchange14 Resolver: Step By Condition
Operation Status: 0
Sep 14, 2020 11:38:44 PM - end Exchange14 Resolver: Step By Condition; elapsed time 0:00:00
Sep 14, 2020 11:38:44 PM - begin Exchange14 Resolver: Read File List
Operation Status: 0
Sep 14, 2020 11:38:44 PM - end Exchange14 Resolver: Read File List; elapsed time 0:00:00
Sep 14, 2020 11:38:44 PM - begin Exchange14 Resolver: Resolver Discovery
Sep 14, 2020 11:38:44 PM - started process bpbrm (pid=23076)
Sep 14, 2020 11:38:45 PM - Info bpbrm (pid=23076) "Client node name" is the host to restore to
Sep 14, 2020 11:38:45 PM - Info bpbrm (pid=23076) reading file list for client
Sep 14, 2020 11:38:48 PM - Info bpbrm (pid=23076) client_pid=16688
Sep 14, 2020 11:38:48 PM - Info bpbrm (pid=23076) from client "Client node name": TRV - BPRESOLVER has executed on server (XXXXX)
Sep 14, 2020 11:39:01 PM - Info bpresolver (pid=16688) done.  status: 2
Sep 14, 2020 11:39:01 PM - Error bpbrm (pid=23076) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup
Sep 14, 2020 11:39:01 PM - Info bpresolver (pid=16688) done. status: 72: the client type is incorrect in the configuration database
Operation Status: 2
Sep 14, 2020 11:39:01 PM - end Exchange14 Resolver: Resolver Discovery; elapsed time 0:00:17
Sep 14, 2020 11:39:01 PM - begin Exchange14 Resolver: Stop On Error
Operation Status: 0
Sep 14, 2020 11:39:01 PM - end Exchange14 Resolver: Stop On Error; elapsed time 0:00:00
Sep 14, 2020 11:39:01 PM - begin Exchange14 Resolver: End Notify Script
Sep 14, 2020 11:39:01 PM - Info RUNCMD (pid=23195) started
Sep 14, 2020 11:39:01 PM - Info RUNCMD (pid=23195) exiting with status: 0
Operation Status: 0
Sep 14, 2020 11:39:01 PM - end Exchange14 Resolver: End Notify Script; elapsed time 0:00:00
Operation Status: 2
Sep 14, 2020 11:39:01 PM - end Parent Job; elapsed time 0:00:17
none of the requested files were backed up  (2)

Cause

The issue is caused because the Node Name is used in the Policy Client Tab of an Exchange Backup.and the below directive exists in the Policy Selections Tab

 "Microsoft Exchange Database Availability Groups:\"
 

Solution

For a Standalone Exchange Server Backup

We cannot use the DAG name and Directive as "Microsoft Exchange Database Availability Groups:\"

• Use the  Stand-alone Exchange Server Node name in the Policy > Client's tab 
• Use the directive in the Policy > Selection's Tab > "Microsoft Information Store:\".