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

1. PlateSpin® Migrate50 Migrations in less than 24 hours Jason Dea – Product Marketing Manager, Novell

2. Session Overview Barriers to Platform Adoption PlateSpin Migrate Accelerate ROI PlateSpin in Action - Essent®

3. Who cares?

5. Barriers to Platform Adoption:

6. Manual Rip and Replace How do I get this stuff Up and Running?

8. Image Capture -> Image Deploy -> System Configuration -> Pray…

9. Error Prone

10. NOT Cross Platform

11. Downtime throughout the process

13. Configure Identical OS Target -> Data Replication – System State Copy -> Pray -> Cutover

14. Software licensing complexity and cost

15. Replication complexity and cost

17. SysPrep

18. Lack of Network Optimization

19. Single Platform Support

21. PlateSpin®Migrate With PlateSpin Migrate, you can automatically migrate server workloads over the network. Physical Servers Blade Servers Virtual Hosts Image Archives Workload Decoupled from Hardware Decouple workload from host infrastructure Live peer-to-peer workload migration Migration testing Sync-up prior to cut-over

22. PlateSpin Migrate – Accelerate ROI

24. Hypervisor agnostic, migrate to ESX, Hyper-V, Xen

25. Hardware agnostic, migrate to bare metal

26. Multi-OS support

27. Migrate over LAN or WAN

29. Migration Project Cost vs Novell ROI 200 Server Refresh Migration time: 7 hours per server avg. 200 x 7 = 1400 hours 175 days 8 man months! x $80hr = $112,000 200 Server Refresh w/Novell Migration Time: 3 hours per server avg. 200 x 3 = 600 hours 3 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

30. Customer Success Case StudyEssent

31. Case Study 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

32. Case Study The Challenge Mandate to shrink 3 datacenters into one Wanted to standardize IT infrastructure Focus on minimizing risk

33. 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

34. 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

35. Helpful Hints and Best Practices

37. Eliminate/Reduce testing and configuration of migrated workloads

38. Ensure migrated workloads contain the most recent data

40. Small Outage Windows, weekends, 24 hours or less…

41. Data skew, between production workloads and migrated workloads

42. Configuration and testing of migrated workloads adds hours to each migration.

43. Moving To disimilar hardware archetectures, AMD to Intel, Paxville to Dunnington XEON processors etc.

45. Live Transfer and Server Sync technology reduce production downtime, and WAN bandwidth requirements.

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

47. Automation of common post migration configuration and testing tasks

49. Architecture Local Hardware Migration In this diagram, Corporate Headquarters (10.10.x.x) Target Blade Servers Satellite A (10.10.120.x) Target Virtual Servers Target Physical Servers Source Physical Servers PlateSpin Migrate Server Source Physical Servers Building B (10.160.x.x) Building A (10.140.x.x) PlateSpin Migrate Server PlateSpin Migrate Server Target Rack Servers Target Blade Servers Source Physical Servers Source Physical Servers

50. Architecture Remote Datacenter Consolidation In this diagram, Corporate Headquarters (10.10.x.x) Target Blade Servers Target Virtual Servers PlateSpin Migrate Server Source Physical Servers Building B (10.160.x.x) PlateSpin Migrate Servers Source Physical Servers

51. Architecture Staged Datacenter Migrations In this diagram, Corporate Headquarters (10.10.x.x) Target Blade Servers PlateSpin Migrate Servers Satellite Site (10.160.x.x) PlateSpin Image Servers Source Physical Servers Target Rack Servers

52. Architecture Staged Datacenter Migrations In this diagram, Corporate Headquarters (10.10.x.x) Target Blade Servers PlateSpin Migrate Servers Source Physical Servers Satellite Site (10.160.x.x) PlateSpin Image Servers Source Physical Servers

53. Direct Migrations Secondary Datacenter Communication path Primary Datacenter Data Path Data Path Communication path

54. Staged Migrations Secondary Datacenter Incremental Replication Primary Datacenter Data Path Data Path Image Repository Shipped to Secondary Datacenter

55. Thank you!Jason Dea – jason.dea@novell.com

56. Questions?

58. 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 Disclaimer 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.