PlateSpin Migrate allows you to use the PlateSpin Migrate Client to migrate Windows and Linux workloads to AWS. For a list of supported workloads, see Supported Workloads For Migration to Amazon Web Services.
NOTE:Migration of AWS source workloads to AWS target containers is not supported.
Consider the following points before you use the PlateSpin Migrate Client to migrate workloads to AWS:
Migration of Windows Cluster workloads is not supported.
Migration of Linux UEFI workloads is not supported. However, Windows UEFI workloads are migrated as BIOS workloads.
The PlateSpin Migrate Web Interface does not support migration of workloads to AWS. You can use only the PlateSpin Migrate Client to migrate the workloads to AWS.
PlateSpin Migrate supports AWS target instances with up to 26 volumes (EBS volumes) for Windows and 40 volumes (EBS volumes) for Linux with each disk not exceeding 15 volumes.
Migrate recommends an AWS instance size that meets or exceeds the source workload's settings for cores, memory, volumes, and NICs. However, you can choose a smaller or larger instance size based on your requirements for the target workload, as limited by the maximum instance sizes available in the AWS region.
The size of the disk created on the AWS instance is the size of the source disk partition plus about 1 GB.
The PlateSpin Migrate server can be installed on-premise where the source workloads reside or in AWS itself.
Before you use PlateSpin Migrate to migrate workloads to AWS, ensure that the following cloud access prerequisites are correctly configured and available:
An AWS account and a subscription for your account. To create an AWS account, go to Amazon Web Services Console.
A VPN connection connecting the AWS gateway to your on-premise gateway.
An Amazon Virtual Private Cloud (VPC) to launch AWS resources into your virtual network. See Amazon Virtual Private Cloud Documentation.
A PlateSpin Migrate Server license.
A Key pair to log in to your AWS instance. By default, Amazon generates the key pair in the .pem format. However, PlateSpin Migrate converts and stores the key pair in the .ppk format.
AWS credentials (combination of access key and a secret access key) for the AWS user to perform migration.
Security group and the VPC gateway that allows traffic through the following ports:
|
Type |
Port Range |
|---|---|
|
RDP |
3389 |
|
SSH |
22 |
|
TCP |
0-65535 |
|
UDP |
0-65535 |
The minimum network-related prerequisites for a successful migration are:
The source and the target workload must be able to communicate with the PlateSpin Migrate server on port 443. The target workload is the replica of the source workload that will reside in AWS.
The PlateSpin Migrate server must be able to communicate with the AWS API endpoint on port 443.
The PlateSpin Migrate server must be able to communicate with the source workloads on the ports that are used for discovery: DCOM, WMI, and RPC.
The target workload must be able to communicate with the source workload on port 3725 (default). Communications are bi-directional. The port number is configurable. For information about changing the default settings, see Section 2.0, Planning Your Workload Migrations.
For detailed access and communication requirements across your migration network, See Access and Communication Requirements across your Migration Network.
The following Microsoft .NET Framework requirements for source workloads:
Net Framework 4.5 or later is required for migrating Windows Server 2008 R2 workloads.
Net Framework 3.5 or later is required for migrating Windows Server 2003, Windows Server 2003 R2, or Windows Server 2008 workloads.
The volume labels on the source workloads must not include any special characters.
On the Windows workloads that you want to migrate, you must set the SAN policy to OnlineAll in order to ensure that the volumes on the target workload are mounted same as on the source workload.
For a Windows workload migrated to AWS to be a part of domain, you must configure the DNS server details of the domain in the AWS subnet.
PlateSpin Migrate uses the following:
During Full Replication: An Amazon Machine Image (AMI) of the PlateSpin Migrate Replication Environment.
During Server Sync: A Snapshot of the root volume of the PlateSpin Migrate Replication Environment.
A PlateSpin Migrate Replication Environment AMI is available in AWS. You must create an instance of this AMI, assign a key pair to the instance, and then create an AMI and Snapshot of the root volume from this instance.
To create AMI and Snapshot for the PlateSpin Replication Environment:
Go to the Amazon Web Services Console and log in to your AWS Console.
Launch an instance of the PlateSpin Replication Environment AMI that is available in AWS.
Review and configure the instance launch details as required. Then, click Launch to assign the key pair to your instance and create the instance.
Click the instance ID displayed on the Console to go to the launched instance.
Select the instance, click Actions > Image > Create Image to create an AMI.
Note the AMI ID displayed on the Console.
Scroll to bottom of the Console page to view the Description tab. Click the device name displayed for the Root device option.
Click the volume ID displayed for the EBS ID option to display the volume. Then, click Actions > Create Snapshot to create a snapshot of the root volume.
Note the Snapshot ID displayed on the Console and terminate the instance created in Step 3.
To help prevent the failure of a migration job to AWS, you must adopt the following best practices when you configure migration jobs:
If you use a static IP address for the network, ensure that the address is unique within the supported subnet range.
The number of target instances running at any point of time must not exceed the instance limit applicable for your subscription.
NOTE:Every migration job uses a temporary AWS instance for the migration.
Consider the following guidelines when you are migrate workloads to AWS:
For workloads with multiple NICs, AWS provides only private IP addresses for the target instance. So, you can connect to the target instance using the private IP addresses only.
Each AWS VM has both a public IP address and a private IP address for communications from machines outside the AWS environment. AWS automatically associates these IP addresses with the primary network interface for the VM.
You can use the Microsoft Remote Desktop client or SSH to remotely connect to the AWS VM. Specify the IP address as follows:
Private IP address: Use the VM’s private IP address if your machine is part of the address space for the AWS VPN.
Public IP address: Use the VM’s public IP address if your machine is not part of the address space for the AWS VPN. A public IP address is not set on the target workload that has multiple NICs.