HP ProLiant DL140 HP Insight Server Migration Software for ProLiant User Guide - Page 49

Physical-to-ProLiant (P2P) migrations for Windows, Preparing for a P2P migration - network drivers

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

Page 49 highlights

Physical-to-ProLiant (P2P) migrations for Windows Preparing for a P2P migration The following sections list prerequisites for a Windows P2P migration. If you use a firewall, see the Configuring SMP with a firewall section in this guide. Source physical machine prerequisites • A valid network connection must exist between the source and destination server. • The source server must contain an active boot partition to be migrated. • Complete any pending reboots and software installations on the source machine before initiating a migration to prevent interrupting the migration process. • Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the migration process. Re-enable the antivirus software after the migration. • To verify that the disks are not corrupted, run FSCK on the source physical machine before initiating a migration operation. • Verify that all hard drives on the source physical machine are correctly initialized (disk signature written). • 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. • 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 /boot/grub/menu.lst file. 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. 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, then download and install it from http://www.microsoft.com. Other versions of the initiator, including later versions, cannot be used with this version of SMP. • Valid migrated previous P2P licenses or SMP X2P or X2X license keys are required on the application station. Verify that adequate licenses exist by selecting the License tab in the SMP application station. • Verify that no virtualization software is installed on the SMP application station. • To prevent interrupting the migration process, temporarily disable any antivirus software autoscans on the SMP application station. Re-enable the antivirus software after the migration. • Disable all the Windows network drive mappings to the source physical machine in the SMP application station. • Verify that the SMP application station Windows operating systems version is greater than or equal to the source physical machine Windows operating system version. • Verify that the SMP application station Windows operating system is configured for NTFS. Destination physical machine prerequisites • The primary storage controller must be configured with drives attached. • The destination server must be booted to SMP Boot CD and running SMP Agent. Physical-to-ProLiant (P2P) migrations for Windows 49

  • 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
Physical-to-ProLiant (P2P) migrations for Windows
Preparing for a P2P migration
The following sections list prerequisites for a Windows P2P migration.
If you use a firewall, see the
Configuring SMP with a firewall
section in this guide.
Source physical machine prerequisites
•
A valid network connection must exist between the source and destination server.
•
The source server must contain an active boot partition to be migrated.
•
Complete any pending reboots and software installations on the source machine before initiating a
migration to prevent interrupting the migration process.
•
Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the
migration process. Re-enable the antivirus software after the migration.
•
To verify that the disks are not corrupted, run FSCK on the source physical machine before initiating a
migration operation.
•
Verify that all hard drives on the source physical machine are correctly initialized (disk signature written).
•
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.
•
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
/boot/grub/menu.lst
file. 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.
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,
then download and install it from
ht
tp://w
w
w
.mic
r
o
s
o
f
t
.com
. Other versions of the initiator, including
later versions, cannot be used with this version of SMP.
•
Valid migrated previous P2P licenses or SMP X2P or X2X license keys are required on the application
station. Verify that adequate licenses exist by selecting the
License
tab in the SMP application station.
•
Verify that no virtualization software is installed on the SMP application station.
•
To prevent interrupting the migration process, temporarily disable any antivirus software autoscans on
the SMP application station. Re-enable the antivirus software after the migration.
•
Disable all the Windows network drive mappings to the source physical machine in the SMP application
station.
•
Verify that the SMP application station Windows operating systems version is greater than or equal to
the source physical machine Windows operating system version.
•
Verify that the SMP application station Windows operating system is configured for NTFS.
Destination physical machine prerequisites
•
The primary storage controller must be configured with drives attached.
•
The destination server must be booted to SMP Boot CD and running SMP Agent.
Physical-to-ProLiant (P2P) migrations for Windows
49