HP Insight Control - Manual (Page 44)

4. If the source and destination servers must be on the network at the same time:
a.
Change the host name of either server or consider reconfiguring the applications.
b. If the IP addresses are static, reassign them.
5. If the license is not a volume license, reactivate it.
6. The mouse and keyboard might not be immediately active after the migration. Wait until the
guest operating system automatically installs all required drivers.
X2V postmigration tasks (Linux)
After you complete an X2V migration, perform the following steps on the destination server:
1.
If you manually booted the virtual machine by using the Insight Control server migration Virtual
Machine Boot CD ISO, you must disconnect the Insight Control server migration Virtual Machine
Boot CD ISO and then manually reboot or shut down the virtual machine.
2. Perform a network configuration for the migrated virtual machine guest. To do so, access the
remote console for the destination virtual machine host to configure the network connections
for the migrated virtual machine guest.
3. (Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might
be required to install additional Integrated Components.
After the virtual machine reboots, you must perform the following steps on the destination virtual
machine guest for hypervisors:
1.
Modify the system host name.
2. Install the proper guest tools.
3. If necessary, verify the network connections.
4. The mouse and keyboard might not be immediately active on the migrated virtual machine
guest. Wait until all the guest operating system automatically installs required drivers, and
then reboot the migrated virtual machine guest when you are prompted.
Viewing migration logs
From the View Status/Logs tab, you can:
•
View currently running migrations.
•
View a log of the migration results.
•
Create support logs.
For more information, click the help icon on the server migration View Status/Logs page.
NOTE: When a job is complete, its link no longer appears in the View Status/Logs page, but
the job-specific log files are still available in the HP Insight Control server migration installationpath\
logs
directory.
Validating the migration
Validating Linux migrations
To verify that the Linux migration was successful, you can do the following:
1.
Compare the md5 checksum of the files on the migrated filesystem with the checksum on the
source. The md5 checksum should match for all files except for the initrd and log files.
2. Make sure that the operating system on the destination server boots normally without critical
errors.
Validating Windows migrations
To verify that the Windows migrations was successful, you can do the following:
44 Postmigration tasks