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 |
|
thaniparthi.rao
Yak Posting Veteran
96 Posts |
 Posted - 2010-01-06 : 09:20:35
|
| Hello,Today we came across a new strange issue on our production server(2005).The production DB has both replication and mirroring configured.Mirroring is configured in asynchronous mode which means principal sents the log buffer to the mirror and commits it on the principal irrespective of the mirroring state as it uses the asynchronous communication.Due to some networks issues the mirror is out of sync with the principal . But now the replication is not running and below is the error logged “Replicated transactions are waiting for next log backup or mirroring partner to catch up”My question here is as we are using asynchronous mode of mirroring why it is impacting replication. Kindly suggest how to overcome this.Any suggestions is greatly appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
thaniparthi.rao
Yak Posting Veteran
96 Posts |
Posted - 2010-01-09 : 12:40:44
|
| Hi,Thanks for the reply.I do agree both the methods use the same technology.But if asyncronous communication is used in mirroring,means the transactions are always commited on the principal irrrespective of the mirror DB status.Once the transactions are commited on the principal Server it should replicate to various subscribers but please let me know why it is not happening. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-01-09 : 14:36:43
|
| Because the mirroring transactions stay in the tlog waiting to be applied to the mirror. This backs up replication as it has to scan the tlog for the replicated transactions. To ensure replication doesn't get back logged too much, make sure mirroring doesn't get back logged. Our asynchronous mirroring pairs are 300 miles apart and they are rarely more than a few seconds latent. Because of this, our transactional replication isn't latent either.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
|
|
|
|
|
|
Replication problem due to mirroring