Exchange transaction logs more recent than last backup time on a database

Question

Exchange transaction logs more recent than last backup time on a database

Joseph Larrew 0

I have an Event ID 2137 for each database copy on this server that has all passive copies. It is the server targeted by the backup solution (Hycu) for backing up all the databases for this DAG. The event reads as follows:

RPC request to the Microsoft Exchange Information Store service for log truncation failed for database <DB Name><server name>. Error: Failed to notify source server '<another server in the DAG>' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.

I think it's because the oldest transaction log is from January, but the database in this particular instance was last fully backed up in December (per Exchange, but not per Hycu). Exchange is looking for transaction logs back in December that don't exist or something. Any ideas on how to resolve this?

Aholic Liang-MSFT 13,886 Reputation points Microsoft External Staff

2023-02-17T07:57:55.03+00:00

Hi @Joseph Larrew ,

Just wondering if you have tried Andy's suggestions?

Did the above method work for you?

If the reply was helpful, you can click the "Accept Answer" button under this post so that other's with similar question can benefit from this thread as well.

It is also an encouragement for respondents to provide quality helpful answers.

2 answers

Your answer

Aholic Liang-MSFT 13,886 Reputation points Microsoft External Staff

2023-02-17T07:57:55.03+00:00

Hi @Joseph Larrew ,

Just wondering if you have tried Andy's suggestions?

Did the above method work for you?

If the reply was helpful, you can click the "Accept Answer" button under this post so that other's with similar question can benefit from this thread as well.

It is also an encouragement for respondents to provide quality helpful answers.

Answer 1

Andy David - MVP 157.9K MVP Volunteer Moderator

Can you backup the active copy of each database instead?

Another option would be to enable circular logging and see if that removes them all.

CAUTION: If you do this, you must take a full backup before and after, then disable circular logging afterward if it clears the logs

Alternatively, remove the logs manually, but CAUTION again and NOT supported:

https://social.technet.microsoft.com/Forums/windows/en-US/79c8f5b9-6d05-4d0e-90d4-5854e9d72639/how-to-manual-delete-the-transaction-logs?forum=exchangesvrgenerallegacy

Joseph Larrew 0 Reputation points

2023-02-14T20:59:58.1533333+00:00

We ended up using Diskshadow to trick exchange into thinking the DBs had been backed up. https://www.msp360.com/resources/blog/exchange-truncate-logs/

Now that the logs are truncated, I'm going to run another full backup to see if it successfully updates the database LastFullBackup attribute.
Joseph Larrew 0 Reputation points

2023-02-14T21:53:31.1433333+00:00

We had not been able to get the backup solution to get Exchange to believe it had been backed up. The backup solution would say, from its perspective, that the backup was successful, but Exchange still wasn't showing any updated info on the database.

Answer 2

Rodrigo de Medeiros Silva 5

https://notes.doodzzz.net/2017/01/30/microsoft-exchange-server-2013-dag-failed-to-notify-source-server-about-the-local-truncation-point/

Share via

Exchange transaction logs more recent than last backup time on a database

2 answers

Your answer