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 VMware vCloud Organization as a migration target, click Targets > Add Target, and then configure the target vCloud platform.
See Table 17-9, Options for VMware vCloud Organization Target.
On the Workloads page, select the workload you want to configure.
Click Configure Migration.
Select one of the following based on the scope of data you want to transfer from the source to the target:
Full Replication: A full volume of data transfer takes place from the source to the target.
Incremental Replication: Only differences are transferred from the source to the target, provided they 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 VMware vCloud Director. However, you can schedule Incremental Replications for subsequent replication of data. See Incremental Recurrence in Step 8.
Select an existing vCloud target platform to which you want to migrate the source workload.
Click Configure Migration.
Configure the following settings. Ensure that the IP address for the source workload, the replication network for target, the cutover network, and the test cutover network are all different.
Schedule Settings |
|
Incremental Recurrence |
|
Specify the following:
|
|
Full Replication |
|
Do one of the following:
NOTE:You must prepare the workload prior to the scheduled time.The full replication cannot run unless the target VM exists and the workload preparation is complete. Migrate skips the scheduled full replication and retries it at the next scheduled time. |
|
Blackout Window |
|
Use these settings to force a replication blackout. The replication blackout suspends scheduled replications during peak utilization hours or prevents conflicts between VSS-aware software and the PlateSpin VSS block-level data transfer component. To specify a blackout window, click Edit and do the following:
NOTE:The blackout start and end times are based on the system clock on the PlateSpin Server. |
|
Compression Level |
|
These settings control 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 |
|
These settings control the bandwidth throttling. PlateSpin Migrate enables you to control the amount of available bandwidth consumed by direct source-to-target communication over the course of a workload migration. You can specify a throughput rate for each migration job. Throttling provides a way to prevent migration traffic from congesting your production network and to reduce the overall load of your PlateSpin Server. To throttle replications to a specified rate, specify the required throughput value in Mbps and the time pattern. |
|
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. |
|
CPU |
|
(For migration to vCloud and VM platforms using VMware 5.1, 5.5, and 6.0 with a minimum VM hardware Level 8) Specify the number of sockets and the number of cores per socket for the target workload. It automatically calculates the total cores. This parameter applies on the initial setup of a workload with an initial replication setting of Full Replication. NOTE:The maximum number of cores the workload can use is subject to external factors such as the guest operating system, the VM hardware version, VMware licensing for the ESXi host, and ESXi host compute maximums for vSphere (see ESXi/ESX Configuration Maximums (VMware KB 1003497)). Some distributions of a guest OS might not honor the cores and cores per socket configuration. Instead they will retain their original cores and sockets settings as installed. |
|
Organization Virtual Data Center |
|
(For migration to vCloud) Select a virtual data center associated with your organization. |
|
vApp |
|
Specify a name for the VMware vApp. |
|
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 path to the hard disk on the target virtual machine. |
|
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 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) Specify one or more LVM logical volumes to be migrated for a Linux workload. |
|
Replication Network for Target |
|
By default, the replication NIC is the primary NIC that you specify in Target Workload Settings> Network Connections. Specify a network interface (NIC or IP address) on the target to use for replication traffic.
|
|
Replication Networks for Source |
|
Select 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. |
|
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) |
|
VM Memory |
|
Specify the amount of memory allocated to the target workload. |
|
VM Tools |
|
To install the VM tools, select the Install VM Tools option. This option is selected by default. |
|
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 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 |
|
(For Linux Workloads) 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 on Target VM |
|
(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. |
|
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. |
|
VM Memory |
|
Specify the amount of memory allocated to the target workload. |
|
VM Tools |
|
To install the VM tools, select the Install VM Tools option. This option is selected by default. |
|
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 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. The default Primary Connection is the first NIC in the list.
|
|
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.