PlateSpin Migrate provides additional tools you can use to help customize your migration efforts.
Some aspects of your PlateSpin Server’s behavior are controlled by configuration parameters that you set on a configuration web page residing your PlateSpin Server host:
https://Your_PlateSpin_Server/PlateSpinConfiguration/
Under normal circumstances you should not need to modify these settings unless you are advised to do so by PlateSpin Support.
Use the following procedure for changing and applying any configuration parameters:
Log in as Administrator to the PlateSpin Migrate Web Interface, then open the PlateSpin Server Configuration page at:
https://Your_PlateSpin_Server/PlateSpinConfiguration/
Locate the required server parameter and change its value.
Save your settings and exit the page.
No reboot or restart of services is required after the change is made in the configuration tool.
Table 3-5 lists common advanced settings that you might encounter in various migration scenarios. See the related documentation for more information.
Table 3-5 Common Advanced Settings in PlateSpin Configuration
|
Common Issue or Concern |
Reference |
|---|---|
|
Changing the adapter type used during the Target Take Control process of workload migration to a target VM on a Hyper-V Host |
Specifying the Network Adapter Type to Use for Migrations to Hyper-V during Target Take-Control |
|
Increasing the upload size limit on post-migration actions |
|
|
Optimizing data transfer over WAN connections |
|
|
Enabling source workloads to initiate contact with target workloads for replications when sources are registered using Migrate Agent |
|
|
Adding or removing applications from a list of applications that will be temporarily disabled for conversions |
Configuring Applications Known to Cause Boot Failure on Windows Target Workloads |
|
Rebranding some features in the Web Interface |
Section B.0, Rebranding the UI for PlateSpin Migrate Web Interface |
|
Configuring parameters that control migration behavior for migrations to Amazon Web Services |
|
|
Configuring Azure tags used by all migrations to Azure Cloud on the Migrate server |
|
|
Configuring parameters that control migration behavior for migrations to VMware vCloud Director |
|
|
Configuring parameters that control migration behavior for migrations to Microsoft Hyper-V |
The PlateSpin Migrate Client installation includes a command line interface (CLI) tool to help you perform common migrations tasks. Conversion jobs using .ini files is supported onto VMware and Hyper-V targets only. See Section I.0, Using the PlateSpin Migrate Client Command Line Interface
PlateSpin Migrate Client provides the PlateSpin Analyzer to determine whether discovered Windows machines are suitable for migration jobs. Before you begin any large-scale migration projects, you should identify potential migration problems and correct them beforehand. See Analyzing Suitability of Discovered Windows Workloads For Conversion to Physical Machines.
The Migrate Agent utility is a command line utility that you can use to install, upgrade, query, or uninstall the block-based transfer drivers. The utility also enables you to register source workloads with PlateSpin Migrate servers and send details about the workloads to the server via HTTPS (TCP/443). Registration allows you to add workloads that cannot be discovered, such as for Migrate Servers in Microsoft Azure when no VPN is configured between the Migrate server and the source workloads.
A reboot is not required for source Linux workloads. Although a reboot of the source Windows workload is always required when you install, uninstall, or upgrade drivers, the Migrate Agent utility allows you to better control when the action occurs and therefore, when the server reboots. For example, you can use the Migrate Agent utility to install the drivers during scheduled down time, instead of during the first replication. See Section F.0, Migrate Agent Utility.
The PlateSpin ISO file enables you to register target physical machines and target virtual machines with PlateSpin Migrate servers and send details about them to the server via HTTPS (TCP/443). Registration allows you to add target machines that cannot be discovered because they have no operating system installed. See Section G.0, PlateSpin ISO Image.