Upgrading or replacing your existing Microsoft® Windows® - based server hardware? Consolidating your existing Microsoft® Windows® servers to a Virtual Environment? No need to deploy from scratch - simply migrate using HP Insight Server Migration software for ProLiant.
This convenient software provides an automated, accurate, and affordable way to migrate your existing servers and virtual machines.
The HP Insight Server Migration software for ProLiant (SMP) simplifies the server consolidation process. HP Insight Server Migration software for ProLiant migrations involve migrating an operating system, applications, and data from one server to another, instead of manually redeploying these elements on a new server. SMP provides the following migration capabilities:
1. Physical-to-ProLiant (P2P) migration — Migrates a physical machine to a ProLiant server
2. Physical-to-virtual (P2V) migration — Migrates a physical machine to a VMware, Microsoft, or Citrix virtual machine guest
3. Virtual-to-ProLiant (V2P) migration — Migrates a VMware, Microsoft, or Citrix virtual machine guest to a ProLiant server
4. Virtual-to-Virtual (V2V) migration — Migrates a virtual machine guest between different virtualization layers, such as migrating a Microsoft Virtual Server VM guest to a VMware ESX VM guest
Server Spec
HP DL380G6 E5540 QC (2.53Ghz, 8MB)
Intel Xeon Processor E5540 QC (2.53 GHz, 8MB L3 defCache, 80W, DDR3-1066, HT, Turbo 1/1/2/2)
HP Smart Array P410I/256 MB Controller (RAID 0/1/1+0/5/5+0)
HP 2GB X 6 PC3-10600 (total 12GB)
HP 146GB 3G SAS 15K 2.5" DP ENT HDD (2X146GB-RAID 1 = 146GB)
HP 300GB 3G SAS 10K 2.5" DP ENT HDD (6X300GB-RAID 10 = 900GB)
Windows 2008 R2 Standard X64 -HyperV Server
146GB - 2 logical drives (C:\70GB-OS, D:\76GB-LOG)
900GB - 1 logical drive (E:\ 900GB - Database)
Virtual Machine configuration
Disk1: 80GB
Disk2: 500GB
Virtual Machine vhd and xml directory: E:\HyperVDB\VHD\DBServer & HyperVDB\XML\DBServer\virtual machine
2GB Memory
To migrate one unit of SQL2000 Server hosted on Windows 2000 Server to Hyper-V based VM
Migration components
SMP migration requires these components:
- The application station is the computer from which you set up and perform the migration.
- The source server is the server or virtual machine to be migrated.
- The destination server is the server or virtual machine to which the source server is migrated.
The following table describes the installation prerequisites. The application station and source server both have specific prerequisites that must be met to ensure proper installation.
SMP application installation prerequisites | |
Component | Prerequisite |
Application station | · Supported Microsoft ® Windows ® operating system must be installed. · Microsoft iSCSI Initiator 2.06, 2.07, or 2.08 must be installed. The iSCSI Initiator can be downloaded and installed from http://www.microsoft.com · Microsoft Internet Explorer 6.0 or 7.0, or Mozilla Firefox 2.0.0.16 must be installed. · The SMP application must be installed on an NTFS partition · Available memory of at least 256 MB · Screen resolution of at least 1024x768 · Available disk space of at least 900 MB · Availability of ports 51124 and 51125 (or ports specified during SMP installation)* |
Source server | The physical or virtual source server requires the following components to be installed:
|
Step 1: Install the SMP application on the application station
- Download the SMP zipped file, and decompress
- it to an ISO image.
- Burn the SMP Boot CD from the ISO image.
- Insert the SMP Boot CD in the CD-ROM of the selected application station. The CD autorun utility displays the installation screen.
- Click Install Application. The welcome page appears.
6. Click Next.
7. Read the license agreement. If you agree to the terms of the license agreement, select the I accept the agreement option, and click Next.
8. Select the destination location for the SMP application. The default location is C:\Program Files\HP\HP Insight Server Migration software for ProLiant.
9. Enter proper service account credentials.
10. Click Next>Finish.
Step 2: Prepare physical source server or source virtual machine host
Manually running SMP Source Agent on the source server
Deploying Windows SMP Source Agent locally on the source server
1. Access SMP Source Agent in the following folder on the application station:
\Agents\SMP\hpsmpagent.exe
2. Copy the file in this folder to the source server, and then run the file. If a security warning window
appears, click Run on the window.
3. To launch SMP Source Agent, click Install.
When SMP Source Agent is ready for migration, the following screen appears on the source machine.
NOTE: The following screen appears only if X Windows was used.
Deploying Windows SMP Source Agent locally on the source server
1. Access SMP Source Agent in the following folder on the application station:
2. Copy the file in this folder to the source server, and then run the file. If a security warning window
appears, click Run on the window.
3. To launch SMP Source Agent, click Install.
When SMP Source Agent is ready for migration, the following screen appears on the source machine.
NOTE: The following screen appears only if X Windows was used.
4. Record the IP addresses listed for the source server entry when using SMP.
After the application station is connected to SMP Agent on these servers, the agent is locked to the
application station.
To unlock the connection between the application station and the source server, access the agent console
on the source server, and then click Abort and Exit.
To stop the source agent, on the source page, click Abort and Exit.
NOTE: After completing a migration, SMP Source Agent no longer runs on the source server.
Step 3: Prepare physical destination server or destination virtual machine host
- If migrating to a destination virtual machine (performing V2V or P2V), launch the appropriate SMP VM Host Agent to the destination virtual machine host or boot the destination virtual machine to the SMP VM Boot CD. Refer to the HP Insight Server Migration software for ProLiant User Guide for steps on how to prepare the destination virtual machine host and virtual machine.
- If migrating to a physical destination server (performing P2P or V2P), boot the destination server to the SMP Boot CD and launch the SMP Agent.
Manually creating and booting a virtual machine destination server for P2V and V2V (agent-less)
Hyper-V migration
• Ensure that the virtual machine does not have more than three disks attached.
• Ensure that the virtual machine has at least 600 MB of memory.
• Ensure that the network adapter is a legacy network adapter.
• Ensure that the network adapter is connected to a virtual network switch which is connected to an
external network.
• Ensure that the virtual disks that you create are attached to an IDE controller.
• Ensure that the boot virtual disk is connected to the 0th channel of the first IDE controller.
• Ensure that the SMP Virtual Boot CD is attached to one of the channels of an IDE controller.
1. Access the virtual machine host management console provided by VMware, HP integrated Citrix XenServer, or Hyper-V.
2. Create a new virtual machine with sufficient disk space for migration.
3. Boot the virtual machine to the SMP VM Boot CD. The SMP VM Boot CD can found in the following location on the application station:
4. After the destination virtual machine is booted to the SMP VM Boot CD, to launch the SMP Agent on the destination virtual machine
You can only configure one IP address for the destination server. Ensure that the selected network card can connect to the same network as the application station. Configure the network to enable the SMP Agent by selecting the adapter from the list. Select one of the following:
• Dynamically obtain an IP address from a DHCP server—This is the default option. The list and text
boxes are disabled when DHCP (Dynamic Host Configuration Protocol) is selected.
• Configure a Static IP Address—The list displays all available network cards for this system. The Select Adapter, IP Address (must be unique), and Subnet Mask entries are required. Specifying the gateway information is optional. The Next button is disabled until the required entries are entered, or if an invalid value for the IP Address, Subnet Mask, or Gateway is entered.
You can set the duplex settings for the selected card by selecting one of the following from the Duplex
Setting list:
• Ignore—This option is selected by default and continues with the current duplex setting for the selected network card from the Selected adapter list.
• Auto-negotiate on—Select this option to enable auto-negotiation for the selected network card.
• 100 MB Full Duplex—Select this option to set full duplex to 100 MB. Full duplex is the capability to send data in both directions at the same time.
• 1000 MB Full Duplex—Select this option to set full duplex to 1000 MB.
When a message appears advising you that the destination server is ready for migration:
a. Record the IP address listed on the screen for the destination server entry when using the SMP application.
b. Perform the migration from the application station. A message appears on the destination server that reports the migration progress when the data copy process begins.
Step 4: Run the migration wizard from the application station
To access the SMP migration wizard from the application station, use either of the following methods:
To start the P2V Migration Wizard:
1. If you are performing a migration from a stand-alone SMP application station:
• From the desktop, access the SMP Migration Wizard by clicking the SMP application icon.
• From the Overview page, click the Migration Wizard tab.
• Choose the Windows migration type.
• Click Physical to Virtual Migration (P2V), and then click Next.
2. Enter the source Server Name or four-part IP address.
3. Select whether SMP must deploy SMP Source Agent on the source server. If you select this option, you must provide the source server administrative credentials.
4. Click Next.
5. To install SMP Source Agent on the source server, select the Deploy SMP Source Agent checkbox, enter the User name and Password, and then click Next.
6. If SMP Source Agent is already running on the specified source server, make sure the Deploy SMP Source Agent checkbox is cleared, and then click Next. The wizard verifies if SMP Source Agent is already running on the specified source server.
7. Select the volumes to be migrated. Volumes marked as active are selected by default. You cannot migrate
or select unsupported file systems.
The boot partition must be migrated. The boot partition is contained in an active volume. If only one active volume exists, by default it contains the boot partition and cannot be cleared. If multiple active volumes exist, ensure that the volume containing the active boot partition (which contains the boot.ini, NTLDR, and NTDETECT.com files) is migrated to the target boot disk. Additional bootable partitions might be contained in other active volumes, but the partitions do not need to be migrated.
The operating system must be stored on the boot disk and loaded using NT Boot Loader (NTLDR). Volumes on dynamic disks are migrated to partitions on basic disks. Volumes that span multiple dynamic disks (including spanned, striped, mirrored, and RAID 5 volumes) are migrated to a single contiguous partition. Volumes stored on a common source disk must be stored on a common destination disk. You can only resize NTFS partitions.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. The Size, Minimum Destination Size, and Maximum Destination Size values in the lower table are updated dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that must be created on the destination server. The entry in the Minimum Destination Size column is estimated, based on reducing eligible volumes to their minimum size during migration. Additional space might be required to accommodate disk geometry differences.
8. Select the appropriate destination virtualization layer in the Select Virtualization Layer box.
• Agent-based hypervisors—Enter the destination virtual machine host name or IP address, and then click Next.
• Agent-less hypervisors—Enter the destination virtual machine host name or IP address, and then enter the host administrative credentials.
• If the destination virtual machine was booted with the SMP Virtual Boot CD, select Manual Boot - Manually create VM through VM Host's Infrastructure Client. Enter the four-part IP address of the destination virtual machine, User name, and Password, and
then click Next.
The Virtual Boot CD can be found at
• If the destination virtual machine is not created, select Auto Boot - Automatically have VM created through SMP migration. Enter the four-part VM Pre-boot IP address, Subnet Mask, and Gateway (optional) to be assigned to the virtual machine, and then click Next.
9. Specify the destination disks, and then select the NTFS partitions to be resized. By default, this page includes a table that displays all disks present on the destination virtual machine, with source disk, disk format, size, and destination disk information.
The following screen appears when the manually booted destination is selected for agent-less virtual machine hosts.
The following screen appears when the automatically booted destination is selected for agent-less virtual
machine hosts.
If you are migrating to an agent-based virtual machine host or migrating to an agent-less virtual machine
host that is automatically booted with the SMP Virtual Boot CD:
a. Enter information in the Guest Display Name, Guest Memory, and Guest Storage Location
boxes.
b. Some of the columns and rows from the Assign Disks and Resize NTFS Volumes table include:
• Minimum Destination Size—This column displays the minimum size to which a partition or
disk can be resized for the destination disk.
• Destination Size—This column displays the desired partition resize or disk resize on the
destination disk.
• Migration Overhead—This row displays the additional space that must be reserved on the
destination disk to accommodate disk geometry differences.
• Unallocated—This row displays the available space remaining on the destination disk after
the migration is complete. To proceed to the Next wizard page, the value of Unallocated must
either be 0 (zero) or a positive number.
10. Test the network connections and latency between the source-to-destination server and the
application-station-to-destination server. The results of a 2-second test initially appear.
11. To perform additional tests, select a test time in the Test network connections section, and then click
Test. The following test times are available:
• 2 seconds
• 5 seconds
• 10 seconds
• 30 seconds
• 60 seconds
If the source-to-destination or application-station-to-destination connection cannot be established, the Next button is disabled. Ensure that ports 51125 and 51126 are open between source and destination servers.
If the source-to-destination or application-station-to-destination connection is established but the network test reports a transfer speed below 250 kbps, the Next button is disabled.
If the source-to-destination or application-station-to-destination connection is established and the network test reports a transfer speed of at least 250 kbps, the Next button is enabled.
12. Click Next.
13. Select the post-migration tasks, and then click Next.
• Select whether the SMP application must perform disk-error checks on the source server before migration. By default, the Use CHKDSK to detect and fix errors on all source disks prior to migration checkbox is selected.
• A reboot or shutdown option is not available for the destination virtual machine for X2V migrations when the option to manually create and the boot the destination virtual machine is selected in step 3 of the Migration Wizard. After the migration is completed, manually reboot the destination virtual machine.
14. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again.
15. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the
Job Status field indicates the migration has been canceled, reboot the source and destination servers
Posts
0 comments:
Post a Comment