Quantcast
Channel: SQLServerCentral » SQL Server 2014 » Administration - SQL Server 2014 » Latest topics
Viewing all articles
Browse latest Browse all 6525

AlwaysOn HA - secondary node failed and restored from VM image - can't get databases back in sync

$
0
0
SQL 2014 AlwaysOn availability group (this is for a DR test, haven't rolled to prod yet)We have two nodes, Red and Blue.Red was primary, died (and we then failed over to Blue making it primary).We restored the VM image of Red from about 12 hours earlier.Now we tried to resume data sync with Blue and Red.However, even though they all "see" each other, Red who we just VM restored stays in the not synchronizing state and when we tried a resume we get:----------[b]AlwaysOn Availability Groups data movement for database 'MyExampleDatabase' has been suspended for the following reason: "system" (Source ID 7; Source string: 'SUSPEND_FROM_REVALIDATION'). To resume data movement on the database, you will need to resume the database manually. For information about how to resume an availability database, see SQL Server Books Online.[/b]---------I think that in this case, we have to delete the databases off Red (who was the VM restored one that died) and restore them back to current and then resync and rejoin them to the AG?Is there anyway to join them back to the AG WITHOUT having to do a full restore plus logs up to current and then re-joining and synching to the AG?I can't find much info on that error but it seems to be saying that the logs that were on the AG are now so out of date they no longer have all the needed info in the current log chain (backups were taken and log checkpointed and truncated) and we have to restore from backups to bring all the logs back and up to chain?Trying to fully understand what is going on here.Thanks!

Viewing all articles
Browse latest Browse all 6525

Trending Articles