Any easy recovery from high availability failure?

[MCMartin]

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?

[ian_mchardy · Accepted solution]

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

[MCMartin · Accepted solution]

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