Exchange 2019 copy of database and more

%3CLINGO-SUB%20id%3D%22lingo-sub-1200795%22%20slang%3D%22en-US%22%3EExchange%202019%20copy%20of%20database%20and%20more%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1200795%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Community%2C%20i%20have%20a%20problem%2C%3C%2FP%3E%3CP%3EI%20have%20a%20Exchange%202019%20with%20a%20DAG%20(only%202%20servers%20on%20it)%3C%2FP%3E%3CP%3EMy%20problem%20is%20that%20the%20database%20copy%20is%20on%20Failed%20And%20Suspended%20Status%20%2C%20i%20remember%20that%20to%20fix%20it%20on%202016%20and%202013%20we%20can%20stop%20the%20search%20service%20and%20update%20de%20catalog%2C%20but%20this%20in%202019%20does%20not%20work.%3C%2FP%3E%3CP%3EThats%20my%20first%20problem%2C%20second%20i%20don%20%3Dt%20know%20why%20but%26nbsp%3B%20migration%20only%20works%20from%20console%20not%20in%20the%20web%20console%20any%20bode%20help%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1200795%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1687702%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202019%20copy%20of%20database%20and%20more%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1687702%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77947%22%20target%3D%22_blank%22%3E%40Jos%C3%A9%20Leonardo%20Ovalles%20Jimenez%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EWhat%20you%20describing%20as%20a%20solution%20is%20actually%20an%20approach%20to%20fix%20Content%20Index%2C%20not%20the%20replication%20of%20the%20databases.%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20could%20be%20variety%20of%20reasons%20why%20the%20replication%20would%20fail.%20The%20following%20command%20should%20assist%20with%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fupdate-mailboxdatabasecopy%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eresuming%3C%2FA%3E%26nbsp%3Breplication.%26nbsp%3B%20Have%20a%20look%20at%20the%20official%20approach%20to%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhigh-availability%2Fmanage-ha%2Fmanage-database-copies%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Emanage%3C%2FA%3E%20database%20copies.%3CBR%20%2F%3EProviding%20the%20errors%20showing%20in%20the%20logs%20for%20the%20reason%20of%20failure%2C%20should%20assist%20with%20identifying%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

Hello Community, i have a problem,

I have a Exchange 2019 with a DAG (only 2 servers on it)

My problem is that the database copy is on Failed And Suspended Status , i remember that to fix it on 2016 and 2013 we can stop the search service and update de catalog, but this in 2019 does not work.

Thats my first problem, second i don =t know why but  migration only works from console not in the web console any bode help?

1 Reply
Highlighted

@José Leonardo Ovalles Jimenez 
What you describing as a solution is actually an approach to fix Content Index, not the replication of the databases.

There could be variety of reasons why the replication would fail. The following command should assist with resuming replication.  Have a look at the official approach to manage database copies.
Providing the errors showing in the logs for the reason of failure, should assist with identifying the problem.