Ensure that your source workloads and network environment meets the following requirements for using the Migrate Agent Utility.
Migrate Agent is supported only for live migrations.
Migrate Agent is supported for automated migrations. You can perform the migration using Migrate Client or Migrate Web Interface.
Migrate Agent is not supported for use with semi-automated (X2P) migrations.
When you use the Migrate Agent for workload registration and migration, ensure that your migration environment meets the following requirements:
Public IP addresses are required for the PlateSpin Migrate server host, replication network, and target machines. In some deployment scenarios, public IP addresses are also required for source machines.
Ensure that workloads can reach the public IP address for Migrate server.
Set the AlternateServerAddress parameter to the Migrate server’s public IP address on the PlateSpinConfiguration page. For Migrate servers deployed from a cloud marketplace, Migrate automatically adds the public IP address to this parameter. See Configuring Alternate IP Addresses for PlateSpin Server.
Enable a public IP address for the replication network when you configure the migration for a workload.
Migrate automatically configures public IP addresses on target machines during migration.
For information about network requirements for registration and migration, see
NOTE:Refer to the deployment diagrams based on your migration target to understand the ports and flow of information between the various migration components. See Section III, Preparing Your Migration Environment.
Ensure that you configure source workloads to support outbound traffic for the following ports:
HTTPS port (TCP/443)
Replication port (TCP/3725 is the default)
The replication port is configurable. If you modify the FileTransferPort parameter on the PlateSpin Configuration page, you must modify your firewall settings accordingly.
When you use the Migrate Agent on the source workload, the source workload contacts the target workload for data transfers. You must reconfigure the replication port direction on the Migrate server.
Change the SourceListensForConnection parameter from True to False on the PlateSpinConfiguration page. For Migrate servers deployed from a cloud marketplace, this parameter is set to False by default. See Configuring the Contact Direction for the Replication Port.
For cloud-based Migrate servers, the server is configured by default for migration to the target type that matches its parent could environment. If the source workloads are in the parent cloud environment for migration to a different target, you must remove the default value (leave the field blank) for the ServerIsHostedInCloud parameter to allow all target types to be available in the Add Target dialog.
Software Prerequisites
Migrate Agent Utility for Linux requires the source machine to have GNU C Library (glibc) 2.11.3 or higher installed.
Reboot
A reboot of the source Windows workload is required when you install, uninstall, or upgrade block-based transfer drivers. A reboot is not required for source Linux workloads.
Although a reboot is always required for Windows workloads, using 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.
Credentials
For Windows workloads, Migrate Agent Utility requires Administrator privileges to execute commands.
For Linux workloads, Migrate Agent Utility requires root-level access to execute the commands. A non-root user account must be authorized to use the sudo command. That is, the user name must be listed as an authorized user in the /etc/sudoers configuration file. For information on using an account other than root, see KB Article 7920711.
NOTE:For source Linux workloads in Amazon Web Services, AMI templates automatically create a default non-root system user account that is enabled for sudo. The user name for this account varies by AMI provider. For Amazon Linux images, the non-root user name is ec2-user for most Linux distributions. It is centos for CentOS AMIs. For more information, refer to your AMI provider documentation.
In AWS, a non-root user must run the sudo -i command to access the root shell and then run the Migrate Agent commands. Typing sudo in each Migrate Agent Utility command might result in a failure on some source workloads.