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

Schedule preparation, Memory and CPU resources on the application station - bios

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 15 highlights

IMPORTANT: Servers with Windows Original Equipment Manufacturer (OEM) licenses are not supported for migration. For licensing questions, contact HP support. Schedule preparation Schedule preparation is essential when planning a migration strategy. Be sure to include adequate time for copying data. Large volumes take time to migrate. Under optimal conditions, an SMP migration requires two to three minutes to migrate 1 GB of data. Using two minutes as a best-case scenario, migrating 500 GB of data might take more than 17 hours. When a migration starts, the source server reboots to a minimal configuration so that no updates occur on the source server during migration. Only those services required for the migration are enabled. Applications that normally execute on the server are not available during migration. After the migration is complete, the source server is restored to its pre-migration state. Schedule the migration to occur at a time when the source server can be offline. Memory and CPU resources on the application station Insufficient memory and CPU resources on the application station might degrade performance and cause errors during migration. For best results, close all other applications on the application station before the migration. Open the applications after the migration is complete. Critical or hardware-dependent application preparation Some hardware applications are bound to the source server and might need reconfiguration to function as expected following an SMP migration. For added safety, manually disable critical and hardware-dependent applications before migrating a source server. You can then manually re-enable these applications after the migration is complete. Manually disabling applications prevents them from starting on the destination server before they are reconfigured for the destination server. Examples of applications that must be disabled during migration include: • Applications that rely on unique hardware serial numbers, BIOS or chassis IDs, NICs, MAC addresses, or devices that authenticate a piece of software. • Applications that store data on a volume different from that of the operating system. SMP retains drive letters (for example, F:) during migration, but hardware differences between the source and destination servers can force the drive letters to change. • Applications that depend on physical disk identifiers instead of drive letters. Depending on the destination server disk enumeration order and selections made in the SMP Migration Wizard, the contents of a physical disk might have a different sequential identifier on the destination server. In these cases, the application must be reconfigured to use the new physical disk identifiers. Virtual machine guest tools Before starting a migration, you must uninstall the guest tools if you are migrating a source virtual machine. The guest tools are not applicable on the destination server and might cause issues with the normal functioning of the network adapters, keyboard, and mouse. After the migration is completed, you can reinstall the Guest tools on the source virtual machine. Domain controllers SMP supports migration of domain controllers. To migrate a domain controller on a source server: 1. Reboot the server. 2. During reboot, press F8 to boot to Directory Services Restore Mode (DSRM). 3. Launch the SMP Agent in DSRM mode. Planning a migration strategy 15

  • 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
IMPORTANT:
Servers with Windows Original Equipment Manufacturer (OEM) licenses are not supported
for migration. For licensing questions, contact HP support.
Schedule preparation
Schedule preparation is essential when planning a migration strategy.
Be sure to include adequate time for copying data. Large volumes take time to migrate. Under optimal
conditions, an SMP migration requires two to three minutes to migrate 1 GB of data. Using two minutes as
a best-case scenario, migrating 500 GB of data might take more than 17 hours.
When a migration starts, the source server reboots to a minimal configuration so that no updates occur on
the source server during migration. Only those services required for the migration are enabled.
Applications that normally execute on the server are not available during migration. After the migration is
complete, the source server is restored to its pre-migration state.
Schedule the migration to occur at a time when the source server can be offline.
Memory and CPU resources on the application station
Insufficient memory and CPU resources on the application station might degrade performance and cause
errors during migration. For best results, close all other applications on the application station before the
migration. Open the applications after the migration is complete.
Critical or hardware-dependent application preparation
Some hardware applications are bound to the source server and might need reconfiguration to function as
expected following an SMP migration.
For added safety, manually disable critical and hardware-dependent applications before migrating a source
server. You can then manually re-enable these applications after the migration is complete.
Manually disabling applications prevents them from starting on the destination server before they are
reconfigured for the destination server.
Examples of applications that must be disabled during migration include:
•
Applications that rely on unique hardware serial numbers, BIOS or chassis IDs, NICs, MAC addresses,
or devices that authenticate a piece of software.
•
Applications that store data on a volume different from that of the operating system. SMP retains drive
letters (for example, F:) during migration, but hardware differences between the source and destination
servers can force the drive letters to change.
•
Applications that depend on physical disk identifiers instead of drive letters. Depending on the destination
server disk enumeration order and selections made in the SMP Migration Wizard, the contents of a
physical disk might have a different sequential identifier on the destination server. In these cases, the
application must be reconfigured to use the new physical disk identifiers.
Virtual machine guest tools
Before starting a migration, you must uninstall the guest tools if you are migrating a source virtual machine.
The guest tools are not applicable on the destination server and might cause issues with the normal functioning
of the network adapters, keyboard, and mouse. After the migration is completed, you can reinstall the Guest
tools on the source virtual machine.
Domain controllers
SMP supports migration of domain controllers.
To migrate a domain controller on a source server:
1.
Reboot the server.
2.
During reboot, press
F8
to boot to Directory Services Restore Mode (DSRM).
3.
Launch the SMP Agent in DSRM mode.
Planning a migration strategy
15