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:
Launch the PlateSpin Migrate Web Interface.
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.
On the Workloads page, select the workload you want to configure.
Click Configure Migration.
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.
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.
Click Configure Migration.
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:
NOTE:
|
|
|
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:
|
|
|
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:
|
|
|
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:
|
|
|
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:
|
|
|
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:
|
|
|
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:
|
|
|
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:
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:
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.
|
|
|
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. |
|
|
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:
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:
|
|
|
Hostname |
|
|
Do one of the following:
|
|
|
Domain / Workgroup |
|
|
(For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:
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:
|
|
|
Domain Credentials |
|
|
(For Windows Workloads) If you select Join Domain, specify the domain administrator credentials. |
|
|
Network Connections |
|
|
|
|
DNS Servers |
|
|
Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:
|
|
|
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:
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:
|
|
|
Hostname |
|
|
Do one of the following:
|
|
|
Domain / Workgroup |
|
|
(For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:
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:
|
|
|
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.
|
|
|
DNS Servers |
|
|
Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:
|
|
|
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. |
(Optional) To change the target, click Change Target.
NOTE:If you change the target, all the settings you specified will be cleared.
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.