26.2 Configuring Migration of a Workload to Amazon Web Services

When you add or discover a workload, the workload is listed on the Workloads page and the status is set as Not Configured. Before you migrate the workload, you must configure the workload for migration:

  1. Launch the PlateSpin Migrate Web Interface.

  2. If you have not configured a Amazon Cloud Region as a migration target, click Targets > Add Target, and then configure the target AWS cloud platform.

     See Table 18-4, Options for Amazon Cloud Region.

  3. On the Workloads page, select the workload you want to configure.

  4. Click Configure Migration.

  5. Specify the Initial Transfer Method for replication based on the scope of data you want to transfer from the source to the target:

    • Full Replication: Migrate replicates the full volume from the source to the target.

    • Incremental Replication: Migrate replicates only differences in data from the source to the target, provided the workloads have similar operating system and volume profiles.

      NOTE:PlateSpin Migrate does not support Incremental Replication for the initial replication of data to existing target workloads in Amazon Cloud. However, you can schedule Incremental Replications for subsequent replication of data. See Incremental Recurrence in Step 8.

  6. Select an existing Amazon Cloud Region target to which you want to migrate the source workload. 

  7. Click Configure Migration.

  8. Configure the following settings:

    Schedule Settings

    Incremental Recurrence

    Specify the time and pattern when you want to run incremental replications after the first full replication, or start each incremental replication manually.

    The default setting is None. The incremental replications are unscheduled.

    To set or modify the incremental recurrence time and pattern:

    1. Click Edit.

    2. For Begin the recurrence schedule, set the date and time when you want to begin the scheduled incremental replications. You can type the date (dd/mm/yyyy) or click the Calendar icon to select the date. By default, the run time is 12:00:00 a.m. (hh:mm:ss a.m. or p.m.).

    3. For Recurrence run setting, set the pattern to follow for scheduled incremental replications:

      • Daily: The replication takes place on the specified daily intervals or on weekdays every week for a period of 60 days from the time the replication starts.

      • Weekly: The replication takes place at specified intervals for a period of 8 weeks from the time the replication starts.

      • Monthly: The replication takes place at specified intervals for a period of 2 months from the time the replication starts.

    NOTE:

    • Scheduled incremental replications are skipped until the first full replication is complete.

    • Scheduled incremental replications take place for a maximum period of 60 days from the time that the scheduled incremental replication runs begin.

    Full Replication

    Specify when you want the first full replication to run, or start the first full replication manually. The first full replication is a one-time event, but the run is attempted daily as scheduled until the first replication begins and completes successfully.

    The default setting is None. The first full replication is unscheduled.

    NOTE:You must prepare the workload prior to the scheduled time or the manual start.The full replication cannot run unless the target VM exists and the workload preparation is complete. If they are not ready, Migrate skips the scheduled full replication and retries it at the scheduled time on the next day.

    To set or modify the schedule for the first full replication:

    1. Click Edit.

    2. Click Start, then set the date and time when you want to start the first full replication. You can type the date (dd/mm/yyyy) or click the Calendar icon to select the date. By default, the run time is 12:00:00 a.m. (hh:mm:ss a.m. or p.m.).

    Blackout Window

    Specify a replication blackout window that suspends scheduled replication activities for a specified period of time and pattern. For example, suspend replications during peak network utilization hours or to prevent conflicts between VSS-aware software and the PlateSpin VSS block-level data transfer component.

    The default setting is None. No blackout window is scheduled.

    To set or modify a blackout window:

    1. Click Edit.

    2. Specify the start and end time for the blackout period.

      The blackout start and end times are based on the system clock on the PlateSpin Server.

    3. Select Daily, Weekly, or Monthly to enable a blackout window, then set the recurrence pattern.

    Compression Level

    This setting controls whether data is compressed during transmission between the source and target workloads, and the level of data compression applied.See Data Compression.

    Select one of the following options:

    • None: No compression.

    • Fast: Consumes the least CPU resources on the source, but yields a lower compression ratio.

    • Optimal: (Default) Consumes optimal CPU resources on the source and yields an optimal compression ratio. This is the recommended option.

    • Maximum: Consumes the most CPU resources on the source, but yields a higher compression ratio.

    Bandwidth Throttling

    Bandwidth throttling enables you to control the amount of available bandwidth consumed by direct source-to-target communication over the course of a workload migration. Throttling helps to prevent migration traffic from congesting your production network and to reduce the overall load of your PlateSpin Server. You can specify a throughput rate for each migration job.

    Throttling is disabled by default with a Throttling Rate value of Off.

    To throttle replications to a specified rate:

    1. Specify a maximum throughput value in Mbps for data transfer for the workload.

    2. Specify the throttling pattern:

      • Always: Always throttle data transfer for the replications.

      • Custom: Specify the time and days to throttle data transfer for the replications running in that window.

        Throttling time is local to the source workload.

    Migration Settings

    Transfer Method

    (For Windows Workloads) Select a data transfer mechanism and security through encryption.See Supported Data Transfer Methods.

    To enable encryption, select the Encrypt Data Transfer option. See Security and Privacy.

    Transfer Encryption

    (For Linux Workloads) To enable encryption, select the Encrypt Data Transfer option.See Security and Privacy.

    Source Credentials

    Specify the credentials required for accessing the workload. See Discovery Guidelines for Source Workloads.

    Virtual Machine Name

    Specify a display name for the new virtual machine.

    License Type

    Select the OS licensing model on the target workload.

    • Auto: (For Windows Workloads) Enables PlateSpin Migrate to decide whether to allow AWS to activate Windows license on the target Windows workload or allow users to bring their own licenses.

    • AWS: (For Windows Workloads) Enables AWS to activate Windows license on the target Windows workload.

    • BYOL: Enables you to bring your own Microsoft licenses (BYOL) and AWS does not bill you for the license. You are responsible for complying with Microsoft licensing and activating the OS license on the target workload. This option is applicable both for Windows and Linux workloads.

    NOTE:

    Storage Layout

    Specify the desired layout of data volumes (and volume groups) on the target workload disks:

    • Source-based

      The Source-based storage layout assigns data volumes to disks according to their layout on the source workload.

    • Single disk

      The Single disk storage layout assigns all the data volumes or LVM volume groups to a single disk on the target workload. An LVM volume group might contain multiple volumes.

    • One volume per disk

      The One volume per disk storage layout assigns each data volume or LVM volume group to a separate disk on the target workload. An LVM volume group might contain multiple volumes.

    Storage Options > Disks

    Select a disk type for each disk. The Disk Type option lists the type of disks that AWS supports. See Amazon EBS Volume Types.

    Select an encryption key to enable encryption of AWS target instance disks. Ensure that the currently logged in IAM user has sufficient permissions to use this encryption key. For information about creating the encryption key, see Creating Keys.

    Storage Options > Volumes

    Select volumes to be included in the target for migration.

    For Windows file-based migrations, you can optionally adjust the size of the target volume by modifying the Size value in the row for that volume.

    NOTE:The ability to adjust the size of the target volume is not currently available in the Disk Layout view of storage in the Migrate Web Interface. See Cannot Adjust the Target Volume Size for File-Based Migrations in the Web Interface.

    NTFS Cluster Size

    (For File-Based Windows Workloads) Specify the cluster size for the NTFS volume. For information about the default cluster size for an NTFS volume, see the Microsoft Support KB Article 140365.

    Non-volume Storage

    (For Linux Workloads) Specify a non-volume storage, such as a swap partition, that is associated with the source workload. This storage is re-created in the migrated workload.

    Disks For Volume Groups

    (For Linux Workloads) Specify the datastore name and the path where the virtual disk must be created on the target machine. You can choose to retain the path specified by default.

    Volume Groups

    (For Linux Workloads) Specify the LVM volume groups to be migrated with the LVM logical volumes listed in the Converted Logical Volumes section of the settings.

    NOTE:Disks that host both regular volumes (such as /boot) and volume groups are configured in the Disks section.

    Converted Logical Volumes

    (For Linux Workloads) Select LVM logical volumes to be included in the target for migration.

    Replication Network for Target

    The replication NIC is the primary NIC that you specify in Target Workload Settings> Network Connections.

    1. Select a network and subnet to use for replication traffic.

    2. If the workload is not part of the address space for the AWS VPN, the replication NIC requires a public IP address. Select Auto-assign Public IP to enable AWS to automatically assign the public IP.

    3. Select one of the following:

      • DHCP: Obtain an IP address automatically assigned by a DHCP server.

      • Static: Specify a static private IP address that is unique within the supported subnet.

    4. Click Add Security Groups to add one or more security groups. See Create a Security Group in the Best Practices for Migrating Servers to Amazon Web Services with PlateSpin Migrate white paper.

    Replication Networks for Source

    Specify one or more network interfaces (NIC or IP address) on the source workload to use for replication traffic that are valid for communications with the replication environment.

    If the network for the NIC you specify is not part of your AWS VPN, ensure that the NIC has a public IP address.

    Services to Stop Before Any Replication

    (For Windows Workloads) We recommend that all the non-VSS compliant services or antivirus are stopped temporarily on the source while the VSS snapshot is being captured on the source. Select the Windows services that you want to be temporarily stopped on the source workload while the VSS snapshot is being captured on the source. These services are restored as soon as the VSS snapshot creation completes.

    Services to Stop for Cutover with Replication

    (For Windows Workloads) Select the Windows services that should be permanently stopped on the source workload for cutover with any replication. The services stopped on the source workload during the replication process are not restored after Cutover. The stopped services are restored after a Test Cutover.

    Daemons to Stop before Any Replication

    (For Linux Workloads) Select the Linux services that you want to be temporarily stopped on the source workload before replication. These services will be restored back after replication completes.

    Daemons to Stop for Cutover with Replication

    (For Linux Workloads) Select the Linux services that should be permanently stopped on the source workload for Cutover with any Replication. The services stopped on the source workload during the replication process are not restored after Cutover. The stopped services are restored after a Test Cutover.

    Boot Services to disable on Target

    Select the boot services that you want to disable on the target workload.

    Target Workload Settings

    (These settings are applied during the Run Cutover)

    AWS Agent

    For collecting metrics and logs from Amazon EC2 Instance on the target workload, select the Install CloudWatch Agent option to install the AWS CloudWatch agent on the target workload. This option is displayed for the following workloads that supports CloudWatch agent:

    • Red Hat Enterprise Linux (RHEL) versions 7.6, 7.5, 7.4, 7.2, 7.0, and 6.5

    • CentOS versions 7.6, 7.2, 7.0, 6.8, and 6.5

    • 64-bit versions of Windows server

    If the AWS CloudWatch Agent is already installed on the source workload, then this option is disabled.

    Tenancy

    Select one of the following options to specify whether your instance should run on a shared or a dedicated hardware:

    • Run a shared hardware instance: Your instance runs on a shared hardware and this is selected by default.

    • Run a dedicated instance: Your instance runs on a single-tenant hardware.

    • Launch this instance on a dedicated host: Your instance runs on a dedicated host, which is an isolated server already allocated for use in your account.

      NOTE:If you choose to launch the instance on a dedicated host, the OS licensing model on the target workload is always set to BYOL irrespective of the licensing model you selected.

      Set the following options based on your requirement:

      • Host: Select a specific host to launch the instance or select Use auto-placement to allow the instance to launch on to any host that has a matching instance type and auto-placement enabled. The Use auto-placement option is selected by default if any of the available dedicated hosts supports auto-placement.

      • Affinity: For a specific dedicated host, the affinity is always Host. However, if you set the Host option to Use auto-placement, then select one of the following:

        • Off: Restarts a stopped instance on any available host. This option is selected by default.

        • Host: Restarts a stopped instance on the same host where it was launched.

    Cloud Instance Size

    Click Change Cloud Instance Size to select a supported cloud instance size appropriate for your workload.

    • If an instance type that AWS supports is not listed, then you can configure the AWSPriceListRegion PlateSpin Configuration parameter to set its value to the region name that has a price list endpoint listing the desired instance type. See Configuring the AWS Region Price List Endpoint To Be Used for Discovering Supported AWS Instance Types.

    • For Linux workloads, you must ensure that the instance type you select for the Target Workload and Target Workload Test Settings must both be of the same type: Nitro or non-Nitro. Using a combination of Nitro and non-Nitro instances during Test Cutover and Run Cutover (that is, Nitro instance during Test Cutover and a non-Nitro instance during Run Cutover or vice versa) results in migration failure.

    • As AWS adds support for new instance types, Migrate detects them dynamically and displays them with an asterisk symbol. PlateSpin Migrate might not have tested such instance types that AWS recently added and support for such AWS instance types is experimental. For a list of the new instance types that Migrate supports in this release, see What’s New in the PlateSpin Migrate 2019.11 Release Notes.

    • For each release, PlateSpin Migrate adds support for new cloud instances and instance families that AWS has released up to a stipulated date prior to the PlateSpin Migrate release. For a list of the new instance types that Migrate supports in this release, see What’s New in the PlateSpin Migrate 2019.11 Release Notes.

      You can add definitions to the PlateSpin Server for new AWS Nitro Based instances and instance families to make the instances available in the AWS Cloud Instance Sizes list. See Displaying the AWS Nitro System Based Cloud Instance Sizes That AWS Recently Supported in the AWS Cloud Instance Sizes list.

    • The m5a, r5a, and F1 instance types are supported only for Linux workloads.

    • For migration of a source Windows Domain Controller workload, select a Nitro System based instance type such as c5, m5, r5, t3, c5d, m5d, or z1d.

    • AWS requires a minimum of Microsoft .NET Framework 4.5 for migration of Windows workloads to Nitro System based VM instances. To use Nitro System based instances, ensure that .NET 4.5 Framework or later is installed on the source Windows workload prior to Migrate discovery.

    By default, Migrate selects a cloud instance size that most closely matches your source workload for the following components:

    • Total number of cores

    • Amount of memory

    • Number of NICs

    • Network Performance

    • AWS Instance Family

    The default instance either meets or exceed the settings for each of these components on the source workload. However, you can choose a smaller instance size based on your requirements:

    • The target VM uses the allowed CPU and memory for the instance size. To reduce the number of CPUs or amount of memory on the target workload:

      1. Select a smaller cloud instance size with fewer CPUs or less memory that best fits your needs.

    • The target VM uses up to the maximum allowed number of NICs for the instance size. To migrate only some of the NICs:

      1. Select a cloud instance size with fewer NICs that best fits your needs. At least one NIC is required.

      2. Under Target Workload Settings, deselect the NICs that should not be migrated until the number of NICs for migration fits the selected instance.

    NOTE:The i3.16xlarge cloud instance size is not supported for migration of Windows Server 2008 R2 Workload to AWS. Use a supported cloud instance size other than i3.16xlarge.

    AWS Instance Tags

    AWS allows you to assign metadata to their resources in the form of tags thereby making it easy to manage, search for, and filter resources. To add tags, do the following:

    1. Click Add/Edit Tags and then click Create Tag.

    2. Specify a key and value for the tag.

    3. Click Apply.

    You can edit tags key and value, and also remove tags.

    Placement Groups

    This setting is applicable only if you set the Tenancy to run your instance as a shared instance.

    Select a placement group where you want to launch your instance.

    IMPORTANT:Placement Group configuration in Migrate is limited to cloud instance types supported by Amazon EC2. Refer to AWS EC2 Documentation for the latest information about placement groups and AWS rules and limitations for using them:

    IAM Role

    Select an AWS Identity and Access Management (IAM) user in your AWS account, with an appropriate IAM role for the user to perform migrations into the VPC using the AWS APIs.

    Key Pair

    Select the AWS EC2 Key Pair that you want to use for logging in to your AWS target instance. However, if you do not want to use a key pair, select Proceed without a key pair to use only the source credentials for logging in to your AWS target instance.

    NOTE:When you select a key pair, PlateSpin Migrate by default allows you to log in to the AWS target instance only by using the selected key pair. To enable logging into AWS Linux target instance either by using the key pair configured in the migration job or the source credentials, see Configuring Target Instance Logging With Key Pair or Source Credentials.

    For information about creating the key pair, see:

    Hostname

    Do one of the following:

    • To retain the same host name, select No Change.

    • To change the host name, select Set To and specify the new name.

      NOTE:An incremental replication is required if you change the host name at cutover.

    Domain / Workgroup

    (For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:

    • Workgroup: Workgroup_name

      where Workgroup_name is the workgroup name to which the source belongs.

    • Domain: Domain_name

      where Domain_name is the domain name to which the source belongs.

    NOTE:An incremental replication is required if you change the domain or workgroup name at cutover.

    Do one of the following depending on where you want the target workload to join:

    • When the source workload belongs to a workgroup: Assume that the source workload belongs to a workgroup named WorkGroup1.

      • For the target workload to join the same workgroup (WorkGroup1), retain the following existing selection:

        Workgroup: Workgroup1

      • For the target workload to join a different workgroup (say WorkGroup2), select Join Workgroup and specify the name as WorkGroup2.

      • For the target workload to join a domain, select Join Domain and specify the domain name you want the target to join.

    • When the source workload belongs to a domain: Assume that the source workload belongs to a domain named Domain1.

      • For the target workload to join a workgroup, click Join Workgroup and specify the name of the workgroup you want the target to join.

      • For the target workload to join the same domain (Domain1) with the domain registration settings preserved, retain the following existing selection:

        Domain: Domain1

      • For the target workload to join the same domain (Domain1) without preserving the domain registration settings, select Join Domain and specify the domain name as Domain1.

      • For the target workload to join a different domain, select Join Domain and specify the domain name you want the target to join.

    Domain Credentials

    (For Windows Workloads) If you select Join Domain, specify the domain administrator credentials.

    Network Connections

    1. To provide high-performance networking capabilities on the workload, PlateSpin Migrate selects the Enable Enhanced Networking option by default if the selected instance type supports only ENA adapter. However, if the selected instance type supports both ENA and Intel adapters, then select the Enable Enhanced Networking option if you want to use ENA adapter.

      IMPORTANT:

    2. For workloads that have more than one NIC, select Include for each NIC to be migrated. Deselect Include to exclude a NIC.

      • At least one NIC is required.

      • The number of NICs to migrate cannot exceed the maximum number of NICs supported by the selected cloud instance.

      • If the source workload is not part of the address space for the AWS VPN, then a public IP address is required for migration. To enable AWS to automatically assign a public IP address, you must include only one NIC for migration. This is because AWS supports assigning public IP address only to instances with a single network interface. To ensure that only public IP is used during migration, configure the UseOnlyPublicIPForAWS parameter in the PlateSpin Configuration settings for the Migrate server as True. See Configuring PlateSpin Migrate Server to Use Public IP Address for AWS Migrations.

    3. For each included NIC, select a network and subnet.

    4. (For primary NIC) Select Auto-assign Public IP to enable AWS to automatically assign a public IP address.

      NOTE:PlateSpin Migrate uses the EnablePublicIPForCloudInstance configuration parameter to control whether or not a public IP address should be assigned to the primary network interface of AWS instances. If the value of EnablePublicIPForCloudInstance is true, then Auto-assign Public IP option is selected by default and you cannot deselect it. However, if the value of EnablePublicIPForCloudInstance is false, then also Auto-assign Public IP option is selected by default, but you can deselect it if you do not want AWS to automatically assign a public IP address to primary NIC on the target instance. See Enabling Public IP Address for Target Instances on Cloud.

    5. For each included NIC, select one of the following:

      • DHCP: Obtain an IP address automatically assigned by a DHCP server.

      • Static: Specify one or more static IP addresses. The network mask and gateway are auto-populated based on the selected subnet. Click Advanced to add multiple IP addresses, edit an IP address, or remove an IP address. The IP addresses must be unique within the supported subnet.

    DNS Servers

    Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:

    • Primary DNS server: Specify the primary DNS server address.

    • Alternative DNS server: Specify an alternate DNS server address.

    • Additional DNS server: To specify additional DNS server addresses:

      1. Click Advanced.

      2. Specify the DNS server address.

      3. Click Add to add the server in the DNS Server Addresses list.

      4. Click OK.

    Services States on Target VM

    (For Windows Workloads) Select Windows services’ start conditions on the target VM. Start options are Automatic, Manual, Disabled, and Automatic (Delayed Start).

    Daemons States to Change

    (For Linux Workloads) Select Linux daemons’ start conditions on the target VM. Enable the daemon to start by selecting the check boxes at the appropriate runlevels (0 to 6) and Boot.

    Post-Migration Action

    Click Configure Action to select a previously configured custom action that you want to execute on your target workload as a part of the migration job. The command line parameters and timeout value that you previously configured for the selected action is displayed by default. You can edit these values as required. If you choose to timeout the action and have not specified any timeout value, then PlateSpin Migrate waits for a maximum period of 7200 seconds before timing out this action. For information about managing the post-migrations, see Managing Post-Migration Actions.

    Target Workload Test Settings

    (These settings are applied during the Test Cutover)

    Copy Target Workload Settings

    Click the Copy Target Workload Settings option to automatically copy the workload settings from Target Workload Settings (These settings are applied during the Run Cutover) section to Target Workload Test Settings (These settings are applied during the Test Cutover) section.

    AWS Agent

    For collecting metrics and logs from Amazon EC2 Instance on the target workload, select the Install CloudWatch Agent option to install the AWS CloudWatch agent on the target workload. This option is displayed for the following workloads that supports CloudWatch agent:

    • Red Hat Enterprise Linux (RHEL) versions 7.6, 7.5, 7.4, 7.2, 7.0, and 6.5

    • CentOS versions 7.6, 7.2, 7.0, 6.8, and 6.5

    • 64-bit versions of Windows server

    If the AWS CloudWatch Agent is already installed on the source workload, then this option is disabled.

    Tenancy

    Select one of the following options to specify whether your instance should run on a shared or a dedicated hardware:

    • Run a shared hardware instance: Your instance runs on a shared hardware and this is selected by default.

    • Run a dedicated instance: Your instance runs on a single-tenant hardware.

    • Launch this instance on a dedicated host: Your instance runs on a dedicated host, which is an isolated server already allocated for use in your account.

      NOTE:If you choose to launch the instance on a dedicated host, the OS licensing model on the target workload is always set to BYOL irrespective of the licensing model you selected.

      Set the following options based on your requirement:

      Set the following options based on your requirement:

      • Host: Select a specific host to launch the instance or select Use auto-placement to allow the instance to launch on to any host that has a matching instance type and auto-placement enabled. The Use auto-placement option is selected by default if any of the available dedicated hosts supports auto-placement.

      • Affinity: For a specific dedicated host, the affinity is always Host. However, if you set the Host option to Use auto-placement, then select one of the following:

        • Off: Restarts a stopped instance on any available host. This option is selected by default.

        • Host: Restarts a stopped instance on the same host where it was launched.

    Cloud Instance Size

    Click Change Cloud Instance Size to select a supported cloud instance size appropriate for your workload.

    • If an instance type that AWS supports is not listed, then you can configure the AWSPriceListRegion PlateSpin Configuration parameter to set its value to the region name that has a price list endpoint listing the desired instance type. See Configuring the AWS Region Price List Endpoint To Be Used for Discovering Supported AWS Instance Types.

    • For Linux workloads, you must ensure that the instance type you select for the Target Workload and Target Workload Test Settings must both be of the same type: Nitro or non-Nitro. Using a combination of Nitro and non-Nitro instances during Test Cutover and Run Cutover (that is, Nitro instance during Test Cutover and a non-Nitro instance during Run Cutover or vice versa) results in migration failure.

    • As AWS adds support for new instance types, Migrate detects them dynamically and displays them with an asterisk symbol. PlateSpin Migrate might not have tested such instance types that AWS recently added and support for such AWS instance types is experimental. For a list of the new instance types that Migrate supports in this release, see What’s New in the PlateSpin Migrate 2019.11 Release Notes.

    • For each release, PlateSpin Migrate adds support for new cloud instances and instance families that AWS has released up to a stipulated date prior to the PlateSpin Migrate release. For a list of the new instance types that Migrate supports in this release, see What’s New in the PlateSpin Migrate 2019.11 Release Notes.

      You can add definitions to the PlateSpin Server for new AWS Nitro Based instances and instance families to make the instances available in the AWS Cloud Instance Sizes list. See Displaying the AWS Nitro System Based Cloud Instance Sizes That AWS Recently Supported in the AWS Cloud Instance Sizes list.

    • The m5a, r5a, and F1 instance types are supported only for Linux workloads.

    • For migration of a source Windows Domain Controller workload, select a Nitro System based instance type such as c5, m5, r5, t3, c5d, m5d, or z1d.

    • AWS requires a minimum of Microsoft .NET Framework 4.5 for migration of Windows workloads to Nitro System based VM instances. To use Nitro System based instances, ensure that .NET 4.5 Framework or later is installed on the source Windows workload prior to Migrate discovery.

    By default, Migrate selects a cloud instance size that most closely matches your source workload for the following components:

    • Total number of cores

    • Amount of memory

    • Number of NICs

    • Network Performance

    • AWS Instance Family

    The default instance either meets or exceed the settings for each of these components on the source workload. However, you can choose a smaller instance size based on your requirements:

    • The target VM uses the allowed CPU and memory for the instance size. To reduce the number of CPUs or amount of memory on the target workload:

      1. Select a smaller cloud instance size with fewer CPUs or less memory that best fits your needs.

    • The target VM uses up to the maximum allowed number of NICs for the instance size. To migrate only some of the NICs:

      1. Select a cloud instance size with fewer NICs that best fits your needs. At least one NIC is required.

      2. Under Target Workload Settings, deselect the NICs that should not be migrated until the number of NICs for migration fits the selected instance.

    NOTE:The i3.16xlarge cloud instance size is not supported for migration of Windows Server 2008 R2 Workload to AWS. Use a supported cloud instance size other than i3.16xlarge.

    AWS Instance Tags

    AWS allows you to assign metadata to their resources in the form of tags thereby making it easy to manage, search for, and filter resources. To add tags, do the following:

    1. Click Add/Edit Tags and then click Create Tag.

    2. Specify a key and value for the tag.

    3. Click Apply.

    You can edit tags key and value, and also remove tags.

    Placement Groups

    This setting is applicable only if you set the Tenancy to run your instance as a shared instance.

    Select a placement group where you want to launch your instance.

    IMPORTANT:Placement Group configuration in Migrate is limited to cloud instance types supported by Amazon EC2. Refer to AWS EC2 Documentation for the latest information about placement groups and AWS rules and limitations for using them:

    IAM Role

    Select an AWS Identity and Access Management (IAM) user in your AWS account, with an appropriate IAM role for the user to perform migrations into the VPC using the AWS APIs.

    Key Pair

    Select the AWS EC2 Key Pair that you want to use for logging in to your AWS target instance. However, if you do not want to use a key pair, select Proceed without a key pair to use only the source credentials for logging in to your AWS target instance.

    NOTE:When you select a key pair, PlateSpin Migrate by default allows you to log in to the AWS target instance only by using the selected key pair. To enable logging into AWS Linux target instance either by using the key pair configured in the migration job or the source credentials, see Configuring Target Instance Logging With Key Pair or Source Credentials.

    For information about creating the key pair, see:

    Hostname

    Do one of the following:

    • To retain the same host name, select No Change.

    • To change the host name, select Set To and specify the new name.

      NOTE:An incremental replication is not required if you change the host name at Test Cutover.

    Domain / Workgroup

    (For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:

    • Workgroup: Workgroup_name

      where Workgroup_name is the workgroup name to which the source belongs.

    • Domain: Domain_name

      where Domain_name is the domain name to which the source belongs.

    NOTE:An incremental replication is not required if you change the domain or workgroup name at Test Cutover.

    Do one of the following depending on where you want the target workload to join:

    • When the source workload belongs to a workgroup: Assume that the source workload belongs to a workgroup named WorkGroup1.

      • For the target workload to join the same workgroup (WorkGroup1), retain the following existing selection:

        Workgroup: Workgroup1

      • For the target workload to join a different workgroup (say WorkGroup2), select Join Workgroup and specify the name as WorkGroup2.

      • For the target workload to join a domain, select Join Domain and specify the domain name you want the target to join.

    • When the source workload belongs to a domain: Assume that the source workload belongs to a domain named Domain1.

      • For the target workload to join a workgroup, click Join Workgroup and specify the name of the workgroup you want the target to join.

      • For the target workload to join the same domain (Domain1) with the domain registration settings preserved, retain the following existing selection:

        Domain: Domain1

      • For the target workload to join the same domain (Domain1) without preserving the domain registration settings, select Join Domain and specify the domain name as Domain1.

      • For the target workload to join a different domain, select Join Domain and specify the domain name you want the target to join.

    Domain Credentials

    (For Windows Workloads) If you select Join Domain, specify the domain administrator credentials.

    Network Connections

    1. To provide high-performance networking capabilities on the workload, PlateSpin Migrate selects the Enable Enhanced Networking option by default if the selected instance type supports only ENA adapter. However, if the selected instance type supports both ENA and Intel adapters, then select the Enable Enhanced Networking option if you want to use ENA adapter.

      IMPORTANT:

    2. For workloads that have more than one NIC, select Include for each NIC to be migrated. Deselect Include to exclude a NIC.

      • At least one NIC is required.

      • The number of NICs to migrate cannot exceed the maximum number of NICs supported by the selected cloud instance.

      • If the source workload is not part of the address space for the AWS VPN, then a public IP address is required for migration. To enable AWS to automatically assign a public IP address, you must include only one NIC for migration. This is because AWS supports assigning public IP address only to instances with a single network interface. To ensure that only public IP is used during migration, configure the UseOnlyPublicIPForAWS parameter in the PlateSpin Configuration settings for the Migrate server as True. See Configuring PlateSpin Migrate Server to Use Public IP Address for AWS Migrations.

    3. For each included NIC, select a network and subnet.

    4. (For primary NIC) Select Auto-assign Public IP to enable AWS to automatically assign a public IP address.

      NOTE:PlateSpin Migrate uses the EnablePublicIPForCloudInstance configuration parameter to control whether or not a public IP address should be assigned to the primary network interface of AWS instances. If the value of EnablePublicIPForCloudInstance is true, then Auto-assign Public IP option is selected by default and you cannot deselect it. However, if the value of EnablePublicIPForCloudInstance is false, then also Auto-assign Public IP option is selected by default, but you can deselect it if you do not want AWS to automatically assign a public IP address to primary NIC on the target instance. See Enabling Public IP Address for Target Instances on Cloud.

    5. For each included NIC, select one of the following:

      • DHCP: Obtain an IP address automatically assigned by a DHCP server.

      • Static: Specify one or more static IP addresses. The network mask and gateway are auto-populated based on the selected subnet. Click Advanced to add multiple IP addresses, edit an IP address, or remove an IP address. The IP addresses must be unique within the supported subnet.

    DNS Servers

    Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:

    • Primary DNS server: Specify the primary DNS server address.

    • Alternative DNS server: Specify an alternate DNS server address.

    • Additional DNS server: To specify additional DNS server addresses:

      1. Click Advanced.

      2. Specify the DNS server address.

      3. Click Add to add the server in the DNS Server Addresses list.

      4. Click OK.

    Services States on Target VM

    (For Windows Workloads) Select Windows services that must be automatically stopped on the target VM.

    Daemons States to Change

    (For Linux Workloads) Select Linux daemons that must be automatically stopped on the target VM.

    Tag

    Post-Migration Action

    Click Configure Action to select a previously configured custom action that you want to execute on your target workload as a part of the migration job. The command line parameters and timeout value that you previously configured for the selected action is displayed by default. You can edit these values as required. If you choose to timeout the action and have not specified any timeout value, then PlateSpin Migrate waits for a maximum period of 7200 seconds before timing out this action. For information about managing the post-migrations, see Managing Post-Migration Actions.

    Tag

    Select a tag to assign to the workload. For more information about tags, see Using Tags to Track Logical Associations of Workloads.

  9. (Optional) To change the target, click Change Target.

    NOTE:If you change the target, all the settings you specified will be cleared.

  10. Do one of the following:

    • Click Save to save the settings.

    • Click Save and Prepare to save the settings and start preparing the workload migration.

    • Click Cancel to exit.