Exchange DAG backup fails with Status 2 and Status 72

Article: 100054363
Last Published: 2022-11-10
Ratings: 1 0
Product(s): NetBackup & Alta Data Protection

Problem

Backup of Exchange DAG fails with "Status: 2" and "Status: 72: the client type is incorrect in the configuration database"

Error Message

Detailed Status shows the following:

Nov 9, 2022 2:51:55 PM - Info bpbrm (pid=221700) from client DAG1: TRV - BPRESOLVER has executed on server (EX01)

Nov 9, 2022 3:16:02 PM - Info bpresolver (pid=35084) done.  status: 2

Nov 9, 2022 3:16:02 PM - Error bpbrm (pid=221700) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup

Nov 9, 2022 3:16:02 PM - Info bpresolver (pid=35084) done. status: 72: the client type is incorrect in the configuration database

 

BPRESOLVER debug log shows:

13:46:40.026 [34136.27444] <2> [fsys\sql2] : DBG - NOT SQL Device Name: \\DAG1\Microsoft Information Store\* (../BEDSContext.cpp:163)
13:48:33.619 [34136.32356] <2> [fsys\shared] : DBG - ESE07 process not ready (../BEDSContext.cpp:163)
13:48:35.664 [34136.32356] <2> [fsys\shared] : DBG - ese command 23 timed out (../BEDSContext.cpp:163)
13:48:36.753 [34136.27444] <2> [fsys\shared] : DBG - ESE07 process not ready (../BEDSContext.cpp:163)
13:48:36.754 [34136.27444] <2> [fsys\ese] : DBG - [EseE14::GetAllNodes] ### EseProcess::GetAllNodes("DAG1") failed ... 0x80004005 (../BEDSContext.cpp:163)
13:48:36.755 [34136.27444] <2> [fsys\shared] : DBG - Monad RPC timeout 300000 (../BEDSContext.cpp:163)
13:48:36.755 [34136.27444] <2> [fsys\shared] : DBG - EseProcess::Init: OpenThreadToken successful (../BEDSContext.cpp:163)
13:48:36.756 [34136.27444] <2> [fsys\shared] : DBG - EseProcess::Init: WhoAmI - <Domain name\Account name> (../BEDSContext.cpp:163)
13:48:37.529 [34136.27444] <2> [fsys\ese] : DBG - [EseE14::GetTargetDatabaseCopyStatus] machine:DAG1 l database:* targetSite:null options:0x4 flags:2048 count:0 (../BEDSContext.cpp:163)
13:53:37.547 [34136.27444] <2> [fsys\shared] : DBG - ese command 19 timed out (../BEDSContext.cpp:163)
13:53:37.547 [34136.27444] <2> [fsys\shared] : DBG - GetTargetDatabaseCopyStatus returned ffffffff (../BEDSContext.cpp:163)
13:53:37.547 [34136.27444] <2> [fsys\ese] : DBG - Error (0xffffffff) !!! EseE14::GetTargetDatabaseCopyStatus("DAG1", "*") failed (../BEDSContext.cpp:163)
13:53:37.547 [34136.27444] <2> [fsys\ese] : DBG - [EseE14::ResolveDeviceName] Backup ... \DAG1\Microsoft Information Store\* => DAG1 ... 0xe0000391 (../BEDSContext.cpp:163)
13:53:37.547 [34136.27444] <16> rai_resolvePathName: Server failed to be found
13:53:37.549 [34136.27444] <4> populate_server_list_with_dag_nodes: Cannot populate server list for '\\DAG1\Microsoft Information Store\*'.
13:53:37.549 [34136.27444] <4> Resolver_Exchange::generate_TopologyList: Not part of a DAG

Cause

Even though the account was configured with all required permissions to backup Exchange with GRT, the account was not set as enabled for "Remote PowerShell"

Solution

Being logged on with the account configured with sufficient permissions, trying to run command

"Get-MailboxDatabaseCopyStatus"

to test PowerShell permissions on the account, the below error is seen on the Exchange Management Shell:

VERBOSE: Connecting to ex01

New-PSSession : [ex01] Processing data from remote server ex01 failed with the following error message: [ClientAccessServer=CAS01,BackEndServer=ex01,RequestId=7424105b-0a0d-4289-9039-22c58ee07f13,TimeStamp=11/9/2022 10:04:44 PM]

[AuthZRequestId=1a32b684-267e-4a0a-a1fb-3c1a26e266c6][FailureCategory=AuthZ-RemotePowerShellNotEnabledException]

Attempt to connect to this Exchange server was denied because account isn't enabled for Remote PowerShell. Exchange administrator can use the following command to enable your account

Set-User -RemotePowerShellEnabled 

For more information, see the about_Remote_Troubleshooting Help topic.

As per the above output, RemotPowerShell will need to granted to the account configured for Exchange GRT backups.

Was this content helpful?