Создание копии БД Failed to notify source server “server fqdn ” about the local truncation point.

https://social.technet.microsoft.com/Forums/Lync/en-US/ee80ee37-51a1-40b4-9cc2-41c8d81affce/failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713?forum=exchangesvravailabilityandisasterrecovery

 https://www.youtube.com/watch?v=6cONqvQx224

https://practical365.com/exchange-server/how-to-reseed-a-failed-database-copy-in-exchange-server-2013/

I tried adding another database thinking that this might be related to this single database and the results were the same. I did a quick research on the subject and most of the responses were that you should:

1. Dismount the database.
2. Run eseutil with the /mh parameters (more info here).

I had a lot of databases and dismounting the databases to run the utility was merely impossible even on a weekend, on the other hand as I was continuing my research I found a thread on Technet which mentions a long side to running the eseutil “moving the logs” to another directory so that they will get recreated and here it hit me!

What if I re-enable circular logging then try to update the database! Because since circular logging was enabled I am already missing on a lot of the transactions that were initially written on the database!

• I tried first hitting the update option but sadly I got the same error
• I tried hitting resume option which resulted again in the failed and suspended status then hit the update option again.
• AND IT WORKED :-D

https://msexchangeguru.com/2015/09/27/e2013-unable-to-create-database-copy/

Issue:

While creating a copy of the database on the 2^nd server, we got the following errors.

First Error

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server “server fqdn ” about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.

2^nd error

Failed to open a log truncation context to source server. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).

Resolution:

This is the issue with the old logs folder which was not in the sync.

For the 1^st error.

-Login to the source server

-Remove the 2^nd copy of the database

-Dismount the database

-Verify database is clean shutdown by running the command eseutil /mh driveletter:\database\database.edb

-Now rename the logs file folder to logs old.

-Mount the database

-Now the 1^st issue will be fixed.

 

For the 2^nd error.

-Login to the destination server where we are creating the 2^nd copy

-Now rename the logs and database file folder by adding old prefix.

-Add the 2^nd database copy.

-Now the 2nd issue will be fixed.

This environment was not backed up so there was a time when circular logging was enabled then disabled. After this one of the administrator messed up the database copies while expanding the C drive.