Post reply

T-log backup clean-up task completing, but giving Error: 18204,Severity: 16, State: 1

  • March 29, 2010 at 6:55 am

    #219920

    I've got a server running 2005 with two user databases. Each database has a maintenance plan that backups the transaction logs up hourly and cleans up any t-logs older than 3 days.

    On this server, for just this one database I'll get the following error in the sql log every so often (couple of days) right after the t-log backup:

    03/28/2010 23:00:01,Backup,Unknown,Log was backed up. Database: SES_Log,creation date(time): 2009/10/20(10:23:13),first LSN: 24:623:1,last LSN: 24:623:1,number of dump devices: 1,device information: (FILE=1,TYPE=DISK: {'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LOGS\SES_Log\SES_Log_backup_201003282300.trn'}). This is an informational message only. No user action is required.

    03/28/2010 22:00:13,spid79,Unknown,BackupDiskFile::OpenMedia: Backup device 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LOGS\SES_Log\SES_Log_backup_201003252200.trn' failed to open. Operating system error 2(The system cannot find the file specified.).

    03/28/2010 22:00:13,spid79,Unknown,Error: 18204,Severity: 16,State: 1.

    03/28/2010 22:00:13,Backup,Unknown,Log was backed up. Database: SES,creation date(time): 2009/10/20(10:23:12),first LSN: 34:4931:1,last LSN: 34:4937:1,number of dump devices: 1,device information: (FILE=1,TYPE=DISK: {'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LOGS\SES\SES_backup_201003282200.trn'}). This is an informational message only. No user action is required.

    03/28/2010 22:00:13,Backup,Unknown,Log was backed up. Database: SES_Log,creation date(time): 2009/10/20(10:23:13),first LSN: 24:623:1,last LSN: 24:623:1,number of dump devices: 1,device information: (FILE=1,TYPE=DISK: {'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\LOGS\SES_Log\SES_Log_backup_201003282200.trn'}). This is an informational message only. No user action is required.

    I've checked the path that it's looking for and it's right - it's just that transaction log isn't there anymore. The job doesn't fail, it just throws that error. Any ideas? Should I just ignore it?

    Tks.

  • March 29, 2010 at 3:38 pm

    #1141771

    Run the following and let us know this info.

    SELECT SERVERPROPERTY('EDITION');

    SELECT SERVERPROPERTY('PRODUCTLEVEL');

    SELECT SERVERPROPERTY('PRODUCTVERSION');

    Does that filename show up in your msdb.dbo.backupfile table?

    Is that file present on the share?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • March 30, 2010 at 5:24 am

    #1142072

    Standard Edition

    SP3

    9.00.4035.00

    The file in question doesn't show up in the msdb.dbo.backupfile table but I wouldn't expect it to. It's a .trn file - a backup of the transaction log, not the actual transaction log.

  • March 30, 2010 at 11:59 am

    #1142529

    Mistype there, sorry.

    Do you have matching LSNs in the backupset table that also match the backup_start_date and backup_finish_date?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

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

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