AWS - Moving data and Migrations

 

  1. AWS Data Pipeline 
    1. To enable running activities using on-premise resources, AWS Data Pipeline does the following: It supply a Task Runner package that can be installed on your on- premise hosts. 
    2. This package continuously polls the AWS Data Pipeline service for work to perform. When it's time to run a particular activity on your on-premise resources, it will issue the appropriate command to the Task Runner. 
    3. Data Pipeline service does not support data streams.
    4. Task runners call PollForTask to receive a task to perform from AWS Data Pipeline. If tasks are ready in the work queue, PollForTask returns a response immediately. If no tasks are available in the queue, PollForTask uses long-polling and holds on to a poll connection for up to 90 seconds, during which time any newly scheduled tasks are handed to the task agent. 
  2. Migration
    1. CloudEndure Migration is a block-level replication tool that simplifies the process of migrating applications from physical, virtual, and cloud-based servers to AWS. 
      1. If your source environment includes bare metal servers, and you can install agents.
      2. CloudEndure Migration continuously replicates your source servers to your AWS account.
    2. AWS SMS supports migrations of virtual machines from VMware, Hyper-V, or Microsoft Azure. AWS SMS doesn’t currently support physical infrastructure or other public cloud providers except for Microsoft Azure.
    3. It is recommended by AWS to use the Server Migration Service (SMS) to migrate VMs from a vCenter environment to AWS. SMS automates the migration process by replicating on-premises VMs incrementally and converting them to Amazon machine images (AMIs). You can continue using your on-premises VMs while the migration is in progress. The Server Migration Connector is a FreeBSD VM that you install in your on-premises virtualization environment.
    4. Use AWS Server Migration Service (SMS) to create and launch a replication job for each tier of the application. Launch instances from the AMIs created by AWS SMS. After initial testing, perform a final replication and create new instances from the updated AMIs.
    5. During the replication process, AWS SMS creates an Amazon S3 bucket in the Region on your behalf, with server-side encryption enabled. AWS SMS replicates server volumes from your environment to this bucket and then creates EBS snapshots from the volumes.
    6. AWS Server Migration Service supports the automated migration of multi-server application stacks from your on-premises data center to Amazon EC2. Where server migration is accomplished by replicating a single server as an Amazon Machine Image (AMI), application migration replicates all of the servers in an application as AMIs and generates an AWS CloudFormation template to launch them in a coordinated fashion. Applications can be further subdivided into groups that allow you to launch tiers of servers in a defined order. 
    7. DMS - AWS DMS is a server in the AWS Cloud that runs replication software. You create a source and target connection to tell AWS DMS where to extract from and load to. Then you schedule a task that runs on this server to move your data. AWS DMS creates the tables and associated primary keys if they don't exist on the target. 
      1. AWS DMS doesn't automatically create secondary indexes, foreign keys, user accounts, and so on, in the target database.  Indexes, triggers, and referential integrity constraints can affect your migration performance and cause your migration to fail. 
      2. When migrating to an Amazon RDS database, it's a good idea to turn off backups and Multi-AZ on the target until you're ready to cut over. 
      3. AWS DMS doesn't perform schema or code conversion - you can use the AWS Schema Conversion Tool (AWS SCT).
      4. When you plan your migration, we recommend that you run diagnostic support scripts. premigration assessment evaluates specified components of a database migration task to help identify any problems that might prevent a migration task from running as expected. 
      5. AWS DMS uses some resources on your source database- reduce the number of tasks or tables for each task for your migration.
      6. With Amazon RDS databases, it's a good idea to turn off backups and Multi-AZ until the cutover.
      7. If you turn on data validation for a task, AWS DMS begins comparing the source and target data immediately after a full load is performed for a table.
      8. A premigration assessment evaluates specified components of a database migration task to help identify any problems that might prevent a migration task from running as expected. This assessment gives you a chance to identify issues before you run a new or modified task.

Comments

Popular posts from this blog

AWS Organizations, IAM

Key Concepts

Linear Algebra Concepts