21
HP Server Migration Pack – Universal Edition

HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Embed Size (px)

Citation preview

Page 1: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

HP Server Migration Pack – Universal Edition

Page 2: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Addressing all elements of the HP ProLiant and BladeSystem lifecycle

Total Control

Maximum Flexibility

Tangible Savings

ProLiant Essentials

Intelligent Infrastructure

HP SIMFoundation

Task-specificsoftware options

Page 3: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Server Migration as a part of the HP Insight Control strategy

Page 4: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

HP Server Migration Pack – Universal Edition

• Meets all your HP ProLiant and BladeSystem migration needs−Physical to ProLiant (P2P)−Virtual to ProLiant (V2P)−Physical* to Virtual (P2V)−Virtual to Virtual** (V2V)

* - Source server can be any x86 server, regardless of vendor.

** - Ability to migrate between virtualization vendors

Page 5: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Screenshot 1

Page 6: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

The three components of any migration – the APP STATION

SMP Universal Application Station

This is the SMP Universal application station – it is the central migration

execution point for all migrations. It does not need to be a server class machine; it

can be a workstation, laptop, etc).

The SMP-UE application station can optionally be installed on the HP Systems

Insight Manager central management server. If so, the HP SIM CMS would need

to be a server class machine. (The application station is not required to be installed on the HP SIM CMS in order to

integrate with HP SIM.)

Page 7: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

The three components of any migration – the SOURCE server

Source server (physical or virtual)

This is the source server – it is where we will be migrating FROM.

This can be any physical x86 server, regardless of hardware vendor, or a VMware or Microsoft virtual server.

Page 8: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

The three components of any migration – the DESTINATION server

Destination server (HP ProLiant,

BladeSystem, or virtual host)

This is the destination server – it is where we will be migrating TO. This can be any supported HP ProLiant

server or BladeSystem server blade, or a VMware or Microsoft virtual

server host.

Page 9: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

How it works…

1. Use the SMP Universal CD to install the SMP Universal browser-based application on the designated application station.

SMP Universal Application Station

Page 10: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

How it works…

Source server(physical or virtual)

2. Use the same SMP Universal CD to run the SMP Universal “agent” on the source server. This agent is run only when needed to migrate, and can be automatically removed after migration.

Page 11: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Destination server (HP ProLiant or BladeSystem)

3. Boot the destination server off of the same SMP Universal CD. No other pre-work is required on the destination server.

a. If an IP address is needed, the SMP Universal CD contains a mechanism to retrieve an IP from a DHCP server of your choice, or to apply a static IP address to the server.

b. In order to partition the volume on the destination server, an array configuration utility is provided on the SMP Universal CD.

How it works…(2ProLiant)

Page 12: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Destination server (virtual host)

3. Use the same SMP Universal CD to run the SMP Universal “agent” on the source server. This agent is run only when needed to migrate, and can be automatically removed after migration.

or How it works…(2Virtual)

Page 13: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Altogether

Source Server Destination Server

Application Station

Page 14: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Automated migration is now an option!

Drivers

OS

Application

Data

New Drivers

Same OS

Same Application

Same Data

Automated migration process takes care of driver compatibilityDrop or resize partitions during migration

Just migrate your existing serverNo need for from-the-ground-up deployment

or

Automated, Accurate, Affordable

otherother brand / Virtual Machine

Page 15: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Before… and after!

HP is HP is designsdesigns, , engineersengineers, and , and teststests HP ProLiant and BladeSystem technology… HP ProLiant and BladeSystem technology…

why trust anyone else for HP ProLiant and BladeSystem why trust anyone else for HP ProLiant and BladeSystem migrations?migrations?

Before After

Getting a new HP ProLiant server or BladeSystem into production takes days, weeks, or even months.

Your new HP ProLiant server or BladeSystem is in production in a matter of hours – on average, 2 – 3 minutes per GB of content.

Three or more specialists per server required to prepare the new server for production (security, application, QA, etc).

Less than one person per server required to run HP SMP Universal.

Highly trained specialists spending time on non critical task of server builds.

Junior level operators stepping through an 8 step wizard, while specialists’ time is put to better use.

Additional tool required to migrate to virtual machines, maybe more than one. No ability to move virtual back to physical.

One tool does it all – no setup time or learning curve for multiple migration tools. Move virtual servers to physical when you need to.

Page 16: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

2ProLiant Support MatrixSource

Server Any x-86 server

OS Windows Server 2000 (32-bit), Windows Server 2003 (32-bit)

Destination

Server ProLiant BL460c

ProLiant BL480c

ProLiant BL465c G5

ProLiant BL680c G5

ProLiant BL685c

ProLiant BL20p G4

ProLiant BL20p G3

ProLiant BL25p G2

ProLiant BL25p G1

ProLiant BL45p G2

ProLiant BL45p G1

ProLiant BL35p

ProLiant DL320 G5

ProLiant DL320 G5p

ProLiant DL360 G5

ProLiant DL360 G4

ProLiant DL360 G4p

ProLiant DL365 G5

ProLiant DL365 G1

ProLiant DL380 G5

ProLiant DL380 G4

ProLiant DL385 G5

ProLiant DL385 G2

ProLiant DL385 G1

ProLiant DL580 G5

ProLiant DL580 G4

ProLiant DL580 G3

ProLiant DL585 G2

ProLiant ML310 G5

ProLiant ML310 G4

ProLiant ML350 G5

ProLiant ML370 G5

ProLiant ML370 G4

ProLiant ML570 G4

ProLiant ML570 G3

Storage Controllers

Smart Array E200/E200i, E500, Smart Array P400/P400i, Smart Array P600, Smart Array 6402, 6404, Smart Array 641, 642, Smart Array 6i, SmartArray P800, P400i, HP 4 Internal Port SAS HBA with RAID, Intel® 6300 ESB/82801FR SATA Controller (Non-RAID only), SC40ge HBA

Storage Enclosures

MSA 30, MSA 50, MSA 60 MSA 70, MSA 600, MSA 700

Network Controllers

NC110T, NC320, NC324i, NC326i, NC364T, NC370i, NC371i, NC373i, NC373T, NC374m, NC7761, NC7781, NC7782, NC373F

Page 17: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

2Virtual Support Matrix

Source Source server for P2V

any x86 server

Source OS for P2V

Windows NT 4.0 SP 6a Windows Server 2000 SP4Windows Server 2000 Advanced Server SP4Windows Server 2003 Standard EditionWindows Server 2003 Standard Edition SP1 Windows Server 2003 Enterprise EditionWindows Server 2003 Enterprise Edition SP1Windows Server 2003 R2 Standard EditionWindows Server 2003 R2 Enterprise EditionWindows XP ProfessionalWindows 2000 Professional

Source VM for V2V

Microsoft Virtual Server 2005Microsoft Virtual Server 2005 R2VMware ESX Server 2.5.3, 2.5.4, 2.5.5, 3.0, 3.0.1, and 3.0.2VMware GSX 3.2, 3.2.1VMware Server 1.0.1, 1.0.2, 1.0.3

Source OS for V2V

Windows NT 4.0 SP 6a Windows Server 2000 SP4Windows Server 2000 Advanced Server SP4Windows Server 2003 Standard EditionWindows Server 2003 Standard Edition SP1 Windows Server 2003 Enterprise EditionWindows Server 2003 Enterprise Edition SP1Windows Server 2003 R2 Standard EditionWindows Server 2003 R2 Enterprise EditionWindows XP ProfessionalWindows 2000 Professional

Destination Destination VM for P2V or V2V

Microsoft Virtual Server 2005Microsoft Virtual Server 2005 R2VMware ESX Server 2.5.3, 2.5.4, 2.5.5, 3.0, 3.0.1, and 3.0.2VMware GSX 3.2, 3.2.1VMware Server 1.0.1, 1.0.2, 1.0.3

Page 18: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Licensing and Pricing

• One year of technical support included!− Rapid access to trained support staff that can help quickly isolate

and troubleshoot software installation and configuration issues. − Customers are eligible for the latest updates of SMP Universal as

long as they have a valid license for any migration.

X2ProLiant Single Migration

Physical / virtual to ProLiant single migration licenses

per migration

X2Virtual Single Migration

Physical / virtual to virtual single migration licenses per migration

1 Year X2X Unlimited Migrations

One year subscription for unlimited migrations of any type

per year

Page 19: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

Next steps• Visit www.hp.com/go/migrate to freely

download SMP Universal for trial− Two full migration licenses available

• Ordering SMP Universal− Licensing options WITH part numbers

Page 20: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

What about HP Server Migration Pack (Classic)?• Former HP product−P2V, V2P, and V2V only−HP SIM requirement−HP VMM requirement

• STATUS: Product is now EOL. −Existing migration licenses owners: Existing

licenses can be converted to SMP Universal Edition licenses using included license utility.

Page 21: HP Universal Server Migration Pack - Magnus Wetterberg.ppt

What about HP Server Migration Pack – Physical to ProLiant Edition (aka P2P, SMP-P2P)?

• Former HP product−Physical to ProLiant migrations only−No ability to interface with HP SIM−Could not reside on HP SIM CMS

• STATUS: Product is now EOL. −Existing migration licenses owners: Existing

licenses can be converted to SMP Universal Edition licenses using included license utility.