50 migrations in 24 hours

PlateSpin® Migrate50 Migrations in less than 24 hours

Jason Dea – Product Marketing Manager, Novell

Session Overview

Barriers to Platform Adoption

PlateSpin Migrate

Accelerate ROI

PlateSpin in Action - Essent®

Who cares?

Server Migration in the Real World

• “The PlateSpin solution from Novell saved Essent about €2 million for the data centre consolidation project alone”

– Marco Spoel, Project Manager, IT Infrastructure, Essent

• "Using PlateSpin we were able to complete 61 migrations within the targeted migration windows, saving an average of 4 hours migration time per server.“

– Joris Haverkort, Product Manager at Atos Origin Netherlands

• "The ability to perform the migrations remotely and over the WAN with no need to be physically in contact with the source and target servers saved us weeks if not months of work.“

– Neil Brindley, Senior Windows Systems Engineer, Midrange Services, AXA Tech Asia Pacific

Barriers to Platform Adoption:

Manual Rip and Replace

How do I get this stuff Up and Running?

Tools: Bare Metal Restore

• Multiple Steps– Image Capture -> Image Deploy -> System Configuration -> Pray…

• Error Prone• NOT Cross Platform• Downtime throughout the process• Labor Intensive

Tools: Pre-Staging + Replication

• Multiple Steps– Configure Identical OS Target -> Data Replication – System State Copy ->

Pray -> Cutover

• Software licensing complexity and cost• Replication complexity and cost• Labor Intensive

Tools: “Free” Migration tool

• Extra Manual steps– SysPrep

• Lack of Network Optimization• Single Platform Support• Minimal Error Logging

Finally a Better Way PlateSpin Migrate

Decouple workloadfrom host

infrastructure

Live peer-to-peer workload migration

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

Migration testing Sync-up prior to cut-over

PlateSpin® Migrate

PhysicalServers

VirtualHosts

BladeServers

ImageArchives

Workload Decoupledfrom Hardware

PlateSpin Migrate – Accelerate ROI

Automated Peer to Peer with PlateSpin Migrate

• Direct Peer to Peer• Hypervisor agnostic, migrate to ESX, Hyper-V, Xen• Hardware agnostic, migrate to bare metal• Multi-OS support• Migrate over LAN or WAN• Fully Automated Solution

etc...

Accelerating Adoption with PlateSpin Migrate

Challenges Manual rebuild process5-7 hrs per server (depending on application)Which workloads/applications go where?Single core onto Multi-core? CPU bottle necks, I/O contention, Memory?

Solution 100% automated Live migrations45 min. to 1 ½ hr migration timePeer to Peer across the networkUp to 20 migrations per Migrate server

Server Migration project are time consuming.

Migration Project Cost vs Novell ROI

200 Server RefreshMigration time:

7 hours per server avg.

200 x 7 = 1400 hours

175 days

8 man months!

x $80hr = $112,000

200 Server Refresh w/NovellMigration Time: 3 hours per server avg.200 x 3 = 600 hours3 Concurrent migrations = 200 hours

25 days 1 month!x $80hr = $16,000

License Cost approx. = $40,000 Total Project Cost = $40k + $16k

ROI/Delta = $56,000

Customer Success Case StudyEssent

The Customer

– The leader in the Dutch energy market

– Turnover of EUR 6.4 billion in 2006

– Annual IT budget of EUR 130 million

– 12,000 employees and 800+ IT staff

– 700 servers and growing 100 per year

– A mix of virtual and physical moves

– Moving from HP to IBM hardware

Case Study

The Challenge

– Mandate to shrink 3 datacenters into one

– Wanted to standardize IT infrastructure

– Focus on minimizing risk

Case Study

The Solution

– Looked at VMware Converter initially – no P2P, V2P

– PlateSpin Recon to monitor the existing estate for new hardware planning and consolidation

– PlateSpin Migrate for 260 migrations (P2P and P2V) across sites

New Site

Case Study

• “If we hadn’t gone with PlateSpin, it would have taken a team of 25 half a year to build all the applications in the new data center, an estimated cost of over EUR 3 million.

• With PlateSpin, we were able to migrate all of our servers in one month with a team of less than eight people.

• The PlateSpin solution brings a high return of investment. In retrospect, after seeing the time and cost savings, we would have been willing to pay a lot more for the PlateSpin solution.”

Marco Spoel, Project Manager, IT Infrastructure, Essent

Helpful Hints and Best Practices

Solution OverviewLarge Scale Migration

Goals• 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

Solution OverviewDatacenter Move/Hardware Migration

Problems• 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

Solution OverviewDatacenter Move/Hardware Migration

Advantages• Optimization for WAN migrations (latent/slow/throttled)

and support for staged migrations• Live Transfer and Server Sync technology reduce

production downtime, and WAN bandwidth requirements.

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

• Automation of common post migration configuration and testing tasks

• Agnostic Operating System and Hardware Platform support

6 Keys to Speed

1. Install PlateSpin Migrate in Advance

2. Know your Network

3. Discover Source Workloads in Advance

4. Use Our Advanced Features (PS Analyzer)

5. Don’t Forget Domain Group Policies

6. Use Windows Services Control

In this diagram,

ArchitectureLocal Hardware Migration

PlateSpin MigrateServer

TargetBladeServers

SourcePhysicalServers

Building A(10.140.x.x)

PlateSpin MigrateServerTarget

RackServers Source

PhysicalServers

Building B(10.160.x.x)

Source PhysicalServers

TargetPhysicalServers

Satellite A(10.10.120.x)

CorporateHeadquarters(10.10.x.x)

TargetVirtualServers

TargetBladeServers

In this diagram,

ArchitectureRemote Datacenter Consolidation

PlateSpin MigrateServers

Building B(10.160.x.x)

CorporateHeadquarters(10.10.x.x)

TargetVirtualServers

TargetBladeServers

In this diagram,

ArchitectureStaged Datacenter Migrations

TargetRackServers

Satellite Site(10.160.x.x)

CorporateHeadquarters(10.10.x.x) Target

BladeServers

PlateSpinImage

Servers

In this diagram,

ArchitectureStaged Datacenter Migrations

Satellite Site(10.160.x.x)

CorporateHeadquarters(10.10.x.x) Target

BladeServers

PlateSpinImage

Servers

SecondaryDatacenter

Communication path

Primary Datacenter

Data Path

unication p

Data Path

Direct Migrations

SecondaryDatacenter

Primary Datacenter

Image Repository Shipped to Secondary Datacenter

Incremental Replication

Data P

Data Path

Staged Migrations

Thank you!

Jason Dea – jason.dea@novell.com

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.

50 migrations in 24 hours

Technology

Transcript of 50 migrations in 24 hours

Bantu Migrations

50 Hours of Origami

Salgado Migrations

North america migrations

Israel's Migrations Intro

Doctrine migrations

Etude Migrations Mineurs

Human Migrations

jewish migrations

Migrations - ayamun

East Africa Migrations

TRAINING OFFER - if-algerie.com · Advanced 1 B2.1 50 hours Advanced 2 B2.2 50 hours Advanced 3 B2.3 50 hours DELF B2 Independent Independent 1 C1.1 50 hours Independent 1 C1.2 50

passeport migrations

BSC. MEDICAL SOCIOLOGY...Theory – 250 Hours & Practical – 50 Hours ANATOMY: THEORY HOURS 125, PRACTICAL HOURS 25 HOURS Sl. No. TOPICS / THEORY HRS PRACTICAL HRS 1 Introduction

BALKAN MIGRATIONS

WP migrations

Disciplinary . I I. , . I . I , Record (50 Hours)

Clinical Policy: Factor VIII (Human, Recombinant)...hours (12-24 hours for age < 6 years) Major episodes: 40- 50 IU/kg every 12- 24 hours (8 to 24 hours for age < 6 years) 50 IU/kg

III. Migrations

Enterprise Drupal Migrations: Lessons From Large-Scale Migrations