question

MikhailFirsov-1277 avatar image
0 Votes"
MikhailFirsov-1277 asked MikhailFirsov-1277 commented

Exchange Server 2019 does not truncate logs V2

Hello,

I've already asked the question on log truncation here and found the similar question here.

Although the answer was "Enable than disable circullar logging" it sounds more like a workaround rather than odinary way for log truncation.

Now after ~2.5years I see exactly the same problem in Exchange 2019 CU12 - can anyone tell me why can this happen in different versions of Exchange Server? Waiting for log truncation after full backup for ~2-3 days or manually truncating the logs seems a bit (mildly speaking) weird for Exchange Server (especially for the Enterprise edition).

The event stating the log truncation was requested:
202343-q1.png

Regards,
Michael


office-exchange-server-administrationoffice-exchange-online-itprooffice-exchange-server-mailflowoffice-exchange-server-connectivityoffice-exchange-server-ha
q1.png (25.7 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MikhailFirsov-1277 ,

Can you find some event ID 224 or 225 generated with the event ID 2046?

And do you have a DAG deployment?

0 Votes 0 ·

Hi AholicLiang-MSFT,

1) No

2) Yes

0 Votes 0 ·

As far as I understand the key point in this problem is that the "...next log generation" is NOT created:
203117-q2-1.png

According to the timing on the screenshot above the new log generation had to be created after ~11:56:39 AM (backup was started at 11:31 AM), but Exchange continued using the old log generation - am I getting it right?

Regards,
Michael


0 Votes 0 ·
q2-1.png (132.4 KiB)

0 Answers