June 23, 2011 at 11:23 am
GilaMonster (6/23/2011)
In this situation, there is NO way to take a log backup (the log chain is broken) so the best you can do is restore full, diff and any log backups you have.
Cat got your tongue?
June 23, 2011 at 11:59 am
Gail, can you please let me know, then in which situations i can take Tail Log backup and in which situations I cannot take Tail Log backup ? What command i should use to take Tail Log backup ?
Thanks in advance.
June 23, 2011 at 1:21 pm
You backup the tail of the log if you are having issues with your database and are about to restore. It's a normal log backup.
This should help: http://msdn.microsoft.com/en-us/library/ms179314.aspx
June 23, 2011 at 1:22 pm
beejug1983 (6/23/2011)
Gail, can you please let me know, then in which situations i can take Tail Log backup and in which situations I cannot take Tail Log backup ? What command i should use to take Tail Log backup ?Thanks in advance.
http://msdn.microsoft.com/en-us/library/ms179314.aspx
perhaps you could answer my question and describe the actual command you issued and whether or not you did truncate your log, your original question does not suggest you did.
---------------------------------------------------------------------
June 23, 2011 at 1:24 pm
beats head on desk..............
---------------------------------------------------------------------
June 23, 2011 at 1:42 pm
Ninja's_RGR'us (6/23/2011)
GilaMonster (6/23/2011)
In this situation, there is NO way to take a log backup (the log chain is broken) so the best you can do is restore full, diff and any log backups you have.
Cat got your tongue?
No. Was on my way to evening event. Suppose I could have just rephrased that, but meaning wouldn't have changed.
What resulted in the error that the OP posted ("BACKUP LOG cannot be performed because there is no current database backup.") was an explicit log truncation of some form, a breaking of the log chain. No fix for that with the DB damaged.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2011 at 1:46 pm
Steve Jones - SSC Editor (6/23/2011)
You backup the tail of the log if you are having issues with your database and are about to restore. It's a normal log backup.This should help: http://msdn.microsoft.com/en-us/library/ms179314.aspx
It's not quite a normal log backup. There needs to be one of two options specified that is not part of a normal log backup.
About to restore with DB online - backup log ... with norecovery
Want to restore with data file damaged (even unavailable) - backup log ... with no_truncate
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2011 at 8:22 pm
The command i issued to take Tail Log backup is :
backup log primer to disk='H:\primer.trn' with continue_after_error;
June 24, 2011 at 12:40 am
You need NO_TRUNCATE for a tail log backup with a damaged mdf (is documented), but won't help here, something broke the log chain before this point (switch to simple recovery and back or an explicit log truncation)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 24, 2011 at 2:21 am
I took tail log backup with no_trucate syntax as Gail suggested. I was able to take Tail Log backup and point in time recovery successfully done. Thanks all for your time.
June 24, 2011 at 3:35 am
beejug1983 (6/24/2011)
I took tail log backup with no_trucate syntax as Gail suggested. I was able to take Tail Log backup and point in time recovery successfully done. Thanks all for your time.
Error from your first post
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
Without a full/diff backup SQL will not allow to do log (or)tail log backup.
then,
How its possible?
How do you did?
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
June 24, 2011 at 8:00 am
beejug1983 (6/23/2011)
The command i issued to take Tail Log backup is :backup log primer to disk='H:\primer.trn' with continue_after_error;
that should have worked. You must have done something else before trashing the data file.
---------------------------------------------------------------------
June 26, 2011 at 2:25 am
Hi muthukkumaran,
Earlier i was using continue_after_error syntax but later i used no_truncate and backup succeeded successfully.
Viewing 13 posts - 16 through 27 (of 27 total)
You must be logged in to reply to this topic. Login to reply