none
Ошибка при создании копии базы данных Exchange 2016 CU12 RRS feed

  • Общие обсуждения

  • Добрый день,

    Имеется: среда состоящая из 2 серверов, объеденных в кластер. 

    В какой-то момент времени перестало работать создание копий почтовых баз. При попытке завершается ошибкой:

    Не удалось выполнить операцию заполнения. Ошибка: The Microsoft Exchange Replication service may not be running on server EXCH02 Error: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_RpccGetDbSeedStatus

    После поиска в гугле: https://support.microsoft.com/en-us/help/4488398/the-microsoft-exchange-replication-service-may-not-be-running-on-serve - были установлены на оба сервера все обновления и CU12, на CU10 и CU11 та же беда.

    Информация из логов серверов:

    EXCH01:

    Active copy of database 'DB2' on this server is now starting a seed for the passive copy on server EXCH02.

    Microsoft.Exchange.Store.Worker (19300) Opening a backup context by server EXCH01 at time 12:51:04 PM on 3/28/2019. 

    Information Store - DB2 (19300,D,0,15.01.1713.001) DB2: An internal copy (for seeding or analysis purposes) is starting. The streaming ESE backup APIs are being used for the transfer method. 

    Information Store - DB2 (19300,D,0,15.01.1713.001) DB2: Starting the copy or backup of the file O:\DB2.edb (size 211968 Mb). 

    Microsoft.Exchange.Store.Worker (19300) Data transfer method is shared memory (1024 KB). 

    Process:w3wp PID:9136 Thread:94] Successfully populated ServiceTopology. Reason to populate ServiceTopology = RefreshTimeout

    Information Store - DB2 (19300,D,0,15.01.1713.001) DB2: Ending the internal copy (for seeding or analysis purposes) of the file O:\DB2.edb. Not all data in the file has been read (read 318767104 bytes out of 222264590336 bytes). 

    Information Store - DB22 (19300,D,0,15.01.1713.001) DB22: The internal database copy (for seeding or analysis purposes) has been stopped because it was halted by the client or because the connection with the client failed. 

    Microsoft.Exchange.Store.Worker (19300) Closing the backup connection that was originally opened by server EXCH01 at time 12:51:04 PM on 3/28/2019. 

    Seed-from-active for database 'DB2' to the passive copy on server EXCH02 completed.

    Current User: 'S-1-5-21-43527209-********-3031047978-****'
    Exchange Control Panel finished an Async web request in the thread 52.
    Command: 'AddDatabaseCopy'

    EXCH02

    Microsoft Exchange Information Store service will perform an internal schema upgrade on (Folder) (6674184f-26db-4ea6-b034-7cc8bd6f6833[1]-4A915426). The upgrade will bring the version from (0.143) to (0.144).

    Microsoft Exchange Information Store service has completed an internal schema upgrade on (Folder) (6674184f-26db-4ea6-b034-7cc8bd6f6833[1]-4A915426). The upgrade has brought the version from (0.143) to (0.174).

     

    Watson report about to be sent for process id: 32336, with parameters: E12, c-RTL-AMD64, 15.01.1713.005, msexchangerepl, unknown, M.E.C.S.A.<>c__DisplayClass10_0.<ResolveFqdn>b__0, M.E.C.Shared.AmGetFqdnFailedNotFoundException, 2a96-dumptidset, unknown.
    ErrorReportingEnabled: False

    The mailbox b3215a21-78f1-****-****-950608cc575d on database c34d658b-****-****-bffc-a430235c49f4 is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.

    The Microsoft Exchange Replication service is starting.

    Microsoft Exchange Server Locator Service successfully started on 'net.tcp://exch02:64337/Exchange.HighAvailability'.

    Microsoft Exchange Replication service has been successfully initialized.

    Подскажите почему падает служба репликации? 

    28 марта 2019 г. 11:29