Filter
Top Products
Suggested action
The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bit RHEL, the
Linux source migration agent window does not appear, although the agent is running. To enable
the display of the agent, you must install the X.Org X11 libXtst runtime library,
libXtst-1.0.99.2-3.el6.i686.rpm.
Remote deployment of Linux Source Agent using nonroot credentials fails
Remote deployment of Linux Source Agent using nonroot credentials fails with the following error:
Failed to deploy server migration Source Agent. Error while installing
the server migration Source Agent on the given Server : exec tar -zxf
hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124,
51125 and 51126 required by the agent might be in use. : exec tar -zxf
hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124,
51125 and 51126 required by the agent might be in use.
Suggested action
Deploy the Linux Source Agent by using root privileges.
Manual installation of Linux Source Agent using sudo user privileges fails
Manual installation of Linux Source Agent using sudo user privileges fails.
Suggested action
Launch the server migration Linux Source Agent by using proper root user privileges.
Incorrect LUN size is detected in step 2 of the migration wizard
If the size of the source LUN detected during step 2 of the migration wizard is incorrect, you might
be attempting to initialize the LUN by using GPTs.
Cause
LUNs initialized with GPTs are not supported, even if they contain partitions with filesystems that
server migration supports. Those partitions appear as RAW partitions in the migration wizard, and
data might be incomplete after the migration.
Suggested action
Deselect LUNs initialized with GPTs in step 2 of the migration wizard, and manually copy data
on GPT disks after the migration.
Migrating a source server fails with the Microsoft Hyper-V role enabled
If you are trying to migrate a source server with the Microsoft Hyper-V role enabled, you must
make sure that certain preconditions are met.
Suggested action
Perform any one of the following on the source server:
• Turn off the hypervisor by using the following command:
bcdedit /set hypervisorlaunchtype off
After the migration, you can re-enable the hypervisor by using the following command:
bcdedit /set hypervisorlaunchtype auto
• Remove the Microsoft Hyper-V role from the source server.
Source preparation 53