Application Migration

Transcription

1 Any App. Any Server. Any Cloud. Application Migration LESSONS FROM A WINDOWS SERVER 2003 REMEDIATION PROJECT AT A LARGE FINANCIAL SERVICES ORGANIZATION Greg O Connor, AppZero CEO grego@appzero.com Neil Phasey, Rone Consulting nphasey@roneconsulting.com

2 Housekeeping Please Participate Use the GoToWebinar controls to ask questions We ll take most questions at the end

3 o Agenda: State of the market Agile Migration process Case Study: Large Financial Services Organization

4 AppZero at a Glance AppZero is the fastest, most flexible way to move applications from machine to machine Named to 10 Cloud Startups to Watch Select Cloud Service Providers and System Integrators

5 Enterprise Application Migration AppZero does for apps what VMs do for machines Source Machine Discover Copy & Run Destination Machine Extract VAA Dissolve & install AppZero extracts existing enterprise applications and packages them into VAAs that can be provisioned and run natively on any OS, machine or cloud, fast.

6

7 MS/AppZero Poll Results Sept 2014 (240 attended) Enterprises: How many servers in your organization are running Windows Server 2003? Possible Answers Percent Response % % % % % Enterprises: What is your level of readiness for Windows Server 2003 end of support? Possible Answers Fall 2013 Fall 2014 Don't know when EOS is 27% 2% I know when EOS is, but have no plan 20% 9% I have started to research technical options 16% 53% I have an upgrade plan 24% 25% Other 13% 11% As part of your upgrade projects, will you be moving applications to the cloud? Possible Answers Fall 2013 Fall 2014 Yes 35% 43% Not Sure 40% 27% No 22% 23% Other 3% 7%

8 Fall 2014 MS/AppZero Poll Conclusions Enterprises have large number of applications to migrate Enterprises are now all aware of the problem Huge change in I don t know when and I don t have a plan Enterprises are still trying to figure out what to do Half are analyzing what to do Enterprises have not moved yet Statistically no change in I have a plan or other responses Cloud is gaining momentum as the destination

9 Poll Question 2 What is the timing of your projects?

10 Migration process 1 Discover 2 Assess 3 Target 4 Migrate Microsoft

11 1 Migration process: Water Fall Discover Too Much Up Front Time 2 Assess 3 Target 4 Migrate Microsoft

12 Agile Migration

13 Discovery and Assessment Help answer: What apps do I have deployed where? Microsoft Assessment Planning Toolkit BlueStripe FactFinder Citrix AppDNA Dell ChangeBASE HP Universal Discovery Lakeside Software SysTrack Do not always or often answer: Is this app compatible? If I migrate this app to WS2012 R2 will it work How long will it take to migrate all of my apps? I am bidding on a project for 10,000 machines and I want to size it right

14 Discovery and Assessment Application portfolio Windows Server 2003 situation Missing source code, not sure what is really deployed The source/production machine is the system of record Server side apps are have multiple installed components, patches, highly configured Re-install, reconfigure, patches, move data result unlikely to equal the current system Installing an application what happens? Put pieces all over the Operating System App Patching, topology configuration variations, security updates further complicated the issue Result: There is no map of an app and all its dependencies Chicken or egg problem Is this app compatible? I must know what the app and all its dependencies are in order to answer the compatibility questions An AppZero migration identifies an app and all of its dependencies but I want to know that before I invest and do a migration An approach Migrate and then assess

15 Migration Process: Agile Approach Application centric categorization taxonomy and grouping 1 Type 2 Tech 3 Topology 4 Biz Critical Start with a give <Type> <Tech> <Topology> <Biz-Critical> End to End migration cycle, learn, iterate, improve Remove white space from end to end process 1 Discover 2 Assess 3 Target 4 Migrate Move by changing the following characteristic <Biz-Critical> <Topology> <Tech> <Type> Dev, Test, UAT, Prod, DR harmonize the sandboxes

16 Top 3 Applications Migrated off Windows Server 2003 AppZero recommend app portfolio taxonomy and migration approach Percent of portfolio App Classification Migration App Approach 20 40% COTS Upgrade path ** 20 40% COTS app heavily customized AppZero 20 40% Homegrown or Bespoke AppZero ** Some business still choose AppZero for Apps that are going to be retired in 2 or 3 years Apps where COTS migration path is very long To assist and reduce time in COTS upgrade path Move to WS2012 and then COTS in-place upgrade

17 Poll Question 1 What is the primary approach you will use for your migrations?

18 Rone Consulting Infrastructure and Application Modernization Lessons from a Financial Services 2003 Remediation

19 Scope of the challenge Large Financial Institution in Canada Windows 2003 Servers Initial target of 18 months to complete remediation of the footprint Phase 1 successfully remediated ~800 servers (~46 Applications) Duration 3.5 months Exited phase 1 with a 70% efficiency increase Phase 2 target ~600 servers (~85 applications) over 3 months

20 The business case for migrating Win2003 Server Support for Windows Server 2003 ends July 2015 Risk - There will no longer be any updates from Microsoft, increasing the risk of security breaches Compliance - Organizations will be unable to meet the legal and regulatory requirements for many industries Cost - Custom Support Agreements will significantly increase cost to support Win2003 The challenge is IT STILL WORKS and organizations feel they can upgrade in the fullness of time Risk and the Cost of Custom Support alone are not yet enough to stimulate the remediation of windows 2003 The remediation of 1000 s of servers across the enterprise is a daunting and costly undertaking. It is important to look for combined value opportunities to support a solid business case: Mitigate Risk and support compliance requirements related to Windows 2003 Server Reduce Custom Support Costs for Windows 2003 Server Support other dependent aging technology upgrades e.g. Backup and Monitoring clients Drive Strategic Business Value through efficient migration paths and supporting future agility Drive Savings through the decommissioning of legacy infrastructure (power/maintenance/real estate costs) Drive Cost Avoidance, agility and strategic infrastructure direction through virtualization and moving to the cloud

21 Key drivers for the move Server Optimization and footprint reduction Achieve 85% virtualization across the x86 platform Reduce x86 physical footprint by 70% (Virtual First Policy) Reduce operational costs through migrating and decommissioning Improve aging infrastructure refresh rate Mitigate risk and costs associated with Windows 2003 Server end-of-life Reduce Custom Support Costs Mitigate Risk Support compliance requirements Windows 2003 Server was targeted as an opportunity platform to stimulate technology currency refresh rates across the stack (HW/OS/DB/App) and accelerate virtualization

22 Some key challenges Large and overwhelming footprint to remediate Lack of understanding as to how big the problem was, how to fix it and how much it would cost No internal competency to support large-scale migrations Nothing stimulating the lines of business to remediate aging technology business enhancement drivers take priority Long lead times for infrastructure provisioning Change freeze windows Key constraint points at the application SME level Complex internal processes with inherent latency

23 Considerations to support a solid foundation Create a dedicated delivery program with the end-goal of remediating all servers efficiency will increase as the program progresses Build a foundation competency providing a repeatable factory-based approach to server remediation that will be integrated into the organization at a future date Leverage technology-assisted migration tools to drive efficiency Divide the program into executable chunks Target a scope of work that is achievable and has executive support for the first phase of the program success is key to achieve buy-in and support Allow time for ramp-up Design, implement and integrate people and processes Integrate and prove-out new technologies to drive increase efficiency Look for Low-Hanging Fruit and other opportunities to accelerate progress Look for opportunities with high server-to-app ratio s Stabilize the competency and sell a proven and efficient delivery model to the rest of the organization Align with the internal processes and organizational structure Integrate resources into the organizations structure to ease the approval, transition process and support competency integration Ensure you plan for change freezes Align the delivery programs processes with the organizations internal processes and remove latency through a dedicated delivery team

24 Considerations to support a solid foundation cont Implement and follow a structured methodology Analyze : understand application footprint and implications of the buy/sell/hold list Assess : high and low level designs and tribal knowledge gathering and documentation as input to remediation effort/migration approach/provisioning Provision : order and implement new infrastructure - get ahead of provisioning so that this does not negatively impact the delivery timelines Build : target platform build-out Deploy : application migration and deployment to target platforms Transition: final acceptance and handover to operations Decommission : removal of legacy infrastructure Leverage multiple modes of remediation to drive efficiency across all application types Technology Assisted migrations / Expedited Factory-Based Migrations and deployments / Manual Deployments Enable an effective PMO structure with key performance indicators to reflect the right level of progress Reporting at an application or server migration level alone is not good enough effort and time is heavily weighted to the backend deployment show progress throughout the process to obtain support Report on key metrics : Assessments / Server Provisioning / Server Builds / Server and application remediations / Server decommissions

25 Application Footprint Analysis/Assessment Data Collection Classification Characterization Data collection tools Inventory and affinity QA and Refinement LOB Engagement Replace Migrate Retire Application category Application affinity Migration path Like for like / like for right Complexity & effort driven largely by: Infrastructure Deployment Patterns Affinity (interconnect with other apps) Additional attributes: Data quality to support analysis and design Clear roadmap from business Define the opportunity landscape 1. Designs 2. Expected effort, cost, timeline 3. Approach Technology Assisted Accelerated path Specialized hardware Specialized authentication, entitlement Internet facing (DMZ) requirements # distinct server roles Clustered apps, DBs Multi-stack environments Vendor COTS (possibly modified)

26 Pragmatic Phased Approach Phase 1 Target a footprint that is achievable, has executive support and develop a core migration competency Integrate and align people and process Introduce New Tools, prove out and improve Build competency foundation and increase efficiency Complete phase 1 server / application remediations Drive expanded buy-in through success and efficiency improvements Integrate lessons learned and improve processes Phase 2 Leverage successes and efficiency gains from phase 1 to expand target footprint Complete Technology Services footprint Target specific LOB application opportunities based on execution value adds Complete phase 2 server / application remediations Integrate lessons learned and improve processes Phase 3 Increased Efficiency Add capacity, complete migrations at higher efficiency rates and integrate competency Complete remainder of application footprint across the remainder of the organization Integrate the migration competency into Life Cycle Management Complete program close-out and final hand-over activities Complexity is driven by the number/complexity of applications, not the number of servers

27 Lessons - Migration competency value proposition Technology-assisted Application Migration: Vendor product (AppZero) to migrate applications has proved highly successful Up to 100X reduction in effort migrating challenging legacy applications, multiple dependencies Environmental Acceleration: Enterprise process hybridized for maximum throughput Up to 10X reduction in cycle time provisioning new target environments compared to business as usual Ad-hoc Technical Assist: Multiple levels of intervention, as project requires Any / all of these accelerators can greatly expand the scope of planned migrations in a given timeframe Understanding the true value proposition can help in further penetrating other parts of the organization with a compelling business case

28 Lessons Process Obligations Enterprise work silo workflow is usually optimized for utilization, not throughput Migration Competency - optimized for throughput by internalizing many workflow activities: Physical / virtual server provisioning Design approach and associated validation Generic (OS, DB, MW) physical / virtual build and all required validation As appropriate: application migration / upgrade / deployment and all required QA validation Documentation and all standard artifacts for hardened PAT, PROD, DR application support Migration Competency aligned 100% with enterprise process requirements: Exploit existing work ticket and change management practices Enterprise Operations final acceptance for checkpoints ('handoff'; 'first server'; 'activation )

29 Lessons Workflow, Artifacts and Pipeline Additional roles / responsibilities to ensure efficient and effective delivery PM ownership of deliverables end-to-end through entire lifecycle Assessment and Documentation resources resources to capture tribal knowledge Decommission management resources to ensure release of legacy infrastructure Define a Unit Cost through well established effort levels Well established effort levels for Assessment, Provision, Build and Decommission App Deploy has varied widely based on terms of engagement, tech-assist, and complexity Ensure artifact self-sufficiency & gathering of tribal knowledge Clarity on app testing exit terms, particularly for LOB apps or supporting platforms Advance agreement / understanding of QA testing in PAT environment Performance comparison and obligations between source and target environments Completeness of documentation Assessment Provision Build AppDeploy Remediate

30 Lessons Technical and Environmental Change Advisory plan on minimal throughput Exemptions are non-binding: approval even with an exemption is unreliable RED advisories should presume very limited traction for change requests, particularly Year End and Network Several practices proved essential in steering changes through the gauntlet: Use of Standard changes (i.e. repeatable, 24 hour lead time, low to medium risk) Disclaimers on the use of shared infrastructure (server, network, storage, circuit et al) Executive sponsorship during various extracurricular CAB sessions Beware the post-freeze crush Additional complexities: increased lead time impacts SSL certificate renewal DMZ applications DNS configuration SMTP activation Service accounts

31 Some Key value drivers Benefit Category Description Key Outcome Measurable Improvement Phased Program Approach and use of technology-assisted migrations Phase 1 Remediate initial footprint target and increase efficiency through core migration competency Successfully exceeded migration targets Improved Efficiency rates by 70% going into phase 2 Achieve significant executive support through show of success 70% increase in migration/remediation efficiency Optimized program throughput Maintain compliance with BAU process and artifacts, but engineer program to optimize throughput Faster build and application deploy cycle time Higher throughput of program deliverables. Example: standard build reduction to 5 days from 23 days Use of emerging technologies (i) (appzero) Transpose "As Is" Application Migration Faster cycle time for migrations, as applicable (100x) Minimal time required of application SME resources Reduction of effort by ~60hrs per server 36 servers Use of emerging technologies (ii) (appzero) Internet Information Server (IIS) in-place Uplift In-place uplift of IIS versions Minimal time required of application SME resources Reduction of effort by 4 hours per server for IIS uplift Use of emerging technologies (iii) (appzero) Database Migration Faster cycle time for hybrid database migrations, as applicable Minimal time required of application SME resources Reduction of effort by 20 hours per DB server - ~850 servers Build Improvements (i) Automated Virtual Citrix Build Reduction in cycle time for build of new virtual Citrix environments Reduction in build time by 11hrs per server 350 servers Build Improvements (ii) Higher Capacity Access to Golden Image Reduction in cycle time for build of new OS environments Reduction in build time by15 minutes per server 5400 servers Virtual Yield Improvements Achieved a significantly higher penetration - greater than 80% server virtualization Benefits of server virtualization cost avoidance and increased time to delivery Potentially 20% increase in virtualization yield

32 Questions? Next Steps: Want Neil s help with your project or have questions? Contact Neil at nphasey@roneconsulting.com Want to try AppZero for yourself? Request a free trial at Read the new whitepaper, Migrating from WS2003 to Newer Operating Systems and the Cloud: