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 |
rikleo2001
Posting Yak Master
185 Posts |
Posted - 2015-03-04 : 06:39:00
|
Hi AllNeeds help please urgently.I had healthy cluster alwayson with 2 nodes.Failover occurred and 3 databases are Not in syn, and they are not coming in Sync.I can't restore all 3 databases from scratch, so what is best way to repair these secondary databases, so they can become in Sync again?Thanks in advance.SKR |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-03-04 : 12:14:22
|
It depends on what the issue is. What status are they in? Are they just latent or are they in a mode that isn't going to allow them to catch up?You could try removing the databases from the AG and then applying whichever tlog backups have occurred since the failover. I believe that'll work if the databases aren't in a bad state since they are in a norecovery/restoring state that should allow tlog backups (if I recall correctly). Otherwise, get ready for a full restore by prepping the full backup and later the differential + tlog chain.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
rikleo2001
Posting Yak Master
185 Posts |
Posted - 2015-03-05 : 04:09:23
|
Thank you TaraThey are simply saying they are not able to sync and they are not in healthy state. when I try to remove them from databases on secondary replica, that won't work.. I tried to remove them from primary databases then databases on secondary goes on restoring state, I tried tlogs, but seems like we had missing tlog, because when failover occurred it was in process of tlog backup.I will try to find more in detail on LSN and its chain, if not then yes unfortunately I have to send 100 gb across to singapore :(SKR |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-03-05 : 12:31:42
|
quote: when I try to remove them from databases on secondary replica, that won't work..
Not enough detail for us to assist. You need to investigate the error log and application log for what happened.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|