50 migrations in 24 hours


Published on

Learn how PlateSpin Migrate can help to accelerate your server consolidation and hardware migration efforts.

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Customer successes. More stories available at http://www.novell.com/success
  • 50 migrations in 24 hours

    1. 1. PlateSpin® Migrate50 Migrations in less than 24 hours<br />Jason Dea – Product Marketing Manager, Novell<br />
    2. 2. Session Overview<br />Barriers to Platform Adoption<br />PlateSpin Migrate<br />Accelerate ROI<br />PlateSpin in Action - Essent®<br />
    3. 3. Who cares?<br />
    4. 4. Server Migration in the Real World<br /><ul><li>“The PlateSpin solution from Novell saved Essent about €2 million for the data centre consolidation project alone”</li></ul>Marco Spoel, Project Manager, IT Infrastructure, Essent<br /><ul><li>"Using PlateSpin we were able to complete 61 migrations within the targeted migration windows, saving an average of 4 hours migration time per server.“</li></ul>JorisHaverkort, Product Manager at Atos Origin Netherlands<br /><ul><li>"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.“</li></ul>Neil Brindley, Senior Windows Systems Engineer, Midrange Services, AXA Tech Asia Pacific<br />
    5. 5. Barriers to Platform Adoption: <br />
    6. 6. Manual Rip and Replace<br />How do I get this stuff Up and Running?<br />
    7. 7. Tools: Bare Metal Restore<br />?<br /><ul><li>Multiple Steps
    8. 8. Image Capture -> Image Deploy -> System Configuration -> Pray…
    9. 9. Error Prone
    10. 10. NOT Cross Platform
    11. 11. Downtime throughout the process
    12. 12. Labor Intensive</li></li></ul><li>Tools: Pre-Staging + Replication<br /><ul><li>Multiple Steps
    13. 13. Configure Identical OS Target -> Data Replication – System State Copy -> Pray -> Cutover
    14. 14. Software licensing complexity and cost
    15. 15. Replication complexity and cost
    16. 16. Labor Intensive</li></li></ul><li>Tools: “Free” Migration tool<br /><ul><li>Extra Manual steps
    17. 17. SysPrep
    18. 18. Lack of Network Optimization
    19. 19. Single Platform Support
    20. 20. Minimal Error Logging</li></li></ul><li>Finally a Better Way PlateSpin Migrate<br />
    21. 21. PlateSpin®Migrate<br />With PlateSpin Migrate, you can automatically migrate server workloads over the network.<br />Physical<br />Servers<br />Blade<br />Servers<br />Virtual<br />Hosts<br />Image<br />Archives<br />Workload Decoupled<br />from Hardware<br />Decouple workload<br />from host<br />infrastructure<br />Live peer-to-peer <br />workload migration<br />Migration testing<br />Sync-up prior <br />to cut-over<br />
    22. 22. PlateSpin Migrate – Accelerate ROI<br />
    23. 23. Automated Peer to Peer with PlateSpin Migrate<br />etc...<br /><ul><li>Direct Peer to Peer
    24. 24. Hypervisor agnostic, migrate to ESX, Hyper-V, Xen
    25. 25. Hardware agnostic, migrate to bare metal
    26. 26. Multi-OS support
    27. 27. Migrate over LAN or WAN
    28. 28. Fully Automated Solution</li></li></ul><li>Accelerating Adoption with PlateSpin Migrate<br />Server Migration project are time consuming. <br />Challenges <br />Manual rebuild process<br />5-7 hrs per server (depending on application)<br />Which workloads/applications go where?<br />Single core onto Multi-core? <br />CPU bottle necks, I/O contention, Memory?<br />Solution ‏<br />100% automated <br />Live migrations<br />45 min. to 1 ½ hr migration time<br />Peer to Peer across the network<br />Up to 20 migrations per Migrate <br />server<br />
    29. 29. Migration Project Cost vs Novell ROI <br />200 Server Refresh<br />Migration time: <br />7 hours per server avg.<br />200 x 7 = 1400 hours<br /> 175 days<br />8 man months!<br />x $80hr = $112,000<br />200 Server Refresh w/Novell<br />Migration Time: <br />3 hours per server avg.<br />200 x 3 = 600 hours<br />3 Concurrent migrations = 200 hours<br /> 25 days<br />1 month!<br />x $80hr = $16,000<br />License Cost approx. = $40,000 <br />Total Project Cost = $40k + $16k <br />ROI/Delta = $56,000<br />
    30. 30. Customer Success Case StudyEssent<br />
    31. 31. Case Study<br />The Customer<br />The leader in the Dutch energy market <br />Turnover of EUR 6.4 billion in 2006<br />Annual IT budget of EUR 130 million<br />12,000 employees and 800+ IT staff<br />700 servers and growing 100 per year<br />A mix of virtual and physical moves<br />Moving from HP to IBM hardware<br />
    32. 32. Case Study<br />The Challenge<br />Mandate to shrink 3 datacenters into one<br />Wanted to standardize IT infrastructure<br />Focus on minimizing risk<br />
    33. 33. Case Study<br />The Solution<br />Looked at VMware Converter initially – no P2P, V2P<br />PlateSpin Recon to monitor the existing estate for new hardware planning and consolidation<br />PlateSpin Migrate for 260 migrations (P2P and P2V) across sites<br />New Site<br />
    34. 34. Case Study<br />“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. <br />With PlateSpin, we were able to migrate all of our servers in one month with a team of less than eight people. <br />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.” <br />Marco Spoel, Project Manager, IT Infrastructure, Essent<br />
    35. 35. Helpful Hints and Best Practices<br />
    36. 36. Solution OverviewLarge Scale Migration<br />Goals<br /><ul><li>Move the maximum number of workloads in the minimum amount of time
    37. 37. Eliminate/Reduce testing and configuration of migrated workloads
    38. 38. Ensure migrated workloads contain the most recent data
    39. 39. Reduce Migration Impact on Users, Servers and Networks</li></li></ul><li>Solution OverviewDatacenter Move/Hardware Migration<br />Problems<br /><ul><li>Slow/Latent/Expensive/Busy Network connections
    40. 40. Small Outage Windows, weekends, 24 hours or less…
    41. 41. Data skew, between production workloads and migrated workloads
    42. 42. Configuration and testing of migrated workloads adds hours to each migration.
    43. 43. Moving To disimilar hardware archetectures, AMD to Intel, Paxville to Dunnington XEON processors etc.
    44. 44. Many different operating systems within the datacenter, that require many different migration tools</li></li></ul><li>Solution OverviewDatacenter Move/Hardware Migration<br />Advantages<br /><ul><li>Optimization for WAN migrations (latent/slow/throttled) and support for staged migrations
    45. 45. Live Transfer and Server Sync technology reduce production downtime, and WAN bandwidth requirements.
    46. 46. Data consistency is ensured between Source and target workloads with Server Sync.
    47. 47. Automation of common post migration configuration and testing tasks
    48. 48. Agnostic Operating System and Hardware Platform support</li></li></ul><li>6 Keys to Speed<br />Install PlateSpin Migrate in Advance<br />Know your Network<br />Discover Source Workloads in Advance<br />Use Our Advanced Features (PS Analyzer)<br />Don’t Forget Domain Group Policies<br />Use Windows Services Control<br />
    49. 49. Architecture<br />Local Hardware Migration <br />In this diagram, <br />Corporate<br />Headquarters<br />(10.10.x.x)<br />Target<br />Blade<br />Servers<br />Satellite A<br />(10.10.120.x)<br />Target<br />Virtual<br />Servers<br />Target<br />Physical<br />Servers<br />Source <br />Physical<br />Servers<br />PlateSpin <br />Migrate<br />Server<br />Source<br />Physical<br />Servers<br />Building B<br />(10.160.x.x)<br />Building A<br />(10.140.x.x)<br />PlateSpin Migrate<br />Server<br />PlateSpin Migrate<br />Server<br />Target<br />Rack<br />Servers<br />Target<br />Blade<br />Servers<br />Source<br />Physical<br />Servers<br />Source<br />Physical<br />Servers<br />
    50. 50. Architecture<br />Remote Datacenter Consolidation <br />In this diagram, <br />Corporate<br />Headquarters<br />(10.10.x.x)<br />Target<br />Blade<br />Servers<br />Target<br />Virtual<br />Servers<br />PlateSpin <br />Migrate<br />Server<br />Source<br />Physical<br />Servers<br />Building B<br />(10.160.x.x)<br />PlateSpin Migrate<br />Servers<br />Source<br />Physical<br />Servers<br />
    51. 51. Architecture<br />Staged Datacenter Migrations <br />In this diagram, <br />Corporate<br />Headquarters<br />(10.10.x.x)<br />Target<br />Blade<br />Servers<br />PlateSpin <br />Migrate<br />Servers<br />Satellite Site<br />(10.160.x.x)<br />PlateSpin<br />Image<br />Servers<br />Source<br />Physical<br />Servers<br />Target<br />Rack<br />Servers<br />
    52. 52. Architecture<br />Staged Datacenter Migrations <br />In this diagram, <br />Corporate<br />Headquarters<br />(10.10.x.x)<br />Target<br />Blade<br />Servers<br />PlateSpin <br />Migrate<br />Servers<br />Source<br />Physical<br />Servers<br />Satellite Site<br />(10.160.x.x)<br />PlateSpin<br />Image<br />Servers<br />Source<br />Physical<br />Servers<br />
    53. 53. Direct Migrations <br />Secondary<br />Datacenter<br />Communication path<br />Primary Datacenter<br />Data Path<br />Data Path<br />Communication path<br />
    54. 54. Staged Migrations <br />Secondary<br />Datacenter<br />Incremental Replication<br />Primary Datacenter<br />Data Path<br />Data Path<br />Image Repository Shipped to Secondary Datacenter<br />
    55. 55. Thank you!Jason Dea – jason.dea@novell.com<br />
    56. 56. Questions?<br />
    57. 57.
    58. 58. Unpublished Work of Novell, Inc. All Rights Reserved.<br />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.<br />General Disclaimer<br />This 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.<br />