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 |
|
avipenina
Starting Member
44 Posts |
 Posted - 2007-11-10 : 13:35:01
|
| Hi,I've setup a Log Shipping environment in my test lab,and every thing works great.i did a TLog backup deliberately "Backup tran DB to disk = N'C:\TLog.trn'"by doing that i break the Backup and Copy TLog chain,and after that the destination DB was not restored with any TLog backup.why is that?and if i by mistake do a tlog backup in a Log Shipping environment how do i sync the destination DB? |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-11-10 : 13:51:50
|
| you can use backup WITH COPY_ONLY that won't break the log chain._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com |
 |
|
|
avipenina
Starting Member
44 Posts |
Posted - 2007-11-10 : 14:32:22
|
| ok.but what happen if i use the backup tran without the COPY_ONLY option?how can i reconnect the chain if i do that backup tran? |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-11-10 : 14:35:31
|
| there's no simple way that i know of. best bet is probably to create a new full backup on which you can restore on._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-12 : 12:10:25
|
| If you break the chain, then you must start over with a full backup. There is no way around it. Just don't run tlog backups on the secondary server ever!Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
avipenina
Starting Member
44 Posts |
Posted - 2007-11-13 : 03:51:27
|
quote:
Originally posted by tkizer
If you break the chain, then you must start over with a full backup. There is no way around it. Just don't run tlog backups on the secondary server ever!Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/
what do you mean by "Just don't run tlog backups on the secondary server ever!"I'm talking about the primary server that i do TLog backup that broke the chain,not TLog on the secondary server. |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-11-13 : 04:55:49
|
she's warning you  on the primary server you have to start with the full backup again._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-13 : 13:07:20
|
quote:
Originally posted by avipenina
quote:
Originally posted by tkizer
If you break the chain, then you must start over with a full backup. There is no way around it. Just don't run tlog backups on the secondary server ever!Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/
what do you mean by "Just don't run tlog backups on the secondary server ever!"I'm talking about the primary server that i do TLog backup that broke the chain,not TLog on the secondary server.
I typo-ed. I meant primary server. If you run a manual tlog backup on the primary server, then you must copy that file over to the secondary and manually restore it using with norecovery option in order for log shipping to work again. Log shipping will only apply the tlog backups that it created.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
backup TLog in log shipping environment