HP ProLiant ML350p HP Insight Server Migration Software for ProLiant User Guid - Page 81

Source physical machine prerequisites, SMP application station prerequisites, Computer, Management

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

Page 81 highlights

Source physical machine prerequisites CAUTION: If the SMP application station shuts down or fails during any migration, then the migration being performed fails. Availability of application station during complete migration cycle is required for successful migration. • Because the SMP application does not migrate virtual machine guests with the following disk types, verify that these disk types do not exist on the source virtual machine. The following table details the prerequisites for the source virtual machine. Table 5-2 Unsupported disk types Virtualization technology Disk type Microsoft Virtual Server 2005 VMware ESX VMware ESX VMware Server Linked disk Differencing disk Append disk Undoable disk Nonpersistent disk Physical (RAW) disk • A valid network connection must exist between the source and destination server. • The source server must contain an active boot partition to be migrated. • To prevent interrupting the migration process, complete any pending reboots and software installations on the source machine before initiating a migration. • Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the migration process. Re-enable the antivirus software after the migration. • Verify that the disks are not corrupted by running CHKDSK and disk defragmenter on the source physical machine before initiating a V2P migration. Verify that all hard drives on the source physical machine are correctly initialized (disk signature written). If Windows 2000 or Windows Server 2003 is installed, then verify initialization by selecting Computer Management→ Disk Management. Verify that the latest hard drive configuration is saved. • Verify that all partitions on the source physical machine have a valid file system and are in a healthy state. • Disable all applications and background services on the source machine. After the migrated machine has synchronized with the new hardware and is assigned a unique network identity, appropriate applications can be manually re-enabled and configured for the new environment. • Temporarily disable HP Management Agents on the source physical machine. • Verify that a Windows NT boot loader (NTLDR) is installed. • During migration, the SMP Agent initiates an operating system reboot on the source physical machine. Verify that the operating system is on the first boot order. If not, then manually change the boot order by editing the [system drive]\boot.ini file or by using the bootcfg.exe tool. The SMP application supports migration of source physical machines that have operating systems installed on the primary drive (Hard Disk0) and the primary drive loaded first in the boot order. • Record the drive letter or mount point to disk-partition mapping for dynamic disk partitions before performing the migration. Any simple (non-extended) dynamic disk partitions are converted to basic disk partitions. The mapped drive letters might have to be manually reassigned after migration. SMP application station prerequisites • Verify that Microsoft iSCSI Initiator 2.06, 2.07, or 2.08, which is required for primary mass storage driver injection, is installed and running on the SMP application station. If iSCSI Initiator is not installed, Virtual-to-virtual (V2V) migrations 81

  • 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
Source physical machine prerequisites
CAUTION:
If the SMP application station shuts down or fails during any migration, then the migration
being performed fails. Availability of application station during complete migration cycle is required for
successful migration.
•
Because the SMP application does not migrate virtual machine guests with the following disk types,
verify that these disk types do not exist on the source virtual machine.
The following table details the prerequisites for the source virtual machine.
Table 5-2 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
•
A valid network connection must exist between the source and destination server.
•
The source server must contain an active boot partition to be migrated.
•
To prevent interrupting the migration process, complete any pending reboots and software installations
on the source machine before initiating a migration.
•
Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the
migration process. Re-enable the antivirus software after the migration.
•
Verify that the disks are not corrupted by running CHKDSK and disk defragmenter on the source physical
machine before initiating a V2P migration.
Verify that all hard drives on the source physical machine are correctly initialized (disk signature written).
If Windows 2000 or Windows Server 2003 is installed, then verify initialization by selecting
Computer
Management
→
Disk Management.
Verify that the latest hard drive configuration is saved.
•
Verify that all partitions on the source physical machine have a valid file system and are in a healthy
state.
•
Disable all applications and background services on the source machine. After the migrated machine
has synchronized with the new hardware and is assigned a unique network identity, appropriate
applications can be manually re-enabled and configured for the new environment.
•
Temporarily disable HP Management Agents on the source physical machine.
•
Verify that a Windows NT boot loader (NTLDR) is installed.
•
During migration, the SMP Agent initiates an operating system reboot on the source physical machine.
Verify that the operating system is on the first boot order. If not, then manually change the boot order
by editing the
[system drive]\boot.ini
file or by using the bootcfg.exe tool. The SMP application
supports migration of source physical machines that have operating systems installed on the primary
drive (Hard Disk0) and the primary drive loaded first in the boot order.
•
Record the drive letter or mount point to disk-partition mapping for dynamic disk partitions before
performing the migration. Any simple (non-extended) dynamic disk partitions are converted to basic
disk partitions. The mapped drive letters might have to be manually reassigned after migration.
SMP application station prerequisites
•
Verify that Microsoft iSCSI Initiator 2.06, 2.07, or 2.08, which is required for primary mass storage
driver injection, is installed and running on the SMP application station. If iSCSI Initiator is not installed,
Virtual-to-virtual (V2V) migrations
81