AWS prescriptive-guidance documentation change
Summary
Updated documentation for SQL Server HA/DR on EC2 including: title simplification, link updates, formatting changes (bold headers), typo fixes, image path updates, terminology adjustments (e.g., 'Amazon EBS' to 'EBS'), and expanded AWS MGN reference.
Security assessment
Changes are editorial and structural (formatting, typos, link updates) with no evidence of addressing security vulnerabilities. The content discusses HA/DR backup strategies but doesn't introduce new security features or address specific security weaknesses.
Diff
diff --git a/prescriptive-guidance/latest/sql-server-ec2-ha-dr/options-considerations.md b/prescriptive-guidance/latest/sql-server-ec2-ha-dr/options-considerations.md index 04503e983..07c1eb1a3 100644 --- a//prescriptive-guidance/latest/sql-server-ec2-ha-dr/options-considerations.md +++ b//prescriptive-guidance/latest/sql-server-ec2-ha-dr/options-considerations.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building a high availability and disaster recovery architecture with native and hybrid methods for Microsoft SQL Server databases on Amazon EC2](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building a high availability and disaster recovery architecture for SQL Server on Amazon EC2](introduction.html) @@ -11 +11 @@ Managing HA/DR resources in AWS BackupUsing AWS DMS for HA/DRUsing AWS Transform -Although the possibility of an AWS Availability Zone or Region going completely offline is extremely rare, we recommend a multi-pronged approach to backup and recovery in the event of a disaster for redundancy and to minimize data loss. Backup and recovery processes should include the appropriate level of granularity to meet the the recovery time objective (RTO) and recovery point objective (RPO) for the workload and to support business processes, and are often dependent on the application. In the case of databases, AWS also supports all Microsoft recommendations for SQL Server setup and configuration for high availability and disaster recovery (HA/DR). Different editions of SQL Server support various HA/DR options, and you should consider special cases such as very large databases (VLDBs) on a case-by-case basis. As with any DR configuration, testing is essential to ensure that each application meets its service-level agreements (SLAs) for HA/DR. For your test/development environment, consider using [SQL Server Developer edition](https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15), which is free but comes with limitations. +Although the possibility of an AWS Availability Zone or Region going completely offline is extremely rare, we recommend a multi-pronged approach to backup and recovery in the event of a disaster for redundancy and to minimize data loss. Backup and recovery processes should include the appropriate level of granularity to meet the recovery time objective (RTO) and recovery point objective (RPO) for the workload and to support business processes, and are often dependent on the application. In the case of databases, AWS also supports all Microsoft recommendations for SQL Server setup and configuration for high availability and disaster recovery (HA/DR). Different editions of SQL Server support various HA/DR options, and you should consider special cases such as very large databases (VLDBs) on a case-by-case basis. As with any DR configuration, testing is essential to ensure that each application meets its service-level agreements (SLAs) for HA/DR. For your test/development environment, consider using [SQL Server Developer edition](https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15), which is free but comes with limitations. @@ -15 +15 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * SQL Server native HA/DR options with a warm standby (database level) – For illustrations of some of these architectures, see the [SQL Server on Amazon EC2 architecture diagrams](./architecture.html) section later in this guide. + * **SQL Server native HA/DR options with a warm standby (database level)** – For illustrations of some of these architectures, see the [SQL Server on Amazon EC2 architecture diagrams](./architecture.html) section later in this guide. @@ -23 +23 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * SQL Server native backups to Amazon S3 (database level, DR only) – Full backups (one time daily) + * **SQL Server native backups to Amazon S3 (database level, DR only)** – Full backups (one time daily) @@ -29 +29 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * Backups need to be taken and copied to Amazon Simple Storage Service (Amazon S3) by using custom scripting or an option such as a [File Gateway](https://aws.amazon.com/storagegateway/file/) for efficient backup and transfer. + * Backups need to be taken and copied to Amazon S3 by using custom scripting or an option such as a [File Gateway ](https://aws.amazon.com/storagegateway/file/)for efficient backup and transfer. @@ -33 +33 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * Use [Amazon S3 Cross-Region Replication (CRR)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html#crr-scenario) with [S3 Replication Time Control (RTC)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-time-control.html) to control and monitor object replication within an SLA of 15 minutes. + * Use [Amazon S3 Cross-Region Replication (CRR)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html#crr-scenario) with [Replication Time Control (RTC)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-time-control.html) to control and monitor object replication within an SLA of 15 minutes. @@ -35 +35 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * For compliance and cost savings, you can also use [S3 Lifecycle management](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) to move and store older backups for long-term storage. + * For compliance and cost savings, you can also use [Amazon S3 Lifecycle management](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) to move and store older backups for long-term storage. @@ -41 +41 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * AWS snapshots (instance and volume level, DR only) + * **AWS snapshots (instance and volume level, DR only)** @@ -43 +43 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * Amazon Elastic Compute Cloud (Amazon EC2) Amazon Machine Image (AMI) backups to rebuild databases from scratch + * Amazon EC2 Amazon Machine Image (AMI) backups to rebuild databases from scratch @@ -45 +45 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can - * Amazon Elastic Block Store (Amazon EBS) volume snapshots to attach EBS volumes to Amazon EC2 + * Amazon EBS volume snapshots to attach EBS volumes to Amazon EC2 @@ -52 +52 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can -[AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/whatisbackup.html) is a fully managed service that offers the ability to create backup plans and schedules, and assign AWS resources that are involved in HA/DR configuration—such as Amazon EBS volumes to create snapshots and Amazon EC2 AMIs—to these backup plans. You can also use AWS Backup to schedule multi-Region copies of these EBS snapshots. For optimal usage, AWS Backup requires an efficient tagging mechanism for resources to be in place. AWS Backup also supports application-consistent backups through the Windows Volume Shadow Copy Service (VSS), which you can use for SQL Server. For storage-level protection, we recommend using EBS snapshots. Initial EBS snapshots are full, and subsequent snapshots are incremental. Although EBS snapshots offer storage-level protection, they do not replace SQL Server file-based native backups that offer point-in-time recovery. +[AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/whatisbackup.html) is a fully managed service that offers the ability to create backup plans and schedules, and assign AWS resources that are involved in HA/DR configuration—such as EBS volumes to create snapshots and Amazon EC2 AMIs—to these backup plans. You can also use AWS Backup to schedule multi-Region copies of these EBS snapshots. For optimal usage, AWS Backup requires an efficient tagging mechanism for resources to be in place. AWS Backup also supports application-consistent backups through the Windows Volume Shadow Copy Service (VSS), which you can use for SQL Server. For storage-level protection, we recommend using EBS snapshots. Initial EBS snapshots are full, and subsequent snapshots are incremental. Although EBS snapshots offer storage-level protection, they do not replace SQL Server file-based native backups that offer point-in-time recovery. @@ -56 +56 @@ For a use case that requires an RPO of 15 minutes and an RTO of 4 hours, you can -If you’re looking for an alternative to SQL Server Always On options for replication or if you have heterogeneous source and target databases, either in a hybrid setup or in AWS, you can use AWS Database Migration Service (AWS DMS) in the following ways. +If you're looking for an alternative to SQL Server Always On options for replication or if you have heterogeneous source and target databases, either in a hybrid setup or in AWS, you can use AWS Database Migration Service (AWS DMS) in the following ways. @@ -58 +58 @@ If you’re looking for an alternative to SQL Server Always On options for repli -If you use AWS DMS with SQL Server in a self-managed context (hosted on Amazon EC2 or on premises), it supports one-time and ongoing replication in two modes: by using MS-REPLICATION (to capture changes to tables that have primary keys) and MS-CDC (to capture changes to tables that don’t have primary keys). However, if you use Amazon Relational Database Service (Amazon RDS) as a source for AWS DMS, only MS-CDC is supported. AWS DMS offers a range of source and target endpoints, supports heterogeneous database engines, and offers fine-grained control over the replication process. You can also use the AWS Schema Conversion Tool (AWS SCT) with AWS DMS for heterogeneous database migrations. AWS SCT automates schema-level changes and also produces reports for migration readiness and planning. +If you use AWS DMS with SQL Server in a self-managed context (hosted on Amazon EC2 or on premises), it supports one-time and ongoing replication in two modes: by using MS-REPLICATION (to capture changes to tables that have primary keys) and MS-CDC (to capture changes to tables that don't have primary keys). However, if you use Amazon Relational Database Service (Amazon RDS) as a source for AWS DMS, only MS-CDC is supported. AWS DMS offers a range of source and target endpoints, supports heterogeneous database engines, and offers fine-grained control over the replication process. You can also use the AWS Schema Conversion Tool (AWS SCT) with AWS DMS for heterogeneous database migrations. AWS SCT automates schema-level changes and also produces reports for migration readiness and planning. @@ -62 +62 @@ You add source and target databases as end points in AWS DMS, as illustrated in - + @@ -66 +66 @@ Consider using AWS DMS instead of native HA/DR methods in the following scenario - * When you want to save on licensing costs. For example, if you’re using an advanced version such as SQL Server Enterprise edition only for its Always On options, you might consider setting up AWS DMS instead, because it can provide a logical replication option without the cost of an Enterprise edition license. + * When you want to save on licensing costs. For example, if you're using an advanced version such as SQL Server Enterprise edition only for its Always On options, you might consider setting up AWS DMS instead, because it can provide a logical replication option without the cost of an Enterprise edition license. @@ -68 +68 @@ Consider using AWS DMS instead of native HA/DR methods in the following scenario - * When you have heterogeneous sources and targets. SQL Server versions on primary and disaster recovery nodes do not need to match (within AWS DMS limitations), which provides significant flexibility. + * When you have heterogenous sources and targets. SQL Server versions on primary and disaster recovery nodes do not need to match (within AWS DMS limitations), which provides significant flexibility. @@ -72 +72 @@ Consider using AWS DMS instead of native HA/DR methods in the following scenario - * For business use cases such as near real-time transfer (depending on replication instance, network configuration, and data volume), data masking, selective filtering, schema/table mapping (homogeneous and heterogeneous), pre-migration assessments, and JSON support. + * For business use cases such as near real-time transfer (depending on replication instance, network configuration, and data volume), data masking, selective filtering, schema/table mapping (homogenous and heterogenous), pre-migration assessments, and JSON support. @@ -81 +81 @@ The following diagram shows an alternative approach to how AWS DMS can provide r - + @@ -83 +83 @@ The following diagram shows an alternative approach to how AWS DMS can provide r -The source and target engines do not have to match. In the diagram, the primary and secondary nodes marked as (1) can be a SQL Server cluster in a Single-AZ or Multi-AZ configuration. Or the source can be a single SQL Server node that supports MS-CDC or MS-REPLICATION. +The source and target engines do not have to match. In the diagram, the primary and secondary nodes marked as (1) can be a SQL server cluster in a Single-AZ or Multi-AZ configuration. Or the source can be a single SQL Server node that supports MS-CDC or MS-REPLICATION. @@ -89 +89 @@ The target DB instance, marked as (2) in the diagram, can be any version of SQL -We recommend using the AWS Transform MGN for lift-and-shift migrations to AWS. MGN continuously replicates your machines (including the operating system, system state configuration, databases, applications, and files) into a low-cost staging area in your target AWS account and preferred Region. In the case of a disaster, you can use MGN to automatically launch thousands of your machines in their fully provisioned state in minutes. +We recommend using [AWS Transform MGN](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) for lift-and-shift migrations to AWS. MGN continuously replicates your machines (including the operating system, system state configuration, databases, applications, and files) into a low-cost staging area in your target AWS account and preferred Region. In the case of a disaster, you can use MGN to automatically launch thousands of your machines in their fully provisioned state in minutes. @@ -126 +126 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -SQL Server on Amazon EC2 single-node architecture +SQL Server on Amazon EC2