Smp Cannot Perform V2V Migrations On Virtual Machine Guests With Certain Disk Types; Starting A New Migration After A Current Migration Is Stopped; Unrecoverable Sector-Read Errors On The Source Server Hard Drive Are Not Supported And Fail A Windows P2P Or P2V Migration; Source Agent Fails To Launch When Source Server Reboots In Smp Agent Mode - Compaq 226824-001 - ProLiant - ML750 User Manual

To resolve this issue:
If an existing disk already containing some Windows partitions is used as the destination for migration,
format the disk before using it as a destination disk.

SMP cannot perform V2V migrations on virtual machine guests with certain disk types

SMP does not move, copy, or migrate virtual machine guests with the following disk types.
Table 8-1 Unsupported disk types*
Virtualization technology
Microsoft Virtual Server 2005
VMware ESX
VMware ESX
VMware Server
* For V2P and V2V migrations, dynamic disk support is limited to simple and mirrored volumes.
V2P and V2V migration have limited support for dynamic disks. Only mirrored and simple dynamic partitions
are supported. These are migrated as basic partitions on the destination.

Starting a new migration after a current migration is stopped

If a migration is stopped by means other than a cancellation or failure, the application station, source server,
and destination server might not recognize that the migration has stopped. To start a new migration:
1. Restart the SMP Agent on the source and destination servers.
2. On the application station, close the Migration Wizard.
3. Restart the HP SMP application service and the HP SMP Web Service.
4. Reopen the Migration Wizard.
Unrecoverable sector-read errors on the source server hard drive are not supported and fail a
Windows P2P or P2V migration
The following error message might appear if a volume with unrecoverable sector-read errors is migrated:
Server Migration failed. ReadFile failed.
Hard drives automatically take corrective action when they have difficulty reading a sector. These sectors
are marked as "bad sectors" and relocated to one of the sparse sectors in a reserved area of the hard disk.
In these cases, no read error is produced, and the drive continues to function properly. The data is lost and
a read error is propagated to the operating system only if the surface error rate is too high and additional
sparse sectors are not available, or when the sector is completely unreadable from the beginning.
If file system tools are used to detect these failing sectors (for example, chkdsk /p /r), the clusters are marked
as "bad." However the data cannot usually be recovered. In such cases, the system is not consistent, and
proper migration is not possible.
SMP does not support the migration of volumes with unrecoverable bad sectors.

Source agent fails to launch when source server reboots in SMP Agent Mode

If the SMP Agent fails to launch when the source server reboots in SMP Agent Mode:
Disk type
Linked disk
Differencing disk
Append disk
Undoable disk
Nonpersistent disk
Physical (RAW) disk
Troubleshooting 131