Exchange Server Unable to Add Database Copy

Our Exchange Server environment is important to our organization and for our Exchange Server environment to work uninterruptedly, it must run in an Exchange Server DAG environment.

We want to include a database located on an Exchange Server into the DAG by replicating a copy of the existing database to another Exchange Server that is a member of the Failover Cluster.

Exchange Server Gives Error While Adding Database to DAG Environment

Sometimes our Exchange Server database in the DAG environment may give errors such as the one below.

Unable to Add Database Copy

“The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: The specified database isn’t configured for replication and therefore cannot be used to perform seed operations”

When we examine the error we receive, we can see that the Exchange Server gave an error during the Seeding process.

Cause of Exchange Server The seeding operation failed Error

This mistake, Active Directory (AD) may be caused by problems with their replication. If more than one Domain Controller (DC) and between these DCs if you are using ConfigurationDomainController ve PreferredGlobalCatalog If the values ​​specified in the parameters are different, you may encounter this type of error.

Replication latency between configured domain controllers and the preferred global catalog can cause mailbox database operations to fail.

How to Fix Exchange Server The Seeding Operation Failed Error

To resolve the issue, it is recommended that you update your configurations to use the same DC/GC. You can statically configure the relevant settings on your Exchange Server with the following PowerShell command;

With this process, your Exchange Server environment StaticDomainControllers you will have provided the configuration.

Set-ExchangeServer –Identity <mailboxserver_name> -StaticDomainControllers <DC FQDN> -StaticGlobalCatalogs <DC FQDN> –StaticConfigDomainController <DC FQDN>

Warnings and Tips:

  • DC/GC'Setting static will solve the mentioned error. However, this configuration is active/passive. fail over This may cause some slowdowns in some cases. Allow your server approximately 30-40 minutes for these transitions to start working normally.
  • If the necessary replications do not occur and a passive database update is required, Exchange Control Panel (ECP) You can solve the problem by updating the passive database via.

Comment