Migrating Applications to a Target Data Center …

1 Migrating Applications to a Target data Center and the use of Cloud Computing Created by: Tom Bronack, president data Center Assistance Group, Inc. 9903 Hamilton Drive Douglasville, Georgia 30135 Phone: (017) 673-6992 Email: Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 1 Mission Statement Applications from one, or many, data centers to Primary, Secondary, and/or Recovery data Centers. Costs while sustaining current, or increasing, work loads and providing continuous operations and supplementing future growth. foot print, infrastructure, and locations that will no longer be needed. Sell, or donate, surplus equipment via Asset Management process. latest technologies to support improved performance, reliability, and continuation of business should a disaster event occur.

2 New operations through automated forms management and control system (ITIL or similar) that will accept Work Orders and associated Purchase Orders for development, implementation, support, maintenance, and recovery services. Management Reporting and Awareness to better manage the new environment. Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 2 Objectives Target environment(s) and their infrastructure, equipment, systems, and locations. migration process and the teams that will be needed to support the effort, then define their functional responsibilities. Migration Life Cycle and sequence of functions to be performed. tools needed to support migration effort and have personnel trained on new tools. Integrate tool usage within personnel functional responsibilities.

3 Applications to be migrated and the phase during which they will be moved to the Target data Center . Create a detailed Project Plan to support the migration. Bench Mark and Performance guidelines to establish baseline and performance improvements associated with migration. Support, Problem, and Change Management procedures along with other system management functions needed to support Applications . Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 3 Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 4 Example Project Goals Information Technology into two locations DC East and DC West. savings by eliminating leased facilities, back-up locations, and assets. internal Systems Development Life Cycle (SDLC) to migrate new and changed Applications to the production environment.

4 data Synchronization between sites to support recovery operations. Standards and Procedures and supportive documentation to represent the new organizational structure for both production and recovery operations. new standards and procedures within the every day functions performed by the staff, provide training and awareness to personnel, and implement periodic testing to insure ability to process workloads in production or recovery modes. a platform for future Virtualization, optimized WAN, and enhanced data Protection going forward. an efficient Information Technology environment that complies to laws and regulations (domestic and international, as needed) and enhances the company reputation thereby improving employee morale and supporting expanded sales. Migration Pathway Personnel SCOPE OF SERVICES The Conversion Specialist will be responsible for providing insight, planning, and execution of conversion activities for management systems.

5 The conversion specialist will be responsible for: Establishing management group and reporting schedule. Creating Risk Assessment to identify compliance and security guidelines. Develop Target Environment profile. Identify Applications and data to be migrated. Review Service Level Agreements for Applications being migrated and insure Service Level Reporting is adequate. Define IT Security, Encryption, Real-Time / Incremental backups, and failover requirements. Incorporate Enterprise Resiliency and Corporate Certification within migration pathway. Create application migration project plan with identified resources, timeframe, and costs. Determine use of Cloud Computing (internal / external) and define backup and recovery requirements. Identify automated tools needed to support identification, migration, and tuning process like ADDM, Sharkwire / Opnet, CiRBA, Double-Talk, AIX, Tivoli and any other identified automated tools.

6 Define migration path from selection through verification, package creation, and migration. Implement Migration Factory and other functional areas needed to perform migration duties. Perform Bench Marking of original system and migrated system and report on results. MANDATORY SKILLS/EXPERIENCE: Demonstrated depth of knowledge Migrating Applications . Demonstrated experience Migrating / converting multiple and multi-platform legacy systems into a single system. Experience in the development of conversion cleanup reporting for use by subordinate staff during data purification. Demonstrated success managing large-scale conversion projects. Direct management of analysts and programmers coding conversion routines. Experience in required Applications and technical requirements. Project Management experience.

7 Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 5 Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 6 Example Migration Pathway and Goals Migration Path Originating Site Applications Tier 1 Tier n Applications Migration Schedule Target Site Movement Complete? Decommission Originating Site Rate Applications for Movement by Tier / Group RTO Support Artifacts Infrastructure Needs Resource Needs Gap & Exceptions Obstacles Mitigate / Mediate Validate Ability to Move Validate Target Site Ability to Accept / Support Movement Testing Quality Assurance Production Acceptance Production Vital Records Access Controls Recovery Planning Acceptance Turnover N Y Applications are identified, evaluated, rated, scheduled, and moved from originating site to Target site DC East DC West Site 1 Site 2 Site 3 Site 4 Site 5 Migration Work Cycle / Flow Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page.

8 7 Start Define Target Environment Infrastructure Equipment Systems and Applications Location(s) Clients Suppliers and Vendors Identify Staff & Functions Establish Migration Process Define Management and Teams Define Functional Responsibilities Define Migration Life Cycle Assign Functions Create Migration Project Plan Define Tool Requirements Obtain Tools and Train Staff A Establish Reporting Cycle Perform Risk Assessment Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 8 A Migration Work Cycle / Flow continued Create Migration Groups & Functions Initiate Migration Process B Define Migration Application Groups Define Tools & Components in Migration Groups Define Migration Move Phases & Timeframes Benchmark Application Groups prior to move Submit Groups to Migration Factory Log Migration Groups and Schedule Copy Migration Groups via Double-Take Verify Successful Migration Benchmark Migration Application Groups Improvement ?

9 Compare Benchmark Results Report Results of Migration Phase Repeat process for all Applications Asset Management Disciplines Master Inventory Work Order Service Order Release Form Work Order Finance Form Purchase Order Ready-to-Sell Inventory Pick-Up List Equip. Type: Disp: Location: PC A Bldg 3, Rm 203 PC R Bldg 1, Rm 405 PC T Bldg 2, Rm 501 Can be sorted by: Equipment Type, Disposition, Date, or Location Warehouse Inventory Pick-Up Inventory Start Acquire Equipment Re-deploy Equipment Terminate Equipment Purchase Order Install Equipment Add to Master Inventory Compare to Master Inventory End Perform Services Disposition = A Disposition = R Disposition = T N, Exceptions List Generated Y Archive Service Order Equipment is being Actively used Equipment is moved to new location Equipment is Sold or Disposed of Marketing & Sales Dispose of Surplus equipment after Migration to Target data Center (s) to reap profit from sales, return of equipment storage space, and personnel.

10 Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 9 Updating the Standards and Procedures Manual Standards And Procedures Manual Equipment Redeployment Procedures Equipment Donation Procedures Equipment Termination Procedures Update manual to Include new procedures for equipment Redeployment, Donation, and Termination in accordance with Legal, Environmental, Business, and Regulatory Requirements. Train Staff on new procedures and provide Maintenance and Support Services going forward. Log & schedule, Pick-up, data Wipe, Reconfigure, Package, Store, Deliver, Document, Notify, Track, History. Log & schedule, Pick-up, data Wipe, Reconfigure, Certify, Package, Store, Donate, Document, Notify, Track, History.