HP ProLiant DL185 HP Insight Server Migration Software for ProLiant User Guide - Page 131

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

Get HP ProLiant DL185 - G5 Server PDF manuals and user guides View all HP ProLiant DL185 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

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 Disk type Microsoft Virtual Server 2005 Linked disk Differencing disk Append disk VMware ESX Undoable disk Nonpersistent disk VMware ESX VMware Server Physical (RAW) disk * 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: Troubleshooting 131

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
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*
Disk type
Virtualization technology
Linked disk
Microsoft Virtual Server 2005
Differencing disk
Append disk
VMware ESX
Undoable disk
Nonpersistent disk
Physical (RAW) disk
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:
Troubleshooting
131