To initiate a peer-to-peer workload migration to a physical machine:
(Recommended) Use PlateSpin Analyzer to ensure that:
Your source operating system and hardware are supported by PlateSpin Migrate.
PlateSpin Migrate’s X2P device driver database contains device drivers that your target requires for the operating system being ported.
See Analyzing Suitability of Discovered Windows Workloads For Conversion to Physical Machines.
Discover your source workload. See Workload Discovery in the Migrate Web Interface.
(Conditional) If drivers for the physical target are not available in the PlateSpin Migrate’s X2P device driver database, upload the required drivers to the database.
Register your target physical machine with PlateSpin Migrate by booting it with the PlateSpin ISO.
See Registering and Discovering Details for Target Physical Machines with PlateSpin ISO.
Launch the PlateSpin Migrate Web Interface.
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.
Depending on whether you want to perform full replication or incremental replication, do one of the following:
Full Replication: Select the target physical machine to which you want to migrate the source workload.
Incremental Replication: Select the target type as Physical Targets. From the list of the prepared target workloads, select a physical target that matches the source workload you want to migrate. If no matching physical target workload is listed, add a physical target and then boot up this physical target and use the PlateSpin Migrate ISO Image to register it with Migrate server.
Click Configure Migration.
Configure the following settings:
NOTE:All of the following settings are applicable for full replication of the workload. Some of the listed settings might not display or display differently when you configure incremental replication for the workload. For example:
The Virtual Machine Configuration Path setting does not display because a target workload matching the source workload must already be available to transfer only the differences from the source to this target.
The Volume Mapping setting displays the volumes and their mappings. You can edit the volume mappings.
Setting Name |
Description |
---|---|
Schedule Settings |
|
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. |
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 currently not 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. |
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) Displays the disks to which volume groups are mapped. |
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) Specify one or more LVM logical volumes to be migrated for a Linux workload. |
Replication Networks for Source |
Specify one or more network interfaces (NIC or IP address) on the source to use for replication traffic. |
Services to Stop Before Any Replication |
(For Windows Workloads) We recommend that all the non-VSS compliant services or anti-virus 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 daemons that you want to be temporarily stopped on the source workload before replication. These daemons will be restored after replication completes. |
Daemons to Stop for Cutover with Replication |
(For Linux Workloads) Select the Linux daemons that should be permanently stopped on the source workload for Cutover with any Replication. The daemons stopped on the source workload during the replication process are not restored after Cutover. The stopped daemons 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) |
|
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:
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 |
Select the local area connection and then select one of the following:
For Windows workloads that have more than one NIC, select the connection for each NIC. |
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’ start conditions on the target VM. Start options are Automatic, Manual, Disabled, and Automatic (Delayed Start). |
Daemons States on Target VM |
(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. |
Tag |
|
Tag |
Select a tag to assign to the workload. See Managing Workload Tags. |
(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 Cancel to exit.