. Hola a todos Estoy Tratando de Copiar las bases de Datos de Buzones de Exchange 2013 Llegue Cuando El Estado de la copia con el comando get-MailboxDatabaseCopyStatus  error tengo el siguiente:  [PS] C: \ Windows \ system32> Get-MailboxDatabaseCopyStatus * Nombre Estado CopyQueue ReplayQueue LastInspectedLogTime Contentin                                                               Longitud Longitud Estado ---- ------ --------- ----------- ------------- ----- - --------- DAG_DB001_Nivel0 \ PROBMMCDTEXC001 Error 11707 0                                   DAG_DB002_Nivel1 \ PROBMMCDTEXC002 Error 11585 0                                   IncomingLogCopyingNetwork: {PROBMMCDTEXC002, ReplicationDagNetwork01, error de la ONU ha Producido Durante la Comunicacin                                         . Con El Servidor 'PROBMMCDTEXC002' Error: No Se Puede Escribir Datos en el transporte de                                         Conexin: Con La Conexin establecida FUE abortada Por software el en su Anfitrin                                         . Mquina} ? Cualquier del Sugerencia Saludos.

Hello everyone

Trying to solve the problem ran the following command update-MailboxDatabaseCopy Database -Identity \ MBX2 -DeleteExistingfiles

but it generates the following error message.

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: An error occurred while Communicating with server 'PROBMMCDTEXC002'. Error: Unable to read data from the transport connection: A connection Attempt failed Because the connected party did not answer-Properly after a period of time, or established connection failed Because connected host has failed to respond.

i appreciate your collaboration

• Edited by apolo91 Tuesday, April 07, 2015 9:22 PM

Hi,

Based on this error, I suggest to manually seed the databases by copying the databases over to the passive node.

Or try the following method.

• Remove the server from the DAG with this command:

Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer ServerName ConfigurationOnly

• Then did a node eviction from the Windows Failover Cluster:

Import-Module FailoverClusters

Get-ClusterNode EX2 | Remove-ClusterNode Force

• Then mounted the DB's outside the DAG
• Then built a new DAG from scratch, made new DB's and started a migration of the users from the evicted node to the new DAG.

Similar thread:

https://social.technet.microsoft.com/Forums/windows/en-US/5f975863-fd85-4d88-9df6-739d320f7b54/database-seeding-failed-as-exchange-dr-side

Best Regards.