Post reply

Transaction Log backup setup ok then continues to falls over

  • January 12, 2009 at 3:19 am

    #204861

    Hi there,

    I am having a problem with my transaction log backup. I have a full backup job running on the server to backup all databases to disk at 20.30. This job runs fine without a problem. I have then created a transaction log backup job to run every four hours to keep the ldf's down in size. I created both of the jobs as seperate jobs using the maintenance plan wizard.

    The problem is that I am able to get the transaction log back to run ok initially but then it stops running and the ldf files balloon and the server runs out of disk space!!

    In order to try and trouble shoot the problem i have tried to get it to do the transaction log backup on one database and this worked fine. We i tried another couple of databases it falls over. Here's the log file from the backup job:

    NEW COMPONENT OUTPUT

    Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3068

    Report was generated on "tyres".

    Maintenance Plan: Test Transaction Logs

    Duration: 00:00:24

    Status: Warning: One or more tasks failed..

    Details:

    Back Up Database Task (tyres)

    Backup Database on Local server connection

    Databases: XXX

    Type: Transaction Log

    Append existing

    Task start: 2009-01-12T10:02:24.

    Task end: 2009-01-12T10:02:48.

    Failed:(-1073548784) Executing the query "BACKUP LOG [XXX] TO DISK = N'F:\\Backup\\SQLMaintenancePlanBackup\\TransactionLogs\\XXXX_backup_200901121002.trn' WITH NOFORMAT, NOINIT, NAME = N'XXX_backup_20090112100224', SKIP, REWIND, NOUNLOAD, STATS = 10

    " failed with the following error: "Write on "F:\\Backup\\SQLMaintenancePlanBackup\\TransactionLogs\\XXX_backup_200901121002.trn" failed: 112(error not found)

    BACKUP LOG is terminating abnormally.

    10 percent processed.

    20 percent processed.

    30 percent processed.

    40 percent processed.

    50 percent processed.

    60 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Apologies if it is something obvious but i am new to SQL admin and seriously struggling with this backup job. Driving me crazy!!!

    Any ideas what is causing the problem?

    Thanks

  • January 12, 2009 at 3:40 am

    #925160

    Error 112 usually indicates that there's not enough space on the disk.

    [font="Verdana"]Markus Bohse[/font]

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

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