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 |
|
DMACK
Starting Member
3 Posts |
 Posted - 2009-08-24 : 17:41:40
|
| I have configured a transaction log shipping scenario (primary --> secondary). Everything was working perfectly until the normal backup ran. The full back up generated a transaction file. The MSN documentation suggests that this is the tail-log which was introduced in 2005. How can I keep transaction log shipping going and allow full backups to occur?DMACK |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-08-25 : 05:18:06
|
| Full backups do not truncate the transaction log and full backups do not generate a transaction log backup file.Check the job that's doing the full backup, make sure it doesn't include a log backup command (very common for people to do)--Gail ShawSQL Server MVP |
 |
|
|
DMACK
Starting Member
3 Posts |
Posted - 2009-09-02 : 11:07:40
|
| The problem has been resolved. The backup job was referring to a maintenance plan. The maintenance plan had two major steps, a full backup and a Transaction log backup. I deleted the transactin log backup and no more problem. Thanks for your help!DMACK |
|
|
|
|
|
|
Transaction log shipping broken by backups