Accelerating Server Hardware Upgrades with PlateSpin Migrate P2P

Accelerating Server Hardware Upgrades with PlateSpin® Migrate P2P

Ari GlaizelProduct ManagerNovell, [email protected]

© Novell, Inc. All rights reserved.2

Workload

Application

Middleware

Operating System

Workload: The (New) IT Paradigm

A workload is an integrated stack of application, middleware, and operating system that accomplishes a computing task

A workload is portable and platform agnostic–it can run in physical, virtual or cloud computing environments

A workload or a collection of workloads makes up a business service, which is what the end user consumes


Does a Workload = a Physical Server?

Physical Server Virtual Host

1 workload per physical server

Multiple workloads per physical server


Hardware migration involves taking server workloads from one physical server to another.

Hardware Migrations

Challenges – Before• End-of-lease server hardware• Older, less powerful servers• Out-of-warranty hardware• Legacy servers risk missing SLAs• High cost in labour and downtime

to manually rebuild workloads

Solution – After• New server hardware under warranty• Meet SLAs with powerful servers• High-density servers use less physical

floor space, rack space and cooling• Automated migrations minimize downtime


Goals of a Hardware Migration Project

Move the maximum number of workloads in the minimum amount of time

Eliminate/reduce testing and configuration of migrated workloads

Ensure migrated workloads contain the most recent data

Reduce migration impact on users, servers and networks


Hardware Migration Potential Hurdles

• Slow/latent/expensive/busy network connections• Small outage windows, weekends, 24 hours or less• Data skew, between production workloads and

migrated workloads• Configuration and testing of migrated workloads adds

hours to each migration.• Moving to disimilar hardware archetectures, AMD to

Intel, Paxville to Dunnington XEON processors etc.• Many different operating systems within the datacenter,

that require many different migration tools


• Number of steps involved in manually moving to new hardware.• Tough to do in parallel for multiple servers• The steps in blue can potentially be automated.

– Acquire new hardware– Hook up hardware in Datacenter– Acquire installation software– Set up volume structure– Install operating system– Apply security policy/patches – Install applications– Transfer existing data– Test and deploy

Typical Steps in Manually Performing a Hardware Migration

For the simplest of servers, you are looking at 6-12 hours per server


Manually Performing Hardware Migrations

• 6-12 hours per server (in the simplest of cases)

• Most tasks can only be serially performed (tough for one person to hardware migrate two servers at the same time)

• Prone to error, significant time spent tracking down problems

The up-front costs of a server can be significantly higher than just buying the hardware!

Is There a Better Way …?


Decouple workloadfrom host

infrastructure

Live peer-to-peer workload migration Migration testing Sync-up prior

to cut-over

PhysicalServers

VirtualHosts

BladeServers

ImageArchives

Workload Decoupledfrom Hardware

PlateSpin® Migrate

With PlateSpin Migrate, you can automatically migrate server workloads over the network.


PlateSpin® MigrateWorkload OS Support for P2P

ServerOperating Systems

• Windows Server 2008(32 and 64-bit)

• Windows Server 2003(32 and 64-bit)

• Windows 2000 Server • SUSE® Linux Enterprise

8-11 (32 & 64-bit)• Red Hat Linux 3-5

(32 and 64-bit)

DesktopOperating Systems

• Windows Vista(32 and 64-bit)

• Windows XP pro

• Windows 2000 Server

All third-party trademarks are the property of their respective owners.


Value of PlateSpin® Migrate for Hardware Migrations

Easy way to upgrade at the end of a lease cycle

Quicker than manual installation

Reliable and repeatable no 'power on and pray'

Not tied to similar hardware, can upgrade to and from any standard (x86/amd64) hardware vendor.

Change control

Testing and staged cutover via Server Sync

How Does PlateSpin® Migrate 'Know' About Your Target Hardware?

Demo: Show driver repository, how to upload.


Features of PlateSpin® Migrate that Helps with Hardware Upgrades

Optimized for wide area networks

Live transfer and Server Sync technology reduce production downtime, and bandwidth requirements.

Data consistency is ensured between source and target workloads with Server Sync.

Automation of common post migration configuration and testing tasks

Operating System Agnostic and Broad hardware platform support


Direct Transfer (Peer-to-peer)

Source Site Target Site

1

Requirements

• Site to site interconnect• Large Bandwidth• Small Used Disk Space (<50 GB)


Direct Transfer (Peer-to-peer)


1

Requirements

• No direct interconnect

• Large Used Disk Space (>50 GB)

2Classic File TransferSAN ReplicationRemovable Media

3


Staged Transfer With Images and Server Sync


1

Requirements

• Site to site interconnect• Small Bandwidth• Large Used Disk Space (>50 GB)

2Classic File TransferSAN ReplicationRemovable Media

3

4


Unique Benefits: Need for Testing

Test your environment with minimal downtime by using Migrate’s Server Sync functionality:

With PlateSpin

Without PlateSpin®

Migrate

Test

Cut Over

Migrate

Test & Validate

Cut Over


Unique Benefits: Optimized Testing

1 InitialWorkloadCopy

3 ServerSync

4 Cutover

2 Test andVerify

App. Users

App. TestTeamApp. Users

App. Users


Demo – P2P Process Using Migrate

• During this demo we willl:

– Set up a P2P job, using a real Linux target booted via ramdisk.

– How would you 'test' your workload

– Perform a subsequent Server Sync.


• The following steps take significantly less time as a result of utilizing PlateSpin® Migrate

– Acquire installation software– Set up volume structure– Install operating system– Apply security policy/patches – Install applications– Transfer existing data

What Are the Savings?

Time reduced by > 50 % !Migrations can be run in parallel with a high degree of consistency

Questions . . . ?

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

Documents

Accelerating Server Hardware Upgrades with PlateSpin Migrate P2P