The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP

One of the annoying issues that you may experience when you work with SharePoint Databases is

The rapid growth of the SharePoint Config Database transaction log (Full).

So you should regularly maintain the SharePoint_Config Database by taking a backup of the log files frequently to avoid the below-encountered error:

errorThe transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ (Microsoft SQL Server, Error : 9002)

The transaction log for database is full due to LOG_BACKUP 1

Note: When The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ error is encountered. No transaction or backup action can be performed on ‘SharePoint_Config’ database.


In this article, I’ll show How to avoid falling into this issue (SharePoint_Config Database log file is Full) by following the below steps:

Steps:

  1. Shrink the log file to reduce the physical file size.
  2. Take a Full database backup.
  3. Create an LOG_BACKUP.
  4. Create an LOG_BACKUP Maintenance Plan.

Continue reading The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP