Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group
Database Blog
This article explains how to use AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group secondary replica that has fallen out of sync, avoiding manual backup-restore cycles and automatic seeding overhead.
- AWS Backup captures VSS-enabled snapshots of secondary replicas and restores them as replacement EC2 instances
- Secondary IP addresses must be manually reconfigured after restore, as AWS Backup does not carry them over
- Restored nodes rejoin the AG through ALTER AVAILABILITY GROUP commands with SEEDING_MODE = MANUAL
- Four scenarios tested: replica loss with/without open transactions, committed transactions not yet replicated, and broken LSN chain requiring differential and log backup restoration
- Scenario 4 (broken LSN chain) requires additional differential backup, file copy, and per-database restore steps
- AWS VSS restore automation cannot rebuild secondary replicas; EC2-level restore is the correct approach
- Resynchronization progress monitored via redo queue size, log send queue, and SQL Server Management Studio AG dashboard
AWS Backup provides a faster, more reliable alternative to traditional manual processes for rebuilding failed AG secondary nodes, with clear operational guidance for handling complex LSN chain scenarios.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2025
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.