Next steps and resources
This guide covered best practices for quick disaster recovery of SQL Server databases. The recommendations include using images to restore the application instance and to use native SQL methods to restore the database, or, preferably, to fail over the database. In contrast to large database restores that can take hours, using Amazon Elastic Compute Cloud (Amazon EC2) Amazon Machine Image (AMI) backups in combination with the most recent transaction logs helps you meet your recovery point objective (RPO) and recovery time objective (RTO) requirements while keeping your overall costs low. The optimal approach depends on the size of your database, the number and nature of backups, and the frequency of transaction log backups for which a disaster recovery strategy needs to be designed. See the following links for more information, best practices, Quick Start guides, and prescriptive guidance on migrating and hosting SQL Server on Amazon EC2.
Documentation
-
Best practices and recommendations for SQL Server clustering on Amazon EC2 (Amazon EC2 documentation)
-
Amazon EC2 instance store (Amazon EC2 documentation)
-
Replicating objects (Amazon S3 documentation)
-
Amazon EBS fast snapshot restore (Amazon EC2 documentation)
-
SQL Server with Always On replication on the AWS Cloud
(Quick Start reference deployment) -
Amazon EBS volume types (Amazon EC2 documentation)
-
Using FSx for Windows File Server with Microsoft SQL Server (Amazon FSx documentation)
-
What is AWS Backup? (AWS Backup documentation)
-
AWS Windows AMIs (Amazon EC2 documentation)
AWS Prescriptive Guidance
Blog posts and news
SQL Server documentation
