cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange 2013 DAG backup

AlexeyF
Level 4

Hi

I want to configure Exchange backup using the dag address but I get this error as if something is configured incorrectly:

You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup
17 janv. 2023 17:49:45 - Info bpresolver (pid=14640) done. status: 72: the client type is incorrect in the configuration database

Could not find any mismatch with the documentation.

Client is dag address DEVDAG01.domain

Backup selection is Microsoft Exchange Database Availability Groups:\DEVDAG01.domain\Microsoft Information Store\DAG01DB004STD

use snapshot is enabled

in preferred list I've included all the servers that store this DAG.

What else could I verify?

PS: if I indicate a single exchange server in the clients tab the backup is successful.

1 ACCEPTED SOLUTION

Accepted Solutions

AlexeyF
Level 4

We've found found the stumbling block thanks to the Veritas support and debugging via bpresolver log.

the name that we've configured the client with was in the backup network ie exch1.backup.local ad the dag didn't know that ame because exchange servers were registered there as exch1.prod.local

After reconfiguring with proper names the error has disappeared. 

 

 

View solution in original post

7 REPLIES 7

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

the issue seems to be pretty googleable, have you checked these hints? I think the first one could be the likely cause.

https://www.veritas.com/support/en_US/article.100054363

https://www.veritas.com/support/en_US/article.100007718

https://www.veritas.com/support/en_US/article.100048910

Regards

M.

thank you Michal for the links.

Unfortunately none of them corresponds to our case: user is granted these priviledges, Exchange Management Shell is installed and the client name is the name of the DAG and not a server name.

 

Faysal
Level 3
Partner Accredited

Hi ,

Try to create policy through webui.

 https://masterserver/webui/login

Regards,

Faysal

 

AlexeyF
Level 4

@Faysal GUI doesn't propose me MS-Exchange policy type unfortunately. 

NurgulG
Level 3

Hi,

Did you add all Exchange servers in Master Server Properties -> Distributed Application Restore Mapping?  Please add or check exchange credential each node can you check this guide?

https://www.veritas.com/support/en_US/doc/19475139-149474632-0/v26185698-149474632

NurgulG_0-1674198615779.png

Best Regards

 

 

@NurgulG yes, did it.

AlexeyF
Level 4

We've found found the stumbling block thanks to the Veritas support and debugging via bpresolver log.

the name that we've configured the client with was in the backup network ie exch1.backup.local ad the dag didn't know that ame because exchange servers were registered there as exch1.prod.local

After reconfiguring with proper names the error has disappeared.