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 Section 19.6.1, Workload Discovery in the Migrate Client.
(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 Section 18.6, Registering and Discovering Details for Target Physical Machines with PlateSpin ISO.
Launch Migrate Client, then start a peer-to-peer workload migration.
The Source and Target panes display workloads and targets applicable to the selected type of a migration job.
See Section 25.2, Initiating a Migration Job.
Under Tasks, select the conversion type, depending on your goals for the migration:
Copy Workload
Move Workload
In the Action dialog, the Transfer Scope is set to Full Migration.
In the Source pane, select the workload you want to migrate.
In the Target pane, select target physical machine for the migration.
Read the validation messages at the bottom of the window.
Click Configure Job to access the Peer-to-Peer Migration Job window.
Configure the required parameters of the job.
See Section 25.0, Configuration Essentials.
Setting Name |
Description |
---|---|
License |
|
Licenses |
PlateSpin Migrate automatically selects the best license key for a migration job. If you have multiple license keys, you can specify the license key to use for the workload, assuming licenses are available (neither expired nor exhausted). To specify an alternate key to use:
|
Conversion |
|
Transfer Scope |
Set by default to Full Migration. |
Transfer Method |
Specify how data is transferred from source to target. The availability depends on your workload and migration job type.See Section 2.2, Supported Data Transfer Methods. |
Source Machine End State |
Specify whether to shut down the source workload after a successful cutover. For a workload move, Shutdown is selected by default. |
Target Virtual Machine End State |
Specify whether to power on, power off, or suspend the target workload after a successful cutover. |
Network |
|
Compression |
Specify whether to compress data during transmission between the source and target workloads, and the level of data compression to apply: Fast, Optimal, or Maximum. Compression is disabled by default.See Section 25.10, Compression during Data Transfer. |
Encryption |
Select Encrypt Data Transfer to encrypt the data as it is transferred from source to target.See Section 2.3, Security and Privacy. |
Bandwidth Throttling |
Select Enable Throttling to control the amount of available bandwidth consumed by direct source-to-target communication over the course of a workload migration. Specify the required throughput value in Mbps and the time pattern. Bandwidth throttling is disabled by default. See Section 25.11, Bandwidth Throttling during Data Transfer. Time-based throttling is based on the source server time. |
Advanced Additional Source Machine Addresses |
Specify additional IP addresses for source workloads to enable communication in environments that use network address translation (NAT). See Section 2.6.6, Migrations Across Public and Private Networks through NAT. |
Schedule |
|
Schedule |
Specify when to start the migration job:
NOTE:You must prepare the target machine prior to the scheduled time.The full replication cannot run unless the target machine is available. Migrate skips the scheduled full replication and retries it at the next scheduled time. |
Source Credentials |
(Windows) Specify the account user name with local or domain-level administrative privileges and a valid password. Use this format:
(Linux) Specify the root or root-level user name and a valid password. |
Target Credentials |
Not required. |
Alerts |
|
Receive Event Notifications |
Specify whether to send email notifications for event conditions. You must configure an SMTP server to use this feature. See Section 5.3.1, Notification Service Using Migrate Client. |
Receive Progress Notifications |
If you enable Event notifications, you can optionally receive progress notifications at a specified interval. |
Send to Addresses |
Add or remove valid email addresses for recipients of the notifications. |
Take Control Settings |
|
Target Virtual Machine |
Under Target Virtual Machine, click Configure, then specify the options for the virtual network and the TCP/IP settings for the replication NIC, then click OK. |
Post-Migration |
|
Action |
Specify a pre-configured action from the PlateSpin Migrate library.See Section 6.5, Managing Post-Migration Actions (Windows and Linux). |
Execution Parameters |
Specify the command line command to run the selected action. You can specify a timeout for the execution. |
Credentials |
Specify the user name and password to use for the post-migration tasks. You can optionally use the source credentials. |
(Target VMs using X2P workflow) In the Virtual Machine Configuration section of the Migration Job window, click General, then configure the required settings.
PlateSpin Migrate displays target virtual machine configuration options specific to the selected target and also provides access to advanced configuration options for some platforms. For information about host-specific configuration options, see:
Setting Name |
Description |
---|---|
Virtual Machine Name |
Specify a name to use for the target VM as it appears in the virtual host environment. |
Number of CPUs |
Select the number of CPUs to assign to the target VM. For example, you can convert a single-processor workload to a multi-processor VM, or a multi-processor workload to a single-processor VM. |
Virtual Machine Memory Allocation |
Specify the amount of virtual memory. |
In the Network Configuration section of the Migration Job window, configure the following settings:
Setting Name |
Description |
---|---|
Network Configuration |
|
Network Identification Settings for Windows |
|
Host Name |
Specify the desired host name for the target machine. |
Generate New SID |
When this option is selected, the target workload is assigned a new System Identifier (SID). Credentials are required only for Windows 2008 systems, and must be the credentials for the local (embedded) Administrator account. If this account has been locally renamed on the source, provide the new name. |
Member of Domain / Workgroup |
Select the required option and type the name of the domain or workgroup that you want the target machine to join. |
Preserve Source Server’s Domain Registration |
Preserves domain registration and ensures that the source server domain registration remains intact during migration. If you disable this option, the source machine’s domain account is transferred to the target machine. The source server still appears to be on the domain, but does not have a valid connection. |
Domain Credentials |
If the target machine is to be part of a domain, specify valid credentials for a user account with permission to add servers to the domain, such as a member of the Domain Admins group or Enterprise Admins group. |
Network Identification Settings for Linux |
|
Host Name |
On the Network Identification tab, specify the desired host name for the target machine. |
DNS |
Use the Add, Edit, and Remove buttons to manage DNS server entries for the new virtual machine. |
In the Operating System and Applications Configuration section of the Migration Job window, configure the following settings:
Setting Name |
Description |
---|---|
Operating System and Application Configuration |
|
Windows Services (Target) |
Select Windows services’ start conditions on the target VM after cutover. Start options are Automatic, Manual, Disabled, and Automatic (Delayed Start). To modify the settings:
|
Live Transfer Services (Source) |
Specify the Windows services to stop on the source workload during data transfers. 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. To modify the settings:
|
Linux Daemons (Target) |
Specify the start states for daemons on the target VM after cutover. To modify the settings:
|
Live Transfer Daemons (Source) |
Specify the daemons to stop on the source workload during data transfers. To modify the settings:
|
In the Drive Configuration section of the Migration Job window, configure the following settings:
Setting Name |
Description |
---|---|
Drive Configuration |
|
Hard Drives |
Specify drive and volume configurations to be migrated. |
Disks |
Specify the path to the hard disk on the target virtual machine. |
Volumes |
Select volumes to be included in the target for migration. |
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. |
Converted Logical Volumes |
(For Linux Workloads) Specify one or more LVM logical volumes to be migrated for a Linux workload. |
(Target VMs using X2P workflow) PlateSpin Migrate displays storage configuration options specific to the selected target and also provides access to advanced configuration options for some platforms. For information about host-specific configuration options, see:
In the Additional Items for Review section of the Migration Job window, review errors and messages about the workload configuration. You must resolve errors before you can submit the migration job.
Click OK.