Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Backups
»
Transaction Log Backup Problem
11 posts, Page 1 of 2
1
2
»»
Transaction Log Backup Problem
Rate Topic
Display Mode
Topic Options
Author
Message
Bob Shaw
Bob Shaw
Posted Tuesday, June 02, 2009 1:54 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:34 AM
Points: 45,
Visits: 174
Im trying to perform a transaction log backup to the same *.bak file holding the Full Database Backup. Im getting this error "BACKUP LOG cannot be performed because there is no current database backup."
I opened the backup file to view its contents and the the database is in there as a FULL backup.
When the database backups run it's marking the expiration date as 7 days from the execution date. I'm also backing up the master and msdb in the same backup file.
The backup order goes like this:
1. master (full backup)
2. msdb (full backup)
3. Our Application Database. ( full backup unless the database name is found in the backup file then it uses a Transaction Log Back instead)
Anyone else run into this situation? Is it possible to store a FULL and Transaction Log backup in the same Backup File?
Post #727696
Lynn Pettis
Lynn Pettis
Posted Tuesday, June 02, 2009 2:20 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 7:10 PM
Points: 21,588,
Visits: 27,380
Bob Shaw (6/2/2009)
Im trying to perform a transaction log backup to the same *.bak file holding the Full Database Backup. Im getting this error "BACKUP LOG cannot be performed because there is no current database backup."
I opened the backup file to view its contents and the the database is in there as a FULL backup.
When the database backups run it's marking the expiration date as 7 days from the execution date. I'm also backing up the master and msdb in the same backup file.
The backup order goes like this:
1. master (full backup)
2. msdb (full backup)
3. Our Application Database. ( full backup unless the database name is found in the backup file then it uses a Transaction Log Back instead)
Anyone else run into this situation? Is it possible to store a FULL and Transaction Log backup in the same Backup File?
The error you have received indicates that a full backup of the database needs to be accomplished before you can run a transaction log backup of the database. Have you recently changed the recovery model of the database in question?
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #727719
Bob Shaw
Bob Shaw
Posted Tuesday, June 02, 2009 2:37 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:34 AM
Points: 45,
Visits: 174
No, the database isnt changing. The backup is running in a application and for troubleshooting the problem.
I deleted the backup file so a new one will be created when the application runs.
Ran the application to create a backup.
Checked the backup file contents to make sure the database backup is in the backup file.
Then I ran the application backup routine again so it will perform a TL backup.
I still get the error. The application is perform the merge replication sync so the backup execute before each sync attempt. Thats why Im trying to use TL backups so the backup file size doesnt get out of hand and to be able to restore to a specific time.
Post #727728
Lynn Pettis
Lynn Pettis
Posted Tuesday, June 02, 2009 2:45 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 7:10 PM
Points: 21,588,
Visits: 27,380
Verify the recovery model of the database. Also, run this query: select * from msdb.dbo.backupset where backup_start_date > '20090602'
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #727737
Bob Shaw
Bob Shaw
Posted Tuesday, June 02, 2009 3:07 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:34 AM
Points: 45,
Visits: 174
Recover model is set to FULL and the query you gave me pulls 66 records and the database in question is in the results.
Post #727748
Lynn Pettis
Lynn Pettis
Posted Tuesday, June 02, 2009 3:30 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 7:10 PM
Points: 21,588,
Visits: 27,380
What is the value of the is_copy_only column?
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #727763
Bob Shaw
Bob Shaw
Posted Wednesday, June 03, 2009 8:29 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:34 AM
Points: 45,
Visits: 174
the value in that column is 0.
Post #728250
David Webb-CDS
David Webb-CDS
Posted Thursday, June 04, 2009 9:58 AM
SSC Eights!
Group: General Forum Members
Last Login: Yesterday @ 10:16 AM
Points: 823,
Visits: 5,664
Is there a chance that the full backup procedure does an explicit truncate on the log at some point after the backup is taken? It would invalidate the use of the full backup as a staring point for rolling forward with the logs. Not a very likely scenario, but it's the only thing I can think of that might explain the problem.
And then again, I might be wrong ...
David Webb
Post #729089
Lynn Pettis
Lynn Pettis
Posted Thursday, June 04, 2009 10:14 AM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 7:10 PM
Points: 21,588,
Visits: 27,380
David Webb (6/4/2009)
Is there a chance that the full backup procedure does an explicit truncate on the log at some point after the backup is taken? It would invalidate the use of the full backup as a staring point for rolling forward with the logs. Not a very likely scenario, but it's the only thing I can think of that might explain the problem.
Good thought, David. I hadn't thought about that myself.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #729104
Bob Shaw
Bob Shaw
Posted Thursday, June 04, 2009 10:28 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:34 AM
Points: 45,
Visits: 174
That was the issue, there was a call to shrink the database files using NoTruncate so they wouldnt hog up the hard drive space. But right after that though there was another call to truncate the log.
I removed the truncate log call and the backups are running fine.
Thank You so much for the help Lynn and David.
Post #729125
« Prev Topic
|
Next Topic »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.