26.2 Configuring Migration of a Workload to Microsoft Azure

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 Microsoft Azure Location as a migration target, click Targets > Add Target, and then configure the target Azure cloud platform.

     See Table 17-5, Options for Microsoft Azure Location Target.

  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 Azure Cloud. However, you can schedule Incremental Replications for subsequent replication of data. See Incremental Recurrence in Step 8.

  6. Select an existing Microsoft Azure Location target platform to which you want to migrate the source workload. 

    To verify the availability in the target location of Premium Blob Storage for unmanaged disks or of Managed Disks, refer to the Microsoft Azure Products Available by Region.

  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.

    Azure Resource Group

    Specify a resource group to use for the target VM resources. Do one of the following:

    • Select an existing resource group from the list.

      NOTE:An existing resource group is required for target VMs that you will add to an Azure Availability Set. Before you configure the workload, use the Azure portal to create an Availability Set in a resource group for the specified target location. The Availability Set definition determines whether you can use the set in combination with Azure Managed Disks.

    • Allow PlateSpin to create a new resource group with the default name:

      <hostname>-Resources

    • Type the name to use when PlateSpin creates a new resource group.

    Virtual Machine Name

    Specify a display name for the new virtual machine.

    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

    Specify the information for disks, depending on whether the target VM uses Azure Managed Disks or uses Storage Accounts and unmanaged disks.

    Azure Managed Disks

    Managed disks are resource objects that represent the actual replicated disks being managed. The Azure Managed Disks setting applies to all disks for the target VM. Using Azure Managed Disks is optional and is enabled by default. Deselect the option to specify an Azure Storage Account and use unmanaged disks in Azure. See Prerequisites for Azure Storage.

    To use Azure Managed Disks for the Target VM:

    1. Select Use Managed Disks to enable Azure Managed Disks for the VM. This is the default setting.

    2. Specify the Storage Type to use for hosting the managed disks for the target VM:

      • Standard HDD (hard disk drives)

      • Standard SSD (solid state drives)

        NOTE:Standard SSD option is not applicable for migrations to Azure Stack.

      • Premium SSD

    3. (Optional) Under Disks, specify a custom name for one or more managed disk. You do not need to specify a storage account or a location in a storage account.

    Managed Disk Names:

    You can optionally provide a custom name for each managed disk. You cannot rename the managed disk after it is created. PlateSpin Migrate applies a default name for each managed disk in the following format:

        <parent VM name>-<context>-<numeric suffix>

    Valid characters for the resource name are alphanumeric, underscore (_), hyphen (-), and period (.). The name should start with a letter or number, and end with a letter, number, or underscore. The maximum name length is 80 characters. Managed disk names do not have a .vhd extension.

    Unmanaged Disks:

    If you disabled Use Managed Disks, specify the Datastore (Azure Storage Account) and the disk path to use in the datastore.

    To use unmanaged disks for the Target VM:

    1. Deselect Use Managed Disks.

    2. Under Disks, specify the Datastore (Azure Storage Account) and Disk Path to use for the disk for the target VM.

    3. (Optional) Specify a custom name for one or more disk.

    Unmanaged Disk Names:

    You can optionally provide a custom name for each unmanaged disk. Names must comply with the naming conventions for disks. Disk names have a .vhd extension.

    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.

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

    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.

    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 you do not use an Azure VPN, the replication NIC requires a public IP address that is automatically assigned by Azure. Click Edit, then select Create Public IP.

    3. Specify a resource group to use for the replication network. The Azure Resource Group setting is the default. To specify a different resource group, click Edit and do one of the following:

      • Type the name to use when PlateSpin creates a new resource group.

      • Select an existing resource group from the list.

    4. 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.

    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 Azure 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

    (For Windows Workloads) Select the boot services that you want to disable on the target workload.

    Target Workload Settings

    (These settings are applied during the Run Cutover)

    Azure Agent

    Specify whether to install the latest Azure Virtual Machine Agent on the target VM. If the check box is selected (enabled), Migrate installs the agent on the target workload at Cutover.

    If the Azure VM Agent is installed on the source, the agent will be uninstalled on the target workload and reinstalled using the latest version of the agent.

    Azure Availability Set

    An Azure Availability Set is an Azure service that provides high availability to two or more member VMs by deploying them in different fault domains and update domains. VMs must be created in the Availability Set. You cannot add an existing VM to an Availability Set. See Prerequisites for Using Azure Availability Sets.

    Using an Availability Set is optional. The default setting is No Availability Set. Click Change Availability Set to select an Availability Set from a list of sets available within the specified Azure Resource Group in Migration Settings.

    NOTE:After Azure assigns the physical hardware for the Availability Set, Azure limits the cloud instance sizes and networks that can be used for future member VMs. PlateSpin Migrate might prompt you to choose different cloud instance sizes or networks accordingly.

    Azure Tags

    Click Edit Tags to access the dialog where you can configure the tag names and values as appropriate for the workload.

    You can specify up to 8 tags for the workload. Global tags are pre-populated automatically. Required global tags with fixed values are applied automatically to the workload and cannot be modified. You must specify a value for a required tag if its value is not fixed. For optional global tags, you can modify the tag name or value, or you can remove them. You can optionally specify other tags, up to the maximum of 8 tags per workload.

    You cannot modify tags and values for the workload after a successful full replication occurs. Changes to the global settings for tag names and values will not apply to migrations in this state.

    See Using Azure Cloud Tags for Azure Migrations.

    Cloud Instance Size

    Select the cloud instance size appropriate for your workload and the storage account type for the target platform.

    IMPORTANT:The Cloud Instance Size must be of the same storage type as the target account: HDD or SDD. Otherwise, you receive a validation error. To verify the availability in the target location of Premium Blob Storage for unmanaged disks or of Managed Disks, refer to the Microsoft Azure Products Available by Region.

    By default, PlateSpin selects a cloud instance size that supports the same Storage account type and that most closely matches your source workload for the following components:

    • Total number of cores

    • Amount of memory

    • Number of data disks

    • Number of NICs

    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 data disks for the instance size. To migrate only some of the data disks:

      1. Select a smaller cloud instance size with fewer data disks that best fits your needs.

      2. Deselect the volumes that should not be migrated until the number of disks for migration fits the selected instance.

    • 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 number of data disks consumed by volumes on the target VM cannot exceed the maximum number of data disks supported by the selected cloud instance.

    • In the Cloud Instance Size list, the Supports SSD Storage column indicates the storage account type of the instance: HDD Storage (No) or SDD Storage (Yes). Ensure that your new instance size supports the same storage account type as the target platform.

    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. 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.

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

    3. Ensure that the Primary NIC is properly configured for its role as Primary. The default Primary Connection is the first NIC in the list. For more information, see Azure Networking Guidelines.

    4. If you do not use an Azure VPN, the primary NIC requires a public IP address that is automatically assigned by a Azure. For the primary NIC, click Edit, then select Create Public IP.

      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 Azure instances. If the value of EnablePublicIPForCloudInstance is true, then Create Public IP option is selected by default and you cannot deselect it. However, if the value of EnablePublicIPForCloudInstance is false, then Create Public IP option is deselected by default, but you can select it if you want Azure 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:

      1. Specify a resource group to use for the NIC. The Azure Resource Group setting is the default. To specify a different resource group, click Edit and do one of the following:

        • Type the name to use when PlateSpin creates a new resource group.

        • Select an existing resource group from the list.

      2. 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.

    Azure Agent

    Specify whether to install the latest Azure Virtual Machine Agent on the target VM. If the check box is selected (enabled), Migrate installs the agent on the target workload at Test Cutover.

    If the Azure VM Agent is installed on the source, the agent will be uninstalled on the target workload and reinstalled using the latest version of the agent.

    Azure Availability Set

    An Azure Availability Set is an Azure service that provides high availability to two or more member VMs by deploying them in different fault domains and update domains. VMs must be created in the Availability Set. You cannot add an existing VM to an Availability Set. See Prerequisites for Using Azure Availability Sets.

    Using an Availability Set is optional. The default setting is No Availability Set. Click Change Availability Set to select an Availability Set from a list of sets available within the specified Azure Resource Group in Migration Settings.

    NOTE:After Azure assigns the physical hardware for the Availability Set, Azure limits the cloud instance sizes and networks that can be used for future member VMs. PlateSpin Migrate might prompt you to choose different cloud instance sizes or networks accordingly.

    Cloud Instance Size

    Select the cloud instance size appropriate for your workload and the storage account type for the target platform.

    IMPORTANT:The Cloud Instance Size must be of the same storage type as the target account: HDD or SDD. Otherwise, you receive a validation error. To verify the availability in the target location of Premium Blob Storage for unmanaged disks or of Managed Disks, refer to the Microsoft Azure Products Available by Region.

    By default, PlateSpin selects a cloud instance size that supports the same Storage account type and that most closely matches your source workload for the following components:

    • Total number of cores

    • Amount of memory

    • Number of data disks

    • Number of NICs

    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 data disks for the instance size. To migrate only some of the data disks:

      1. Select a smaller cloud instance size with fewer data disks that best fits your needs.

      2. Deselect the volumes that should not be migrated until the number of disks for migration fits the selected instance.

    • 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 number of data disks consumed by volumes on the target VM cannot exceed the maximum number of data disks supported by the selected cloud instance.

    • In the Cloud Instance Size list, the Supports SDD Storage column indicates the storage account type of the instance: HDD Storage (No) or SDD Storage (Yes). Ensure that your new instance size supports the same storage account type as the target platform.

    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

    Available NICs match the included NICs in Target Workload Settings > Network Connections.

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

    2. Ensure that the Primary NIC is properly configured for its role as Primary. The default Primary Connection is the first NIC in the list. For more information, see Azure Networking Guidelines.

    3. If you do not use an Azure VPN, the primary NIC requires a public IP address that is automatically assigned by a Azure. For the primary NIC, click Edit, then select Create Public IP.

      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 Azure instances. If the value of EnablePublicIPForCloudInstance is true, then Create Public IP option is selected by default and you cannot deselect it. However, if the value of EnablePublicIPForCloudInstance is false, then Create Public IP option is deselected by default, but you can select it if you want Azure to automatically assign a public IP address to primary NIC on the target instance. See Enabling Public IP Address for Target Instances on Cloud.

    4. For each included NIC:

      1. Specify a resource group to use for the NIC. The Azure Resource Group setting is the default. To specify a different resource group, click Edit and do one of the following:

        • Type the name to use when PlateSpin creates a new resource group.

        • Select an existing resource group from the list.

      2. 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.

    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

    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.