Maintenance plan failing

  • Hi,

    I have 2 drives where db full backups( D:) and log backups(E:) are created for weekly once Maintenance plan. 
    The problem is E drive has space and good with backups but the job failed due to insufficient space in log backups drive. 
    Sample Error for 2 specific user db's :DESCRIPTION:The transaction log for database 'DBNAME' is full due to 'LOG_BACKUP'.

    Now, how to make this work. could you please help with step by step process or hints. Thanks.

  • sizal0234 - Wednesday, November 14, 2018 2:03 PM

    Hi,

    I have 2 drives where db full backups( D:) and log backups(E:) are created for weekly once Maintenance plan. 
    The problem is E drive has space and good with backups but the job failed due to insufficient space in log backups drive. 
    Sample Error for 2 specific user db's :DESCRIPTION:The transaction log for database 'DBNAME' is full due to 'LOG_BACKUP'.

    Now, how to make this work. could you please help with step by step process or hints. Thanks.

    The error says that, your transaction log file is getting full because of lack of log backup taken.
    You can check - select log_reuse_wait_desc,* from sys.databases  - Shrink with initial size and schedule a regular log backup to maintain the growth.

    https://www.sqlserverblogforum.com/dba/database-transaction-log-file-full-in-the-full-recovery-model/

    https://www.sqlserverblogforum.com/dba/drive-space-check-sql-server-steps-and-scripts/

    Muthukkumaran Kaliyamoorthy
    https://www.sqlserverblogforum.com/

  • sizal0234 - Wednesday, November 14, 2018 2:03 PM

    Hi,

    I have 2 drives where db full backups( D:) and log backups(E:) are created for weekly once Maintenance plan. 
    The problem is E drive has space and good with backups but the job failed due to insufficient space in log backups drive. 
    Sample Error for 2 specific user db's :DESCRIPTION:The transaction log for database 'DBNAME' is full due to 'LOG_BACKUP'.

    Now, how to make this work. could you please help with step by step process or hints. Thanks.

    It's hard to say for sure but if it's the size of the logs itself, it could be that you just need to backup your logs more often. That can help keep the size of the log more reasonable.

    Sue

  • Can you clear some space on your drives....like delete or move older files to tape..Then once you have enough space i would take a full backup and that should commit the logs as well if not take a full log back up also.  Then shrink the logs and as Sue_H was saying increase the frequency of the log backup and that should help in your scenario.  good luck.

    DHeath

  • Thanks all, found the root cause, the problems was the THIRD party software is also taking FULL & DIFF but not TRUNCATING the logs. Now, the issue is the SQL native backups via maintenance plan were disabled due to CONFLICT errors with third party software.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply