Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
vijay8282in
Starting Member
4 Posts |
Posted - 2009-02-05 : 12:14:55
|
Hi,M using Back Exec from Symentec. My Full backup of the SQL 2005 goes fine and when I try running Transaction logs it fails with following error.V-79-65323-4214 - An error occurred on a query to database XYZ.V-79-65323-4214 - BACKUP LOG cannot be performed because there is no current database backup.The item <server host>\XYZ in use - skipped.Backup of other instances is running fine.RegardsVijay |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-05 : 12:17:06
|
What Recovery model is your database? |
 |
|
vijay8282in
Starting Member
4 Posts |
Posted - 2009-02-05 : 12:20:16
|
quote: Originally posted by sodeep What Recovery model is your database?
Using Full Recovery Option |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-05 : 12:22:46
|
quote: Originally posted by vijay8282in
quote: Originally posted by sodeep What Recovery model is your database?
Using Full Recovery Option
Are you sure you have Full backup? Transaction log backup needs Full backup first. Check MSDB.Backupset |
 |
|
vijay8282in
Starting Member
4 Posts |
Posted - 2009-02-05 : 12:24:14
|
quote: Originally posted by sodeep
quote: Originally posted by vijay8282in
quote: Originally posted by sodeep What Recovery model is your database?
Using Full Recovery Option
Are you sure you have Full backup? Transaction log backup needs Full backup first. Check MSDB.Backupset
Yeah I checked that , we have a full backup. |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-05 : 12:33:12
|
My best bet is you must have truncated the log chain with Truncate_only option. If this is the case, you need to do Full backup again to continue the chain. |
 |
|
vijay8282in
Starting Member
4 Posts |
Posted - 2009-02-05 : 18:57:28
|
quote: Originally posted by sodeep My best bet is you must have truncated the log chain with Truncate_only option. If this is the case, you need to do Full backup again to continue the chain.
You got it right buddy...I found out that someone has schedules transaction log backup in Maintenance Plan..have cancelled that and it seems backup is running fineThanks buddy appreciate your helpVijay |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-05 : 19:18:14
|
You are Most Welcome |
 |
|
|
|
|