If it happens that a database copy in a DAG is faulty, it usually helps to copy the database again (reseed). To initiate the process, the replication of the database to the faulty copy must first be stopped:
Suspend-MailboxDatabaseCopy -Identity "MailboxDatabase\ServerName"
The "-Identity" parameter is made up of the database name and the server name of the defective copy. If the database MBDB01 on EXSRV02 is faulty, the command must therefore be
Suspend-MailboxDatabaseCopy -Identity "MBDB01\EXSRV02"
are.
Once the copy has been stopped, the reseed can be carried out:
Update-MailboxDatabaseCopy -Identity "MailboxDatabase\Servername" -DeleteExistingFiles
The "-Identity" parameter is again composed as described above. "-DeleteExistingFiles" triggers a complete reseed without retaining any existing files. Depending on the size of the database, the process can of course take some time.
