This section contains information on documentation content changes that were made in the English version of the PlateSpin Migrate User Guide since the General Availability of PlateSpin Migrate 2018.11.
|
Location |
Update |
|---|---|
|
Configuring an Application in Azure to Represent PlateSpin Migrate Configuring a Contributor User for PlateSpin Migrate to Use Enabling PlateSpin Replication Environment for Azure Subscriptions |
These Prerequisites for Azure Migration topics were updated to reflect recent changes by Microsoft in the Azure Portal UI. They also clarify the required permissions and options. |
|
Location |
Update |
|---|---|
|
Configuring an Application in Azure to Represent PlateSpin Migrate |
Updated the procedure for registering an azure application because Azure recently replaced the legacy way of registering the application with a new and improved method of registration. |
|
Registering and Discovering Details for Target VMs on Virtual Hosts with PlateSpin ISO Registering and Discovering Details for Target Physical Machines with PlateSpin ISO |
PlateSpin Migrate discontinues support for migrations of workloads with multipath I/O (MPIO) enabled. We recommend that you perform migration with a single path, and then enable MPIO on the cutover workload. |
|
Location |
Update |
|---|---|
|
This is new |
|
|
Supported Microsoft Windows Workloads For Migration to Non-Cloud Platforms Supported Workloads For Migration to Amazon Web Services |
PlateSpin Migrate does not support migration of Active Directory domain controller servers with Flexible Single Master Operation (FSMO) roles on them. For information, see Best Practice Tips for Active Directory Domain Controller Conversions (KB Article 7920501). |
|
Location |
Update |
|---|---|
|
PlateSpin Migrate does not support discovery, configuration, and migration actions for a target VMware DRS Cluster where one or more hosts are in maintenance mode. See Best Practices for Maintaining or Updating VMware Environments That Are Configured as Migration Targets. |
|
Location |
Update |
|---|---|
|
Supported Source Workloads For Migration to Non-Cloud Platforms |
To install Migrate Agent Utility for Linux, your source machine must have GNU C Library (glibc) 2.11.3 or higher installed. |
|
For X2P migrations, the target workload should have only a single path to each of its SAN disks. PlateSpin supports only one unique path to each LUN that is used during the migration process. |
|
|
This section in new. |
|
|
Understanding PlateSpin Replication Environment Used for Migration of Workloads to vCloud |
The SLES 11 PRE also supports migration of 32-bit workloads. |
|
RHEL 7.4 and later kernel versions have built-in drivers for ENA. |
|
|
Removed conditions that are no longer required. |
|
|
Updated Network Connections in Target Workload Settings and Target Workload Test Settings: PlateSpin MIgrate selects the Enable Enhanced Networking option by default if the selected instance type supports only ENA adapter. However, if the selected instance type supports both ENA and Intel adapters, then select the Enable Enhanced Networking option if you want to use ENA adapter. |
|
|
Section K.0, Using the iPerf Network Test Tool to Optimize Network Throughput for PlateSpin Products |
Linux automatically doubles the requested TCP buffer size. If you use iperf on a Linux server, the win_size value for the -w option should be only 1/2 of the desired value (that is, <win_size>/2). Otherwise, you will inadvertently test with a buffer size that is twice the desired value. The value for the FileTransferSendReceiveBufferSize parameter setting is the optimal value you determined for win_size. Migrate automatically takes the Linux behavior of halving buffer sizes into consideration when it configures your Linux workloads. |
|
Location |
Update |
|---|---|
|
Migrate supports AWS instance types based on x86 and x86_64 processor architectures. |
|
|
This section was moved from |
|
|
This section is new. |