AWS prescriptive-guidance documentation change
Summary
Complete restructuring of documentation page - removed technical content about database migration tools/DMS and replaced with navigation links, support sections, and general AWS portal UI elements
Security assessment
Changes appear to be website navigation/structure modifications rather than security-related content. Removed technical details about migration methods but no security vulnerabilities or security feature additions are evident in the diff
Diff
diff --git a/prescriptive-guidance/latest/migration-database-rehost-tools/dms.md b/prescriptive-guidance/latest/migration-database-rehost-tools/dms.md index e41f4bc81..1764b3575 100644 --- a//prescriptive-guidance/latest/migration-database-rehost-tools/dms.md +++ b//prescriptive-guidance/latest/migration-database-rehost-tools/dms.md @@ -1 +1 @@ -[](/pdfs/prescriptive-guidance/latest/migration-database-rehost-tools/migration-database-rehost-tools.pdf#dms "Open PDF") +Skip to main content @@ -3 +3,4 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing a migration tool for rehosting databases](welcome.html) + * English + * [Contact us](https://aws.amazon.com/contact-us/?nc2=h_ut_cu) + * Support + * My account @@ -5 +7,0 @@ -Advantages @@ -7 +8,0 @@ Advantages -# Migration with native database tools and AWS DMS @@ -9 +9,0 @@ Advantages -Many DBAs are familiar with a wide range of tools that handle database migration and replication. These tools are typically offered by database engine vendors and third-party companies, and they work on the logical level of the specific database engine, unlike the fully application-agnostic, block-level replication approach offered by AWS Application Migration Service. @@ -11 +11 @@ Many DBAs are familiar with a wide range of tools that handle database migration -Here’s a list of these tools, ranging from the simplest to more complex approaches: + * [ ](https://aws.amazon.com/?nc2=h_home) @@ -13 +12,0 @@ Here’s a list of these tools, ranging from the simplest to more complex approa - * **Full backup/restore** is a familiar, well-known, and easy to use process for IT staff. The method depends on the type of the database engine. The process usually moves multiple logical databases that are collocated on the same database server, and can also be used to restore the databases into a managed service such as Amazon Relational Database Service (Amazon RDS). Backup/restore is the simplest method but requires a much longer cutover window compared with the other options, due to the size of the backups and the time it would require to create, copy, and restore them on the target database. For more information about this approach, see [Native SQL Server backup/restore](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/native-backup-restore.html) and [Oracle RMAN](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-oracle-database/homogeneous-migration-tools.html#oracle-rman) on the AWS Prescriptive Guidance website. @@ -15 +14 @@ Here’s a list of these tools, ranging from the simplest to more complex approa - * **Logical backup or export** is another method that takes a copy of a full or partial logical database. This native database engine tool lets you decompose a large database server to migrate selected databases that are associated with a particular application. It provides more control than full backup/restore on what to migrate, and also supports Amazon RDS as a target. However, this option also requires a longer cutover window for the same reasons as the previous method. + * Filter: All @@ -17 +16,2 @@ Here’s a list of these tools, ranging from the simplest to more complex approa - * **Native database high availability (HA) tools** include the Always On or distributed availability group clusters in Microsoft SQL Server and Oracle’s Data Guard replications. This approach requires a major effort to set up across extended, cross-site HA clusters, and might cause some performance degradation because of the longer latency to achieve fully synchronous active/active deployments. However, this method provides the closest to near-zero downtime during the cutover. + * Sign in to console + * [Create account](https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_su&src=header_signup) @@ -19 +18,0 @@ Here’s a list of these tools, ranging from the simplest to more complex approa - * **Change Data Capture (CDC) replication** is supported by [AWS Database Migration Service](https://aws.amazon.com/dms/) (AWS DMS) and native database replication tools such as Oracle GoldenGate, Qlik, and Talend. You can use these tools to copy a partial or complete database with the advantage of near-zero downtime, because they keep the target database in sync with the source database. You can also use this method with [AWS Schema Conversion Tool](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Welcome.html) (AWS SCT) and AWS DMS for heterogeneous migrations, to migrate and modernize your database at the same time. @@ -21 +19,0 @@ Here’s a list of these tools, ranging from the simplest to more complex approa - * If network throughput is a bottleneck during your database migration, you can use AWS DMS in conjunction with [AWS Snowball](https://aws.amazon.com/snowball/) to migrate and modernize very large databases. For more information, see the [New AWS DMS and AWS Snowball Integration Enables Mass Database Migrations and Migrations of Large Databases](https://aws.amazon.com/blogs/database/new-aws-dms-and-aws-snowball-integration-enables-mass-database-migrations-and-migrations-of-large-databases/) blog post. @@ -22,0 +21 @@ Here’s a list of these tools, ranging from the simplest to more complex approa +AWS Prescriptive Guidance @@ -23,0 +23 @@ Here’s a list of these tools, ranging from the simplest to more complex approa + * [Home](/prescriptive-guidance/) @@ -24,0 +25 @@ Here’s a list of these tools, ranging from the simplest to more complex approa + * [Accelerating cloud transformation](/prescriptive-guidance/accelerating-cloud-transformation/) @@ -26 +27 @@ Here’s a list of these tools, ranging from the simplest to more complex approa -## Advantages + * [Agentic AI](/prescriptive-guidance/agentic-ai/) @@ -28 +29 @@ Here’s a list of these tools, ranging from the simplest to more complex approa -Using database tools for migration has the following advantages over block-level replication methods: + * [Large migrations](/prescriptive-guidance/large-migrations/) @@ -30 +31 @@ Using database tools for migration has the following advantages over block-level - * Some tools provide migration with minimal downtime. These include AWS DMS and native tools that support native HA clusters or CDC replication. + * [Migration tools](/prescriptive-guidance/migration-tools/) @@ -32 +32,0 @@ Using database tools for migration has the following advantages over block-level - * You’re able to use tools that are familiar to most DBAs to migrate your clustered databases. @@ -34 +33,0 @@ Using database tools for migration has the following advantages over block-level - * You can modernize the database as part of the migration workflow, and move into managed database services such as Amazon RDS or Amazon Aurora. @@ -36 +34,0 @@ Using database tools for migration has the following advantages over block-level - * You can take advantage of consolidation and decomposition (or partial database migrations), when moving from a monolithic infrastructure to microservices, splitting up a large database server or a cluster, or merging smaller databases into a larger instance or into an AWS service. @@ -37,0 +36,2 @@ Using database tools for migration has the following advantages over block-level + * [AWS](/)› + * [Prescriptive Guidance](/prescriptive-guidance/) @@ -41 +41 @@ Using database tools for migration has the following advantages over block-level -### Disadvantages +# AWS Prescriptive Guidance @@ -43 +43 @@ Using database tools for migration has the following advantages over block-level -Most of the benefits discussed in the previous section are outside a typical lift-and-shift migration scenario and fall under the replatform approach. Moreover, native database migration methods have some disadvantages in large-scale migrations, such as: +Resources from AWS technology experts and AWS Partners to help accelerate cloud adoption and modernization @@ -45 +45 @@ Most of the benefits discussed in the previous section are outside a typical lif - * Preparation – You have to pre-provision and configure the target infrastructure, database servers, and clusters fully before you can use any of the native database methods. +## Guides @@ -47 +47 @@ Most of the benefits discussed in the previous section are outside a typical lif - * Complexity – Some methods, such as full or logical backup/restore, have to be combined with another replication method to detect all the changes since the initial backup was created. +Guidance for planning and implementing strategies, with focus on best practices and tools, for architects, managers, and technical leads @@ -49 +49 @@ Most of the benefits discussed in the previous section are outside a typical lif - * Scalability – There’s no simple automation framework available to roll these methods out to other database clusters and servers when you migrate at scale. +Loading @@ -50,0 +51 @@ Most of the benefits discussed in the previous section are outside a typical lif +Loading @@ -51,0 +53 @@ Most of the benefits discussed in the previous section are outside a typical lif +Loading @@ -52,0 +55 @@ Most of the benefits discussed in the previous section are outside a typical lif +Loading @@ -54 +57 @@ Most of the benefits discussed in the previous section are outside a typical lif - **Javascript is disabled or is unavailable in your browser.** +Loading @@ -56 +59 @@ Most of the benefits discussed in the previous section are outside a typical lif -To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. +## Patterns @@ -58 +61 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -[Document Conventions](/general/latest/gr/docconventions.html) +Steps, architectures, tools, and code for implementing common migration, optimization, and modernization scenarios, for builders and other hands-on users @@ -60 +63 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Migration with AWS Application Migration Service +Loading @@ -62 +65 @@ Migration with AWS Application Migration Service -Next steps: decision matrix +Loading @@ -64 +67 @@ Next steps: decision matrix -Did this page help you? - Yes +Loading @@ -66 +69 @@ Did this page help you? - Yes -Thanks for letting us know we're doing a good job! +Loading @@ -68 +71 @@ Thanks for letting us know we're doing a good job! -If you've got a moment, please tell us what we did right so we can do more of it. +Loading @@ -70 +73 @@ If you've got a moment, please tell us what we did right so we can do more of it -Did this page help you? - No +## Strategies @@ -72 +75 @@ Did this page help you? - No -Thanks for letting us know this page needs work. We're sorry we let you down. +Business perspectives, methodologies, and frameworks for cloud migration and modernization, for CxOs and senior managers @@ -74 +77,111 @@ Thanks for letting us know this page needs work. We're sorry we let you down. -If you've got a moment, please tell us how we can make the documentation better. +Loading + +Loading + +Loading + +Loading + +Loading + +## Content collections + +1 / 4 + +[ business-productivity Accelerating cloud transformation Learn more ](/prescriptive-guidance/accelerating-cloud-transformation/) + +[ ai-ml Agentic AI Learn more ](/prescriptive-guidance/agentic-ai/) + +[ migration Large migrations to the AWS Cloud Learn more ](/prescriptive-guidance/large-migrations/) + +[ migration Migration tools Learn more ](/prescriptive-guidance/migration-tools/) + +## More information + +Services, tools, and resources to help with your large migration journey + +### Additional resources + + * [Migrate and modernize with AWS](/migrate-modernize-build/cloud-migration/) + * [AWS Architecture Center](/architecture/) + * [AWS Documentation](https://docs.aws.amazon.com/) + * [AWS Professional Services](/professional-services/) + * [AWS Partner Network](/partners/) + + + +### Feedback and support + + * [Send us your feedback](https://docs.aws.amazon.com/forms/aws-doc-feedback?hidden_service_name=ProServe%20Enterprise%20GPS&topic_url=http://aws.amazon.com/prescriptive-guidance/) + * [Contact AWS Support](/premiumsupport/) + + + +[Create an AWS account](https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc1=f_ct&src=footer_signup) + +## Learn + + * [What Is AWS?](/what-is-aws/?nc1=f_cc) + * [What Is Cloud Computing?](/what-is-cloud-computing/?nc1=f_cc) + * [What Is Agentic AI?](/what-is/agentic-ai/?nc1=f_cc) + * [Cloud Computing Concepts Hub](/what-is/?nc1=f_cc) + * [AWS Cloud Security](/security/?nc1=f_cc) + * [What's New](/new/?nc1=f_cc) + * [Blogs](/blogs/?nc1=f_cc) + * [Press Releases](https://press.aboutamazon.com/press-releases/aws) + + + +## Resources + + * [Getting Started](/getting-started/?nc1=f_cc) + * [Training](/training/?nc1=f_cc) + * [AWS Trust Center](/trust-center/?nc1=f_cc) + * [AWS Solutions Library](/solutions/?nc1=f_cc) + * [Architecture Center](/architecture/?nc1=f_cc) + * [Product and Technical FAQs](/faqs/?nc1=f_dr) + * [Analyst Reports](/resources/analyst-reports/?nc1=f_cc) + * [AWS Partners](/partners/work-with-partners/?nc1=f_dr) + + + +## Developers + + * [Builder Center](/developer/?nc1=f_dr) + * [SDKs & Tools](/developer/tools/?nc1=f_dr) + * [.NET on AWS](/developer/language/net/?nc1=f_dr) + * [Python on AWS](/developer/language/python/?nc1=f_dr) + * [Java on AWS](/developer/language/java/?nc1=f_dr) + * [PHP on AWS](/developer/language/php/?nc1=f_cc) + * [JavaScript on AWS](/developer/language/javascript/?nc1=f_dr) + + + +## Help + + * [Contact Us](/contact-us/?nc1=f_m) + * [File a Support Ticket](https://console.aws.amazon.com/support/home/?nc1=f_dr) + * [AWS re:Post](https://repost.aws/?nc1=f_dr)