x

Transactional logbackup failure

.on 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:30:00 AM Progress: 2014-07-28 10:30:02.62 Source: {4A248835-E31F-44AD-AAFC-645A837777B4} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp...".: 100% complete End Progress Progress: 2014-07-28 10:30:03.94 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 6% complete End Progress Progress: 2014-07-28 10:30:03.94 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 13% complete End Progress Progress: 2014-07-28 10:30:03.94 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 20% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 26% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 33% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 40% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 46% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 53% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 60% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 66% complete End Progress Progress: 2014-07-28 10:30:03.95 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 73% complete End Progress Progress: 2014-07-28 10:30:03.96 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 80% complete End Progress Progress: 2014-07-28 10:30:03.96 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 86% complete End Progress Progress: 2014-07-28 10:30:03.96 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 93% complete End Progress Progress: 2014-07-28 10:30:03.96 Source: Back Up Database (Transaction Log) Executing query "EXECUTE master.dbo.xp_create_subdir N'E:\Backup\Tr...".: 100% complete End Progress Progress: 2014-07-28 10:30:04.08 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [AbraEmployeeSelfService] TO DISK = N'...".: 100% complete End Progress Progress: 2014-07-28 10:30:04.21 Source: Back Up Database (Transaction Log) Executing query "BACKUP LOG [AbraHRMS_Live] TO DISK = N'E:\Backup...".: 100% complete End Progress Error: 2014-07-28 10:30:04.34 Code: 0xC002F210 Source: Back Up Database (Transaction Log) Execute SQL Task Description: Executing the query "BACKUP LOG [AbraHRMS_Sample] TO DISK = N'E:\Backu..." failed with the following error: "BACKUP LOG cannot be performed because there is no current database backup. BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultS... The package execution fa... The step failed.

What do I need to do to fix this error? All backups are generated in the designated area but there is the above error for the transactional log. Do I need to change the time of the schedule. Full backup is completed at 12:02 AM and Transactional log also starts at 12 AM. Do I change the time and that should fix the error?
more ▼

asked Jul 28 at 03:34 PM in Default

chitrarekha.saha gravatar image

chitrarekha.saha
666 24 38 46

Did you read the error in the text? BACKUP LOG cannot be performed because there is no current database backup...you have a database in FULL recovery that is missing a full backup.
Jul 28 at 03:49 PM Shawn_Melton
Yes, but full, differential and transactional log backup is successful.
Jul 28 at 04:02 PM chitrarekha.saha
(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first
Most likely there is some process is changing your database recovery mode from FULL to SIMPLE then back to FULL, thus breaking the log chain. Changing the time won't fix your problem because FULL and transaction log backups are don't interfere with each other. The FULL backup will include everything transaction log backed up while the FULL was running. So you need to find what changes your database recovery mode.
more ▼

answered Jul 29 at 02:04 AM

DenisT gravatar image

DenisT
1.5k 1 3

Consider following points to solve your issue

Check Database Backup Currently Finished it or not.

To Run Transaction Log Backup You have to take Database backup Full Once a Day.

When you have Changed Database Recover Mode then You have to take DB Backup Immediately.

Hope This Helps!!!!!!!!!!! Thanks
Jul 29 at 08:08 AM sqlqa
@sqlqa You don't have to run full backups once a day. You can mix and match all sorts of combinations successfully. You do have to have at least one full backup after a database has been switched from simple to full, but from there, there is no dependency chain between full backups and log backups.
Jul 29 at 11:51 AM Grant Fritchey ♦♦
I have about nine databases that is using one Transactional log backup maintenance plan and one databases is in simple recovery model. Is this causing the issue with the Transactional log error?
Jul 29 at 02:05 PM chitrarekha.saha
You cannot take a transaction log back of a database that is in SIMPLE recovery mode. So, if I understood your comment correctly, you need to exclude this one database from the transaction log backup plan. From the log above, it looks like this is the database that needs to be removed from the plan -- AbraHRMS_Sample.
Jul 29 at 02:48 PM DenisT

You now have no method to control the transaction log size on the AbraHRMS_Sample database. If you leave it in FULL recovery, you should take a full backup and start taking transaction log backups. If you do not want transaction log backups for this database, you should put it into the SIMPLE recovery model.

Would hate to see you come back in a few months to ask this question - http://ask.sqlservercentral.com/questions/23112/why-is-my-ldf-log-file-so-big-getting-bigger-bigge.html
Jul 29 at 07:20 PM KenJ
(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x597

asked: Jul 28 at 03:34 PM

Seen: 215 times

Last Updated: Jul 29 at 07:23 PM