We have had a network problem in a high availability scenario. The arbiter switched the primary and the old primary announced, that its database was incompatible to the primary server. The transaction logs were out of sync.

In such a situation does any approach exists to bring the two servers back to sync without the need to rebuild the failing servers db (like e.g. copying it from the primary)?

Any way to resend the missing log file information, so that the failed server can become valid again?

asked 26 Nov '13, 10:35

Martin's gravatar image

Martin
8.6k118151237
accept rate: 14%


You didn't say what version you are using.

Assuming a recent SQLA 12 or 16 and you are using synchronous mode, when the new mirror (was primary before failover) reconnects to the new primary, it should be able to automatically correct a log mismatch. There are some cases where it can't.

See the following for recovery instructions: How to recover from primary server failure

permanent link

answered 26 Nov '13, 11:28

Ian%20McHardy's gravatar image

Ian McHardy
3.1k23353
accept rate: 39%

Great that this was improved, currently our system is using a 11.0.1 server.

(27 Nov '13, 02:44) Martin
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×54

question asked: 26 Nov '13, 10:35

question was seen: 533 times

last updated: 27 Nov '13, 02:44