HP Insight Control - Manual (Page 150)

partitions appear as RAW partitions in the Migration Wizard, and data might be incomplete after the
migration. You must 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 with the Microsoft Hyper-V role enabled
If you are trying to migrate a source server with the Microsoft Hyper-V role enabled, perform one of the
following prerequisites on the source server:
•
Turn off the hypervisor using the following command:
bcdedit /set hypervisorlaunchtype off
After the migration, you can re-enable the hypervisor using the following command:
bcdedit /set hypervisorlaunchtype auto
•
Remove the Microsoft Hyper-V role from the source server.
Remote deployment of Linux source agent using non-root credentials fails
Remote deployment of Linux source agent using non-root credentials fails with the error:Failed to Deploy
SMP Agent. Error while installing the SMP Source agent on the given Server
address>: 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."
To resolve this issue, the Linux source agent must be deployed 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. To resolve this issue, launch the
SMP Linux source agent with proper root user privileges.
Destination preparation
Destination server identification fails
If the destination server identification fails in step 3 of the Migration Wizard:
1. Verify that the network adapter on the destination server is configured with a valid IP address, subnet,
and gateway. Also verify the network configuration information reported on the destination server.
2. Verify that the destination server is booted from the Insight Control server migration Boot CD and ready
for migration. For more information, see the
Insight Control server migration User Guide.
3. Verify that the destination server can be reached from the application station and source server.
Communication on network ports 51125 and 51126 must be enabled by any firewall between this
computer and the destination server.
4. Verify that another Insight Control application is not already communicating with the destination server.
Application station fails to connect to the destination server
After an automatic boot through remote management during a P2P or V2P migration, the application station
may fail to connect to the destination server and the message Could not connect to destination
server agent.
appears in the migration wizard. This error can occur if the destination server has multiple
NICs connected to different networks and the IP address is configured to a NIC that is not on the same
network as the application station. To resolve this issue, verify that the destination server and the application
station are on the same network.
150 Troubleshooting