1

I have Availability Group of 3 servers, and transaction log backups for databases in Availability Group are taken on a secondary replica, each 1 minute

It was working like this for several months

Now MSDB on this secondary replica is 6 GB data file size (mdf) and is only 4% full and log file size is 14.2 GB (ldf) and is 7% full

I can only remember that I made MSDB 500 MB both data and log files in the beginning when server was setup...

I thought log file grew because of often transaction log backups and FULL recovery mode - but no, MSDB has SIMPLE recovery mode on that server

So it left me wondering, what caused both data and log file growth for MSDB ?

Improve this question

1 Answer 1

Reset to default
1

For me, large growths in MSDB are from adding and deleting the table entries within the backupset tables. Do you have a history purge or anything running?

Improve this answer
1
  • Yep weekly below procedures are run: EXEC sp_cycle_errorlog EXEC msdb.dbo.sp_cycle_agent_errorlog -- below SPs run to remove history older than 2 weeks EXEC msdb.dbo.sp_delete_backuphistory EXEC msdb.dbo.sp_purge_jobhistory EXEC msdb.dbo.sysmail_delete_mailitems_sp EXEC msdb.dbo.sysmail_delete_log_sp
    – Aleksey Vitsko
    Feb 6, 2020 at 15:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.