Tom Bronack, president Data Center Assistance Group, Inc. 9903 Hamilton Drive Douglasville, Georgia 30135 Phone: (017) 673-6992 Email: bronackt@dcag.com Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 1 Mission Statement 1. Migrate Applications from one, or many, data centers to Primary, Secondary, and/or Recovery Data Centers.
2. Reduce Costs while sustaining current, or increasing, work loads and providing continuous operations and supplementing future growth.
3. Reduce foot print, infrastructure, and locations that will no longer be needed. Sell, or donate, surplus equipment via Asset Management process.
4. Utilize latest technologies to support improved performance, reliability, and continuation of business should a disaster event occur.
5. Integrate 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.
6. Integrate Management Reporting and Awareness to better manage the new environment. Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 2 Objectives 1. Define Target environment(s) and their infrastructure, equipment, systems, and locations.
2. Establish migration process and the teams that will be needed to support the effort, then define their functional responsibilities.
3. Define Migration Life Cycle and sequence of functions to be performed.
4. Define tools needed to support migration effort and have personnel trained on new tools. Integrate tool usage within personnel functional responsibilities.
5. Identify 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.
6. Create Bench Mark and Performance guidelines to establish baseline and performance improvements associated with migration.
7. Implement 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 1. Combine Information Technology into two locations DC East and DC West.
2. Generate savings by eliminating leased facilities, back-up locations, and assets.
3. Provide internal Systems Development Life Cycle (SDLC) to migrate new and changed applications to the production environment.
4. Provide Data Synchronization between sites to support recovery operations.
5. Update Standards and Procedures and supportive documentation to represent the new organizational structure for both production and recovery operations.
6. Integrate 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.
7. Prepare a platform for future Virtualization, optimized WAN, and enhanced Data Protection going forward.
8. Achieve 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.
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. 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. 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: 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 ? 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. 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. Log & schedule, Pick-up, Data Wipe, Reconfigure, Certify, Package, Store, Sell, Client Pick-up, Financials, Document, Notify, Track, History. Status = T Status = D Status = R Release Date: 8/10/2013 Thomas Bronack - Application Migration Guideline Document Page: 10 Thomas Bronack - Application Migration Guideline Document Business Continuity Management Disciplines and Integration Contingency Planning Disaster Recovery Risk Management Business Recovery Charter: Eliminate Business Interruptions; Ensure Continuity of Business; Minimize Financial Impact; and Adhere to Legal / Regulatory Requirements Information Technology Protection Critical Jobs; Data Sensitivity and Access Controls; Vital Records Management; Vaulting and Data Recovery; Recovery Time Objectives; Recovery Point Objectives; and Mainframe, Mid-Range, and Servers. Risk Management Exposures (Gaps and Exceptions); Insurance; Legal / Regulatory Requirements; Cost Justification; and Vendor Agreements. Corporate Asset Protection Inventory Control Asset Management Configuration Management Business Continuity; and Office Recovery. Contingency Recovery Disciplines Contingency Recovery Planning Facilities Executive Management Personnel General Services Public Relations Finance Auditing Company Operations Information Technology Contingency Planning affects every part of the organization and is separated into logical work areas along lines of responsibility. These four Contingency Planning Disciplines allow for logical work separation and better controls Establishing interfaces with key departments will allow for the inclusion of corporate-wide recovery procedures (Security, Salvage, and Restoration, etc.) in department specific Recovery Plans Release Date: 8/10/2013 Page: 11 Thomas Bronack - Application Migration Guideline Document Asset & Inventory Management Configuration Management Capacity Management Performance Management Contingency Management Service Level Management EDP Security Management Vital Records Management Production Acceptance Production Operations Change Management Problem Management Systems Management and Controls (SMC) Application Development (SDLC) Application Maintenance Application Testing Quality Assurance Data Processing Environment Systems Management Organization Business Recovery Risk Management Disaster Management Release Date: 8/10/2013 Page: 12 Incident Management Network Management Thomas Bronack - Application Migration Guideline Document Vendor or company Site Company or Client Site Development Testing Version And Release Control Business Recovery Facility Disaster Recovery Facility Off-Site Vault End-User Request for New Product Or Service On-Line Data Files BKUP Unit and System Testing Quality Assurance Naming, Documents, and Placement Security, Vital Records, Back-up, Recovery, Audit. Production Acceptance On-Line Data Files BKUP Security, Vital Records, Back-up, Recovery, Audit. Production On-Line Data Files BKUP Vendor or Company Site Change Management Maintenance Enhance And Repair Periodic / Incremental Real-Time End-User Defines: Business Purpose, Business Data, Ownership, Sensitivity, Criticality, Usage, Restrictions, RTO and RPO, Back-Up, and Recovery. End-User Location Update Recovery New Systems Development Life Cycle (SDLC), Components and flow Release Date: 8/10/2013 Page: 13 Thomas Bronack - Application Migration Guideline Document Development Testing Maintenance Quality Assurance Production Acceptance Production Disaster Recovery Vital Records Off-Site Vault Disaster Recovery Facility
Mainframe and Office Recovery Change Management Product or Service, Service Level Management, Project Life Cycle, Work Order, Purchase Order(s), Documentation. Walk Thrus, Unit Testing, System Testing, Regression, Scenarios, Scripts, Recovery Tests, Benchmarks, Post Mortem. Test Validation, Components, Naming, Placement, Functionality, Process. Batch / On-Line, Security / Encryption, Operations, Recovery, EDP Audit. Systems Development Life Cycle, Component & Release Management, Standards & Procedures, User Guides & Vendor Manuals, Training (CBT & Classroom), etc... Service Level Reporting, Capacity Management, Performance Management, Problem Management, Inventory Management, Configuration Management. Service Level Management, Project Life Cycle. Batch and On-Line Management A Forms Management & Control System, used to originate work requests and track work until completed, will facilitate optimum staff productivity and efficiency. Systems Management Controls and Workflow Release Date: 8/10/2013 Page: 14 Thomas Bronack - Application Migration Guideline Document Schedule Request Interfaces Between Applications, QA, and Production Groups. Create Service Request Perform Technical Assessment Perform Business Assessment Perform Requested Work Application Group Testing Return to Submitter Create QA Turnover Package Submit to Production Control Successful Successful No Yes No Create Production Control Turnover Package QA Review And Accept Yes Error Loop Error Loop APPLICATIONS GROUP QA GROUP TESTING and QA Turnover Package Components:_________ Service Form and results Assessments, Change & Release Notes, Application Group Testing Results, Test Scenarios & Scripts, Messages & Codes, and Recoveries, Data for Regression and Normal Testing, Documentation. PRODUCTION CONTROL Turnover Package Components:
Explanation and Narrative, Files to be released, Predecessor Scheduling, Special Instructions, Risk Analysis, Authorizations. Perform Requested Work QA Review Meeting Perform Post- Mortem CP # 1 CP # 2 CP # 3 Perform User Acceptance Testing Quality Assurance and PLC Checkpoints Release Date: 8/10/2013 Page: 15 Checkpoints are used to review progress and make Go / N-Go decisions, update process, and better document. Thomas Bronack - Application Migration Guideline Document SDLC Documentation Requirements and Forms Automation Development Request Form Phase: Date User Information _____________ Business Justification _____________ Technical Justification _____________ Build or Buy _____________ Development (Build / Modify) _____________ Test: _____________ Unit Testing _____________ System Testing _____________ Regression Testing _____________ Quality Assurance _____________ Production Acceptance _____________ Production _____________ Support (Problem / Change) _____________ Maintenance (Fix, Enhancement) _____________ Documentation _____________ Recovery _____________ Awareness and Training _____________ Documentation Development Request Form Number Business Need Application Overview Audience (Functions and Job Descriptions) Business / Technical Review Data Cost Justification Build or Buy Decision Interfaces (Predecessor / Successor) Request Approval Data Sensitivity & Access Controls IT Security Management System Encryption Vital Records Management Data Synchronization Backup and Recovery Vaulting (Local / Remote) Disaster Recovery Business Recovery Application Owner Documentation & Training Application Support Personnel End User Coordinators Vendors and Suppliers Recovery Coordinators Testing Results Application Setup Input / Process / Output Messages and Codes Circumventions and Recovery Recovery Site Information Travel Instructions Documents are Linked to from Date Field Link to Documents New Product / Service Development Request Form Life Cycle Documentation Documentation Documentation Development: Testing: Quality Assurance: Production Acceptance Release Date: 8/10/2013 Page: 16 8/10/2013 Thomas Bronack - Application Migration Guideline Document 17 Information Accounting and Charge-Back System Concept By utilizing Work Order (WO) and Purchase Order (PO) concepts, it is possible to track and bill clients for their use of Information Technology services associated with development and maintenance services. This concept is presented below:
User Name: ____________________ User Division: ___________ User Identifier _______ Work Order #: __________________ Date: ___________ For: _________________________ PO for: Development Cost: $ _____________ PO for: Testing Cost: $ _____________ PO for: Quality Assurance Cost: $ _____________ PO for: Production Acceptance Costs $ _____________ PO for: Production (on-going) Cost: $ _____________ PO for: Vital Records Management Cost: $ _____________ PO for: Asset Management (Acquisition, Redeployment, Termination) Cost: $ _____________ PO for: Inventory and Configuration Management Cost: $ _____________ PO for: Information and Security Management Cost: $ _____________ PO for: Workplace Violence Prevention Cost: $ _____________ PO for: Recovery Management Cost: $ _____________ PO for: Documentation and Training Cost: $ _____________ PO for: Support and Problem Management Cost: $ _____________ PO for: Change Management Cost: $ _____________ PO for: Version and Release Management Cost: $ _____________
Total Cost: $ _____________
Bill can be generated via Forms Management, Time Accounting, or Flat Cost for Services. This system can be used to predict costs for future projects and help control expenses and personnel time management. Target Environment Intel Builds Dell x86 Chips for their Servers Dell x86 Servers IBM AIX P7 (Watson) Systems using AIX VMware vSphere 5 and AIX Tivoli VMware vSphere 5 Software Supports : vShield for Cloud Computing - security, control, and compliance. vCenter Site Recovery Manager 5. vCloud Director 5 model and activate recovery and failover. EMC SAN, supporting 2 channels, AIX Storage Array, up to 2 TeraBytes of Local storage NetApp NAS to support Remote and Cloud Storage Cisco Network Equipment for remote locations Local Storage Remote Storage 1 million I/O per Sec. Thomas Bronack - Application Migration Guideline Document Double-Talk Release Date: 8/10/2013 Page: 18 Thomas Bronack - Application Migration Guideline Document Disaster Recovery Site Development Maintenance Testing and Quality Assurance Development And Maintenance Environments Company Data Electronic Transmission Electronic Transmission Systems Development Life Cycle (SDLC) New Applications End User Work Order to create a new Product or Service Open Network With Multiple Access Points Remote Locations Production Site #2 Customers; Credit Bureaus; Feed-Files; and, Other Locations. Physically Transported Using Tape Only Encryption Problem Resolution And Enhancements Send Approved Applications To Production Acceptance Cloud Computing Local Sites Local Tape / Data Vault Local Tape / Data Vault Remote Tape / Data Vault Production Site #1 Electronic Vaulting; Incremental Vaulting; and, Electronic transmission to Disaster Recovery Site Local Sites Encryption of Data at Rest to Provide Total Protection Overview of the Enterprise Information Technology Environment Encrypting Data-In- Movement will protect data being transmitted to remote sites Logical Example of Enterprise Target Environment Release Date: 8/10/2013 Page: 19 Thomas Bronack - Application Migration Guideline Document Fully Integrated Recovery Operations and Disciplines (End Goal) State and Local Government., First Responders (Fire, Police, & EMT), Department of Homeland Security (DHS), Office of Emergency Management (OEM), Local Community. Risk Management, Disaster Recovery, Business Continuity, Crisis Management, Emergency Management, Workplace Violence Prevention, Audit and HR. Private Sector Preparedness Act (Domestic Standard) CERT Resiliency Engineering Framework And COSO ISO22313 and ISO22318 (International Standard) National Fire Prevention Association 1600 Standard Contingency Command Center (CCC) Incident Command Center (IC) Help Desk (HD) Operations Command Center (OCC) Network Command Center (NCC) Corporate Certification Command Centers Information Security Management System (ISMS) based on ISO27000 Workplace Violence Prevention Emergency Operations Center (EOC) Lines of Business Emergency Response Management Business Continuity Management Business Integration Locations, Employees, Infrastructure, Equipment, Systems, Applications, Supplies, Customers. Service Level Agreements & Reporting, Systems Development Life Cycle (SDLC), COSO, CobIT, ITIL, and FFEIC, ISO Guidelines, Six Sigma or Equivalent for Performance and Workflow Management Release Date: 8/10/2013 Page: 20 ISO27000 ISMS Security Standard Existing Post Office Mail Pick-up and Delivery System An IT Communications Analogy 1. Letter has Address of Recipient and Return Address of Sender. 2. Sender drops letter into Mail Box. 3. Post Office picks letter up from Mail Box and Sorts it by Recipient Address, then routes letter via best method or priority paid for. 4. Letter is resorted at Recipient Post Office and placed into Postmans Route Bag. 5. Postman delivers letter to recipient. 6. Letter is Returned to Sender if address is incorrect or refused by Recipient. 7. This example is used as the foundation for the Internet and the Internet Protocol (IP) being used. 8. Internet is currently transitioning from IPv4 (Internet of Things) to IPv6 (Internet of Everything) because IPv4 is running out of addresses (2>32 = 4.3 Billion Addresses, IPv6 2>128 = Unlimited Addresses). This will support more addresses than there are atoms on earth, so you can expect machines of all types to have IP Addresses. Sender Recipient Mail Pick-Up Sort Route Sort Deliver 8/10/2013 Thomas Bronack - Application Migration Guideline Document 21 Internet Protocol (IP) Delivery System (Local / Remote) An IT Communications Overview Sender posts / receives data from Internet via 7 Level Internet Service Communications method. Sender Mail Recipient Route Sort Deliver From PC to Application Layer (1) From Application Layer (1) through Presentation Layer (2), Session Layer (3), and Transportation Layer (4) for delivery to receiving site. Process is repeated until message has been successfully sent and received. This is a Handshaking operation where Data Packets are sent to receiving site and acknowledged as successfully received (ACK) or not (NAK). Failures are retransmitted until received successfully or an error notification is posted (Layer 5-7). Pick-Up Sort Internet Protocol (IP) provides a sending and receiving address. IPv4 has 4.3 Billion addresses (IOT), which are almost gone, while IPv6 has unlimited Addresses (IOE). Logical Layer Physical Layer 8/10/2013 Thomas Bronack - Application Migration Guideline Document 22 Thomas Bronack - Application Migration Guideline Document Problem Identification and Response process Release Date: 8/10/2013 Page: 23 Problem Management and Circumvention Techniques VMware vSphere 5 Functions:
VMware vSphere 5 VMware vCenter Site Recovery Manager 5 VMware vCloud Director 5
Together these tools help business: Deploy business critical applications with confidence, Respond to the needs of the business with Cloud agility, and Move to Cloud Computing with confidence. VMware vSphere 5 Features: Utilizes x86 technology to provide an infrastructure- as-a-service architecture. Can support 32 Virtual CPUs with up to 1 Terabyte of memory. Support 1 million I/o per second. Provides Intelligent Policy Management by allowing a set-it and forget-it approach to managing data center resources, including server deployment and storage management through user defined profile. Profile-Driven Storage Management saves personnel administrative time. Comprehensive Cloud Infrastructure Suite, includes:
vShield 5 addresses the top enterprise concerns about Cloud Computing security, control, and compliance the vShield product family overcomes the limits of traditional security solutions by delivering an adaptive, software-based security model designed for virtual and cloud environments. vShield 5 will include new Data Security capabilities that will enable IT to quickly identify risk exposures resulting from unprotected sensitive data, isolated applications with different levels of trust and migrate security policies as data and applications move between different virtual systems and apply the same policies in public clouds.
vCenter Site Recovery Manager 5 Extending this proven disaster recovery solution, vCenter Site Recovery Manager 5 will introduce built-in VMware vSphere replication capabilities that will allow customers to double the number of protected applications for the same cost while supporting heterogeneous storage configurations in the primary and backup sites. New automated failback and planning migration capabilities will allow customers to orchestrate migrations for disaster avoidance and to support planned maintenance activities and data center consolidations.
vCloud Director 5 Enabling a self-service model for provisioning infrastructure services across internal and external sources, VMware vCloud Director 5 will enable IT to dramatically reduce the time required to provision new servers. New Linked Clone capabilities will reduce provisioning time to as few as 5 seconds, while also reducing storage costs by as much as 60 percent, all while managing resources from a single pane of glass. VMware vSphere 5 platform and supporting components. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 24 BMC Atrium Discovery and Dependency Mapping (ADDM) Discover through Integrate phases Discover: Build a complete topology of your applications, software, host infrastructure and network devices and updates the profile as often as you need. Keep pace with changes in dynamic virtual environments from VMware, Sun, Microsoft, HP, and Citrix. Operate agent-free across Windows, Linux, Unix and Netware environments, using standard management protocols, such as SSH, WMI, and SNMP. Deep discovery of J2E applications and data bases (Tables, License options, etc.). Analyze: Automatically group servers that work closely together, based on an analysis of the communications between them. Highlight high-risk servers that touch a large portion of the estate. Exclude hosts from automatic grouping as needed. Manual Grouping: Identify groups of hosts to help manage them through a project. Refine automatic groups based on non-discoverable head-knowledge. Exclude sets of servers from visualization such as super-connected servers with hundreds of dependencies. Application Dependency Mapping: Automatically identify IT components and configurations, and interpret raw, discovered data from individual software processes to large-scale, distributed business applications. Use pre-populated patterns to recognize more than 400 infrastructure software products (with more added monthly). Automatically build visualizations that show configuration dependencies between switches, routers, virtual and physical hosts, software, business applications, and other business entities. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 25 BMC Atrium Discovery and Dependency Mapping Visualize and Integrate Dashboard & Reports: In seconds, create tabular reports and charts that provide answers to critical questions. Leverage pre-populated reports or create your own using the Search Engine Query Language. Organize your favorite charts into at-a-glance dashboards that display the metrics that matter most to you. Search: Perform fast, free text search of the entire data store and get the most relevant results in seconds. Narrow your searches to specific object types and use Search Query Language. Export search results in XML and CSV formats to facilitate information sharing. Host Profiles: View essential details for each host, including and analysis of the hosts network traffic in an accessible, easy-to-use format. Create reports as pdf documents. Email, print, discuss, and annotate, as needed. Integrate Dynamic CMDB: Provides seamless flow of the vital accurate, up to date data needed to underpin BSM initiatives and processes. Continuous CMDB synchronization allows real time up date of the CMDB as Cis are discovered. Filtering allows you to control the Cis types that are synchronized with the CMDB. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 26 CiRBA Overview CiRBA Data Center Intelligence
CiRBA Data Center Intelligence (DCI) is predictive analytics software that powers a revolutionary console for policy-based control of virtual and cloud infrastructure.
The CiRBA Control Console
CiRBA's Control Console gives you unprecedented control over the efficiency and risk of virtual and cloud infrastructure by optimizing resource allocations and workload placements. This revolutionary console shows you in a single glance which resources need attention and also provides the explicit actions required for optimization. Imagine knowing that you have the perfect amount of infrastructure to satisfy SLA and policy requirements, without having too much. And that your workloads are optimally placed and configured. This is the power of CiRBA Data Center Intelligence (DCI).
CiRBA's Control Console enables you to:
1. Visualize - In a single glance, see which resources are appropriately placed, provisioned, and configured and which are at risk.
2. Control - Precise actions are derived from policies and operational data to provide IT with unprecedented control over virtual and cloud infrastructure.
3. Automate - Integrate DCI-Control with existing management systems to safely automate actions that improve efficiency and reduce risk. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 27 Wireshark Network Analyzer Wireshark is the world's foremost network protocol analyzer. It lets you capture and interactively browse the traffic running on a computer network. It is the de facto (and often de jure) standard across many industries and educational institutions.
Wireshark development thrives thanks to the contributions of networking experts across the globe. It is the continuation of a project that started in 1998. (see www.wireshark.org for in-depth information and free download). Wireshark features include:
Deep inspection of hundreds of protocols, with more being added all the time Live capture and offline analysis Standard three-pane packet browser Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility The most powerful display filters in the industry Rich VoIP analysis Read/write many different capture file formats: tcpdump (libpcap), Pcap NG, Catapult DCT2000, Cisco Secure IDS iplog, Microsoft Network Monitor, Network General Sniffer (compressed and uncompressed), Sniffer Pro, and NetXray, Network Instruments Observer, NetScreen snoop, Novell LANalyzer, RADCOM WAN/LAN Analyzer, Shomiti/Finisar Surveyor, Tektronix K12xx, Visual Networks Visual UpTime, WildPackets EtherPeek/TokenPeek/AiroPeek, and many others Capture files compressed with gzip can be decompressed on the fly Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platform) Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2 Coloring rules can be applied to the packet list for quick, intuitive analysis Output can be exported to XML, PostScript, CSV, or plain text Wireshark enables capturing and playback of transactions and network activity to benchmark / test migrated applications. Wireshark can be used to test Business Recovery Applications at the remote site to insure they work properly and within Service Level Agreement guidelines. Wireshark is a free product that can be downloaded and activated within minutes. It is an Open-Source product that can be tailored to the specific needs of your organization. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 28 Automated Tools (ITIL v3) Information Technology Information Library version 3 for Forms Management and Control to support work flow and improve productivity. AIX Unix based operating system with GUI front ends and many tools to support present and future computing needs. System Z x86, Hx5 Blades, MF / Server, Scalable, Load Balancing, manage Virtual / Real computing System P Server Manager with Power Saving features IBM System P7 (Power 7) Watson computer used for Jeopardy and is extremely Scalable, Efficient and Powerful zOS MF, Server, Problem Management (Detect, Solve, Forward to Resolver, Analysis / Reporting) with extreme security Tivoli Omegamon XE, Storage Management, Tape System Optimization DS8000 Solid State to Disk Level to support priority processing, High I/O rate, Power Regulation controller DS4000 Fabric Storage Management, RAID Configuration, Configure Storage Arrays, Enclosure Drive Protection TS3500 Automated Tape / Cartridge Management System from picker to machine delivery and back Double-Take from Vision Systems and includes: Recover Now, Share, and Move modules that support: Recovery Point Objective (RPO) and Data Synchronization in virtual and real environments. Ensures aggressive Business Continuity Management over the environment and its data. Rewind Data for Continuous Data Protection, Roll-Back to Recovery Point, and Roll-Forward to pick-up point. Availability for Load Balancing, Transparent Recovery via Shut-Down, Move, Reconnect, and Restart operations. The Use of these tools and the others mentioned in this presentation can support automated and incremental recovery operations for organizations of all sizes and we recommend you research their use for your company. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 29 ITIL V3 Overview 3. Service Transition Change Management Project Management (Transition Planning and Support) Release and Deployment Management Service Validation and Testing Application Development and Customization Service Asset and Configuration Management Knowledge Management
4. Service Operation Event Management (Crisis) Incident Management (Incidents) Request Fulfillment (Enhancements) Access Management (Security Physical / Data) Problem Management IT Operations Management (SDLC, Support, etc.) Facilities Management 1. Service Strategy Service Portfolio Management Financial Management
2. Service Design Service Catalogue Management Service Level Management (SLA / PKI) Risk Management Capacity Management Availability Management IT Service Continuity Management (BCM) Information Security Management (ISMS) Compliance Management (Regulatory) Architecture Management Supplier Management (Supply Chain) ITIL Available Modules ITIL Five Phase approach to IT Service Support
1. Service Strategy, 2. Service Design, 3. Service Transition, 4. Service Operation, and 5. Continual Service Improvement. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 30 Information Technology Infrastructure Library (ITIL) IBM System Z overview Built on a scalable, secure, reliable, simplified and cost-efficient infrastructure IBM System z is the ideal platform for meeting your Business Analytics needs for today while minimizing the costs of Business Analytics tomorrow. The server platform allows you to implement a single Business Analytics standard while providing Business Analytics as a service to your organization, for better corporate compliance and greater optimization.
Provide all decision-makers with complete, consistent, timely and relevant information Easily scale to meet the needs of every decision-maker, from executives and line-of-business managers, financial and business analysts, to front line managers, partners and customers. Offer a complete portfolio of business analytics on a single platform to meet business needs. Provide a more complete view of the business with greater access to real-time data.
Increase user satisfaction and ROI Obtain guaranteed system performance and availability (an enterprise SLA). Provide faster time to value for the business. Enable business units to shift their focus from administrative tasks to decision-making.
Reduce the cost and complexity of providing Business Analytics to your organization Centralize resources and reduce the hardware, software and facilities (power, floor space, etc.) required to manage and maintain the Business Analytics infrastructure. Significantly reduce the costs associated with Business Analytics system administration and facilities by upwards of 50% over 5 years. Realize greater economies of scale, enabling IT to deliver Business Information (BI) to a broader audience at a reduced cost. Make the high availability of your Business Analytics infrastructure a viable option for IT.
Make Business Analytics deployment easier Deploy in days/weeks on System Z instead of months. Reduce the time, resources and cost of delivering BI to new divisions, departments and users. Automate and facilitate self-service provisioning. Eliminate the cost-related barriers to introducing BI to new divisions/departments.
Simplify enforcement of corporate regulations and standards Ensure corporate security policies are followed. Ensure disaster recovery plans are in place. Maintain control over business processes. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 31 IBM System P overview History
It was originally a line of workstations and servers called RS/6000, but the server line was then renamed to the eServer pSeries in 2000 as part of its e-Server branding initiative. With the advent of the POWER5 processor in 2004 the family was rebranded the eServer p5. With the global move of the server and storage brands to the System brand with the Systems Agenda, the family was renamed yet again to System p5 in 2005. The System p5 now encompasses the IBM OpenPower product line. With the introduction of POWER6 processor models the new models are now being released under the System p brand, dropping the p5 designation.
Processors
Where RS/6000 used a mix of early POWER and PowerPC processors, when pSeries came along this had evolved into RS64-III and POWER3 across the board. POWER3 for its excellent floating point performance and RS64 for its scalability, throughput and integer performance. IBM developed the POWER4 processor to replace both POWER3 and the RS64 line in 2001. After that the differences between throughput and number crunching optimized systems no longer existed. Since then System p machines evolved to use the POWER5 but also PowerPC 970 for the low end and blade systems. The last System p systems used the POWER6 processor, such as the POWER6 based System p 570 and the JS22 blade. In addition IBM introduced during the SuperComputing 2007 (SC07) conference in Reno a new POWER6 based System p 575 with 32 POWER6 cores at 4.7 GHz and up to 256GB of RAM with water cooling.
Features
All IBM System p5 and IBM eServer p5 machines support DLPAR (Dynamic Logical Partitioning) with Virtual I/O and Micro-partitioning. System p generally uses the AIX operating system and, more recently, 64-bit versions of the Linux operating system. Sun Microsystems is also developing an OpenSolaris port, currently experimental.[1] Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 32 IBM System Power 7 (P7) Watson What is the Power7 processor?
The Power7 is the latest generation of IBM processors (chips) that are used as the CPUs in IBM mid range and high end open systems (pSeries) for Unix (AIX) and Linux as well as for the iSeries (aka AS400 successor). Building on previous Power series processors, the Power7 increases the performance per core (CPU) along with the number of cores per socket (chip) footprint. For example, each Power7 chip that plugs into a socket on a processor card in a server can have up to 8 cores or CPUs. Note that sometimes cores are also known as micro CPUs as well as virtual CPUs not to be confused with their presented via Hypervisor abstraction.
Sometimes you may also hear the term or phrase 2 way, 4 way (not to be confused with a Cincinnati style 4 way chili) or 8 way among others that refers to the number of cores on a chip. Hence, a dual 2 way would be a pair of processor chips each with 2 cores while a quad 8 way would be 4 processors chips each with 8 cores and so on.
IBM Power7 with up to eight cores per processor (chip)
In addition to faster and more cores in a denser footprint, there are also energy efficiency enhancements including Energy Star for enterprise servers qualification along with intelligent power management (IPM also see here) implementation. IPM is implanted in what IBM refers to as Intelligent Energy technology for turning on or off various parts of the system along with varying processor clock speeds. The benefit is when there is work to be done, get it down quickly or if there is less work, turn some cores off or slow clock speed down. This is similar to what other industry leaders including Intel have deployed with their Nehalem series of processors that also support IPM.
Additional features of the Power7 include (varies by system solutions):
Energy Star for server qualified providing enhanced performance and efficiency. IBM Systems Director Express, Standard and Enterprise Editions for simplified management including virtualization capabilities across pools of Power servers as a single entity. PowerVM (Hypervisor) virtualization for AIX, iSeries and Linux operating systems. ActiveMemory enables effective memory capacity to be larger than physical memory, similar to how virtual memory works within many operating systems. The benefit is to enable a partition to have access to more memory which is important for virtual machines along with the ability to support more partitions in a given physical memory footprint. TurboCore and Intelligent Threads enable workload optimization by selecting the applicable mode for the work to be done. For example, single thread per core along with simultaneous threads (2 or 4) modes per core. The trade off is to have more threads per core for concurrent processing, or, fewer threads to boost single stream performance. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 33 IBM zOS System Overview Major characteristics
z/OS supports stable mainframe systems and standards such as CICS, IMS, DB2, RACF, SNA, WebSphere MQ, record-oriented data access methods, REXX, CLIST, SMP/E, JCL, TSO/E, and ISPF, among others. However, z/OS also supports 64-bit Java, C/C++, and UNIX (Single UNIX Specification) APIs and applications through UNIX System Services.
The Open Group certifies z/OS as a compliant UNIX operating system with UNIX/Linux-style hierarchical HFS
and zFS file systems As a result, z/OS hosts a broad range of commercial and open source software of any vintage.
z/OS can communicate directly via TCP/IP, including IPv6, and includes standard HTTP servers (one from Lotus, the other Apache - derived) along with other common services such as FTP, NFS, and CIFS/SMB. Another central design philosophy is support for extremely high quality of service (QoS), even within a single operating system instance, although z/OS has built-in support for Parallel Sysplex clustering.
z/OS has a unique Workload Manager (WLM) and dispatcher which automatically manages numerous concurrently hosted units of work running in separate key-protected address spaces according to dynamically adjustable business goals. This capability inherently supports multi-tenancy within a single operating system image. However, modern IBM mainframes also offer two additional levels of virtualization: LPARs and (optionally) z/VM. These new functions within the hardware, z/OS, and z/VM and Linux and OpenSolaris support have encouraged development of new applications for mainframes. Many of them utilize the WebSphere Application Server for z/OS middleware. Because there is only one z/OS version (at least at present), releases are normally called "Release n," though more formally they are "Version 1 Release n" or "V1.n". The IBM Program Number for all z/OS Version 1 releases is 5694-A01.
From its inception z/OS has supported tri-modal addressing (24-bit, 31-bit, and 64-bit). Up through Version 1.5, z/OS itself could start in either 31-bit ESA/390 or 64-bit z/Architecture mode, so it could function on older hardware albeit without 64-bit application support on those machines. (Only the newer z/Architecture hardware manufactured starting in the year 2000 can run 64-bit code.) IBM support for z/OS 1.5 ended on March 31, 2007. Now z/OS is only supported on z/Architecture mainframes and only runs in 64-bit mode. z/Architecture hardware always starts running in 31-bit mode, but current z/OS releases quickly switch to 64-bit mode and will not run on hardware that does not support 64-bit mode. Application programmers can still use any addressing mode: all applications, regardless of their addressing mode(s), can coexist without modification, and IBM maintains an unwavering commitment to tri-modal backward compatibility. However, increasing numbers of middleware products and applications, such as DB2 Version 8 and above, now require and exploit 64-bit addressing.
IBM markets z/OS as a flagship operating system, suited for continuous, high-volume operation with high security and stability. It is the most popular mainframe operating system. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 34 IBM zOS System Overview (continued) z/OS introduced Variable Workload License Charges (VWLC) and Entry Workload License Charges (EWLC) which are sub-capacity billing options. VWLC and EWLC customers only pay for peak monthly z/OS usage, not for full machine capacity as with the previous OS/390 operating system. VWLC and EWLC are also available for most IBM software products running on z/OS, and their peaks are separately calculated but can never exceed the z/OS peak. To be eligible for sub-capacity licensing, a z/OS customer must be running in 64-bit mode (which requires z/Architecture hardware), must have completely eliminated OS/390 from the system, and must e-mail IBM monthly sub- capacity reports. Sub-capacity billing substantially reduces software charges for most IBM mainframe customers. Advanced Workload License Charges (AWLC) is the successor to VWLC on mainframe models starting with the zEnterprise 196 and EAWLC is an option on zEnterprise 114 models. AWLC and EAWLC offer further sub-capacity discounts.
The primary development center for z/OS is located at IBM's facilities in Poughkeepsie, New York, but numerous development centers in several other countries contribute substantially to z/OS. As one example, IBM's center in Perth, Australia is mainly responsible for z/OS's HLASM and DFSMS components.
64-bit memory support
Within each address space, z/OS typically only permits the placement of data above the 2GB "bar," not code. z/OS enforces this distinction primarily for performance reasons. There are no architectural impediments to allowing more than 2GB of application code per address space. IBM has started to allow Java code running on z/OS to execute above the 2GB bar, again for performance reasons. Memory is obtained as "Large Memory Objects" in multiples of 1MB (with the expectation that applications and middleware will manage memory allocation within these large pieces). There are three types of large memory objects: Unshared - where only the creating address space can access the memory. Shared - where the creating address space can give access to specific other address spaces. Common - where all address spaces can access the memory. (This type was introduced in z/OS Release 10.)
Extreme security - In 1973, IBM published a unique "Statement of Integrity" for MVS which has been updated for z/OS and is still in force. z/OS is available under standard license pricing as well as via System z New Application License Charges (zNALC) and "System z Solution Edition," two lower priced offerings aimed at supporting newer applications ("new workloads"), U.S. standard commercial z/OS pricing starts at about $125 per month, including support, for the smallest zNALC installation running the base z/OS product plus a typical set of optional z/OS features. [
Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 35 IBM Tivoli System Overview Why Tivoli software A holistic approach to delivering and managing infrastructure services aligned to evolving business priorities.
What Tivoli offers
Visibility Control Automation An Integrated Service Delivery & Management platform optimized for:
Asset and Facilities Management Improve efficiency and reduce the cost and risk of your assets, from medical devices to buildings.
Business Service Management Improve customer satisfaction with increased availability of critical business services.
Cloud and IT Transformation Lower the cost of your IT infrastructure and speed the delivery of innovative products and services.
Data Protection and Storage Management Create a more responsive and resilient storage infrastructure.
Enterprise Mobility Management Manage physical and virtual endpoints in real time and ensure compliance.
Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 36 IBM DS8000 I/O Priority Manager Overview Abstract
The DS8000 I/O Priority Manager enables more effective storage consolidation and performance management combined with the ability to align Quality of Service (QoS) levels to separate workloads in the system.
With DS8000 I/O Priority Manager, the system can prioritize access to system resources to achieve the volume's desired QoS based on defined performance goals (high, medium, or low) of any volume. I/O Priority Manager constantly monitors and balances system resources to help applications meet their performance targets automatically, without operator intervention. Starting with DS8000 Licensed Machine Code (LMC) level R6.2, the DS8000 I/O Priority Manager feature supports open systems and IBM System z.
DS8000 I/O Priority Manager, together with IBM z/OS Workload Manager (WLM), provides more effective storage consolidation and performance management for System z systems. Now tightly integrated with Workload Manager for z/OS, DS8000 I/O Priority Manager improves disk I/O performance for important workloads. It also drives I/O prioritization to the disk system by allowing WLM to give priority to the system's resources automatically when higher priority workloads are not meeting their performance goals. Integration with zWLM is exclusive to DS8000 and System z systems.
This slide is aimed at those who want to get an understanding of the DS8000 I/O Priority Manager concept and its underlying design. It provides guidance and practical illustrations for users who want to exploit the capabilities of the DS8000 I/O Priority Manager. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 37 IBM DS4000 I/O Priority Manager Overview The DS4000 EXP810 is the latest disk drive enclosure in the DS4000 Series of products. This 3U enclosure has 4 Gbps Fibre Channel (FC) interfaces, and supports up to 16 disk drives.
The 4 Gbps ready IBM System Storage EXP810 Storage Expansion Unit machine type (1812-81A) offers a new 16-bay disk enclosure for attachment to selected DS4000 Midrange Disk Systems, with up to 4.8 terabytes (TB) physical capacity per expansion unit using sixteen 300 GB disk drives.
The EXP810 Storage Expansion Unit is designed to accommodate the new optional 2 Gbps Fibre Channel Enhanced Disk Drive Modules (E-DDM), as well as intermix of future optional 4 Gbps Fibre Channel Enhanced Disk Drive Modules (E-DDM), all within the same enclosure. Contains redundant (AC) power and cooling modules, and ESM interfaces. The DS4000 EXP810 is available in a 19- inch rack mount package. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 38 IBM TS3500 Automated Tape Manager Overview Highlights
Supports highly scalable, automated data retention on tape utilizing LTO Ultrium and IBM 3592 and TS1100 families of tape drives.
Delivers extreme scalability and capacity, growing from 1 to 16 frames per library and from one to 15 libraries per library complex using the TS3500 shuttle connector.
Provides up to 900 PB of automated, low-cost storage under a single library image, dramatically improving floor space utilization and reducing storage cost per terabyte.
Offers optional second robotic accessor to enhance data availability and reliability.
Enables data security and regulatory compliance via support for tape drive encryption and WORM cartridges.
The IBM System Storage TS3500 Tape Library is designed to provide a highly scalable, automated tape library for mainframe and open systems backup and archive that can scale from midrange to enterprise environments.
The TS3500 Tape Library continues to lead the industry in tape drive integration with features such as persistent World Wide Name, multipath architecture, drive/media exception reporting, remote drive/media management, and host-based path failover.
The TS3500 Tape Library supports IBM System z when used with the IBM 3953 Tape System, the IBM Virtualization Engine TS7740, or the IBM System Storage Tape Controller for System z with its embedded library manager. These systems enable System z hosts to access the TS3500 Tape Library cartridge inventory and allow connection to TS1140, TS1130, TS1120 and IBM TotalStorage 3592 Model J1A Tape Drives. The TS3500 Tape Library can support up to four 3953 tape systems, up to eight IBM Virtualization Engine TS7740 subsystems per physical library, and up to sixteen IBM System Storage Tape Controllers for System z per logical library. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 39 Double-Take Software Overview Double-Take Availability for AIX
Double-Take for AIX has simplified failover management to meet the most aggressive Recovery Time Objectives, providing high availability for the masses.
Monitoring and automated failover ensures business continuity for customers, partners, and employees.
Failover to local or remote nodes for reliable, affordable offsite data protection.
Protects both physical and virtual AIX environments.
Eliminates the IT costs and business consequences of downtime and data loss.
Removes the exposure to major data loss of conventional backup and restore technologies. Double-Take RecoverNow for AIX
Double-Take RecoverNows replication technology provides superior performance that allows for a high level of system scalability and satisfies aggressive Recovery Time Objectives.
Reliable, affordable offsite data protection. Supports physical and virtual environments. Real time capture of data changes and replication to a recovery system Maintains write order consistency to ensure data integrity for disaster recovery Intelligent and efficient re-sync of production and recovery systems in the event of lost connectivity In the event of a disaster, applications can be immediately restarted on the recovery system Eliminates the IT costs and business consequences of downtime and data loss Ensures business continuity for your customers, partners and employees Removes the exposure to major data loss of conventional backup and restore technologies Storage independence avoids vendor lock-in and maximizes existing storage investments Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 40 Produced by Vision Systems Double-Take Share for AIX:
Real time data replication.
Reliable change data capture ensures data integrity.
Built-in conflict resolution and collision monitoring.
Accurate tracking and data auditing.
Ensures delivery of replicated data even if the target system is unavailable.
LAN/WAN friendly.
Real time, integrated data from divergent sources allows for better informed decision making. Double-Take Software Overview continued Double-Take Move for AIX:
With solutions for Windows, Linux, AIX and IBM I, Vision leads the way in keeping systems and applications resilient and available. Whether you need an easier, more reliable disaster recovery solution, want to manage and share data seamlessly between platforms and databases, need a better way to maintain system efficiency, or you need a comprehensive high availability solution for assured 24/7 operations, Vision Solutions has what youre looking for - including your physical environments, your virtual environments, as well as the cloud. SAN Array-Based Replication and Double-Take Availability.
High Availability Deliver nonstop business continuity and boost productivity. Innovative, easy to use switching and replication solutions eliminate costly IT downtime.
Disaster Recovery Protect critical information and recover lost data in a fraction of the time and effort of traditional tape backup solutions. Affordable, automated solutions deliver the power of continuous data protection and the flexibility of in-house or hosted recovery options.
Data Sharing and Migration Data center consolidation and virtualization initiatives save organizations a great deal of money. Now you can move and share data with unprecedented ease and efficiency. Powerful yet flexible solutions let you unlock the maximum business value of your data. Thomas Bronack - Application Migration Guideline Document Release Date: 8/10/2013 Page: 41 8/10/2013 Thomas Bronack - Application Migration Guideline Document 42 Example Data Center Migration Plan Goals PCL Internap Leased Back-Up Vendor Primary DC Valencia, CA Back-Up DC Seattle, WA CCL HAL Peak 10 Back-Up Vendor Owned Primary DC Seattle, WA Leased Back-Up DC Ft. Lauderdale, FL Back-Up DC Primary DC Miami, FL Legend:
PCL = Valencia, CA Site HAL = Seattle, WA Site CCL = Client Owned Site Internap = WA Back-Up Vendor Peak 10 = Florida Back-Up Vendor DC West CCL Owned Primary DC, Valencia, CA Comprised of HAL, Peak 10, and PCL DC East CCL Owned Primary DC, Miami, FL Comprised of CCL and Internap Internap (Phase I) HAL (Phase II) Peak 10 (Phase III) WAN Current Environment Future Environment Data Centers support production and are back-up to each other, owned by Client Company, and utilize by new products and capacity, as needed. Migrate & Close Migrate & Close 8/10/2013 Thomas Bronack - Application Migration Guideline Document 43 Example Migration Plan Potential Problems Phase I Migrate Internap to DC East Who will back-up PCL? Make sure DC East can back-up PCL before terminating Internap contract. Consider moving PCL to DC West to support PCL production, then test recovery to DC East before migrating Internap backup support to DC East and closing contract with Internap.
Phase II Migrate HAL to DC West HAL back-up is still CCL, now DC West. Who will back-up HAL and CCL during this phase. If Peak 10, then review capacity and contract with Peak 10 to make sure you can support recovery operations; Consider DC East as HAL backup, then test production and recovery for HAL. If production and recovery are successful then close HAL Seattle location and reposition CCL assets (redeployment, upgrade, Termination).
Phase III Migrate Peak 10 to DC West Who will back-up CCL and HAL? Consider DC East for Back-up operations, then test CCL and HAL recovery before closing Peak 10.
After Phase III Preparation for the future DC East supports designated production, while being able to recovery DC West operations. DC West can support designated production, while providing back-up to DC East. Ensure all procedures, documentation, awareness, and training are completed. Ensure adherence to recovery time objectives and compliance laws and regulations. Ensure both sites have sufficient resources to recover the other site and kept in sync. 8/10/2013 Thomas Bronack - Application Migration Guideline Document 44 Example Data Center Migration Plan Concerns Make sure Service and Recovery Protection is maintained at all times; Closing Recovery Sites must come after supplemental protection is achieved; Only Close site after protection is validated. Perform a financial analysis of equipment to select the products that are most economical to retain (i.e., Owned, Leased, Rented, Multiple Software Licenses, or resources no longer needed); Utilize Asset Management to Update, Relocate, or Terminate equipment; Make sure appropriate Insurance is Maintained throughout project and then going forward, so that financial considerations and management protection can be maintained; Ensure Capacity and Performance can be supported at new facilities and that all remote offices can access new data centers through the WAN without loss of transaction speed; Ensure Documentation is complete, in sync, and personnel are trained; Utilize Checkpoints to review progress, fix problems or change direction, and make go / no-go decisions; Integrate procedures within the everyday functions performed by personnel so that all records and procedures are current in adherence to Version and Release Management; Integrate Support and Maintenance procedures for resolving Problems / Incidents and implementing Enhancements going forward; and, Utilize ITIL to support operations and maintain a repository of information. 8/10/2013 Thomas Bronack - Application Migration Guideline Document 45 Example Data Center Migration Approach Establish a Management Reporting Structure and Status Reporting schedule; Identify Stakeholders and participants, formulate teams, train, and create project structure; Perform a Risk Assessment to identify compliance requirements; Conduct a Environmental Analysis to define current environment capacity / performance, SLA / KPI / Contract requirements, gaps & exceptions, and obstacles that prevent achieving project goals; Eliminate compliance gaps & exceptions, while eliminating obstacles preventing project success; Identify and Rate Applications to be migrated, while ensuring their ability to process successfully in both a production and recovery condition; Define IT Security, encryption, real-time / incremental back-up and recovery requirements, failover / failback for High Availability (HA) applications, Flip / Flop for Continuous Availability (CA) applications; Creation of an Applications Migration Project Plan with tasks to be performed, subject matter experts, deliverable time schedule, resource requirements, tasks to be performed, and costs; Determine if Cloud Computing and Virtualization should be incorporated into new system design; Identify target environment and automated tools needed to help achieve project goals; Define an Organization Structure for application migration, data center decommission, and testing of production and recovery procedures; Formulate Migration Path to move applications from existing data center to target data center, with personnel functional responsibilities, job descriptions, standards and procedures, and training to all personnel assigned to this project; Integrate Enterprise Resiliency and Corporate Certification when migrating applications to new site; Implement Migration Factory and other functional areas needed to perform migration duties; Benchmark applications and systems at primary site and target site, reporting results to management; and, Implement SDLC, Systems Management, Version and Release Management, and ITIL to support and maintain production operations going forward. Integrate within everyday functions to insure currency. 8/10/2013 Thomas Bronack - Application Migration Guideline Document 46 Example Data Center Migration Benefits Creation of Client Owned facilities to support domestic production operation, while having the ability to support recovery operations in a reciprocal manner in accordance to SLA (Service Level Agreement) and PKI (Performance Key Indicators) recovery time objectives; Elimination of Leased Facilities (PCL and HAL); Eliminate of Back-Up Vendor costs (Internap and Peak 10); Better controls over IT Operations because procedures can be tailored to Client, without having to consider leased and recovery obstacles; Implementation of Recovery Plans to protect locations, personnel, clients, and reputation; Elimination of redundant operations and procedures; Reduction is staff; Platform for Virtualization going forward; Ability to implement State-of-the-Art WAN (Wide Area Network) to support current and future communications requirements; Ability to implement State-of-the-Art Data Protection and Recovery operations through Data De-Duplication (Dedupe), Virtual Tape Library (VTL), Snapshots, Continuous Data Protection, and Automated Recovery tools; Ability to implement Continuous Availability (CA) and High Availability (HA) procedures to protect applications and business operations in accordance to contractual and regulatory requirements; and, A better trained staff will improve satisfaction and loyalty, while enhancing the companys reputation with personnel and clients.