Ensure that your source workloads and network environment meets the following requirements for using the Migrate Agent Utility:
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.
Migrate Agent Utility for Linux requires the source machine to have GNU C Library (glibc) 2.11.3 or higher installed.
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.
When you use the Migrate Agent on the source workload, the source workload contacts the target workload for data transfers.
Ensure that you configure source workloads to support outbound traffic:
HTTPS port (TCP/443)
Replication port (TCP/3725 is the default)
Reconfigure the replication port direction on the Migrate Server (SourceListensForConnection=False) using the PlateSpinConfiguration page. See Section 5.9, Configuring the Contact Direction for the Replication Port.
NOTE:Migrate Agent is supported only for live migrations. You can use Migrate Agent for automated migrations performed in the Migrate Web Interface and Migrate Client. It is not supported for use with semi-automated (X2P) migrations.