unmatched migration a nonstop success story
play

Unmatched Migration a NonStop success story 01.05.2018, HANS-JRG - PowerPoint PPT Presentation

Unmatched Migration a NonStop success story 01.05.2018, HANS-JRG RICHTER/ IT-OPERATIONS agenda Introduction Motivation Migration Concept Go Live and Results Challenges 1 Introduction Ingenico Group in figures 6,000


  1. Unmatched Migration – a NonStop success story 01.05.2018, HANS-JÖRG RICHTER/ IT-OPERATIONS

  2. agenda  Introduction  Motivation  Migration Concept  Go Live and Results  Challenges

  3. 1 Introduction

  4. Ingenico Group in figures 6,000 88 EMPLOYEES, LOCATIONS 74 NATIONALITIES 170 > €2 billion COUNTRIES WITH TURNOVER INGENICO HAS DOUBLED IN 4 YEARS REPRESENTATION 300+ 1,000+ PARTNER BANKS PAYMENT AND PROCEDURES ACQUIRERS 4 Unmatched Migration - a NonStop success story * 01/05/2018

  5. Your partner for successful trade: stationary, online or mobile Our comprehensive range of Ingenico Payment Services Ingenico ePayments – terminals , together with our believes in unlimited payment scalable solutions for partnership agreements, solutions. Our strong position successful online allows Ingenico Smart in Europe is the basis for our business. With only one Terminals to offer you over interface, you can gain global service portfolio. 250 payment methods . access to more than 200 acceptance partners and 150 payment methods . 5 Unmatched Migration - a NonStop success story * 01/05/2018

  6. Ingenico Payment Services in figures 95,000 583 CUSTOMERS IN GERMANY EMPLOYEES IN GERMANY 160,000 CUSTOMERS 1,000 EMPLOYEES THROUGHOUT EUROPE THROUGHOUT EUROPE 2.04 billion € 70 billion TRANSACTIONS PER YEAR VOLUME OF PROCESSED IN GERMANY PAYMENT TRANSACTIONS IN GERMANY 288,000 TERMINALS AND CHECKOUT SOLUTIONS BEING USED IN GERMANY 6 Unmatched Migration - a NonStop success story * 01/05/2018

  7. Our clients Below are some of the top companies, from a wide range of business sectors, who are long-standing customers of ours : 7 Unmatched Migration - a NonStop success story * 01/05/2018

  8. 2 Motivation Why we started thinking about a technical update

  9. Fact 1 • Replacement of high availability infrastructure every five years • Test machine needs to be replaced (EoS 01.08.2017) • Renewal of contracts for support and licenses NB54000c NB54000c NS2000 Purchase in 04/2012 Purchase in 04/2012 Purchase in 07/2009 Supported until at least Supported until at least Supported until 08/2017 02/2019 02/2019 9 Unmatched Migration - a NonStop success story * 01/05/2018

  10. Batch utilization: OLTP ultilization (Peak day): Fact 2 Average ~ 63% Average ~ 35% Peak > 70% Peak ~ 43% • Rematch the scaling of the production system to the daily use • Strategic decision to move epayments to an other ingenico entity CPU load 23.12.2015 50 45 40 35 30 25 20 15 10 5 0 00:00 00:30 01:00 01:30 02:00 02:30 03:00 03:30 04:00 04:30 05:00 05:30 06:00 06:30 07:00 07:30 08:00 08:30 09:00 09:30 10:00 10:30 11:00 11:30 12:00 12:30 13:00 13:30 14:00 14:30 15:00 15:30 16:00 16:30 17:00 17:30 18:00 18:30 19:00 19:30 20:00 20:30 21:00 21:30 22:00 22:30 23:00 23:30 CPU-00 CPU-01 CPU-02 CPU-03 CPU-04 CPU-05 10 Unmatched Migration - a NonStop success story * 01/05/2018

  11. 3 Migration Concept Scenarios, criterias and POC

  12. NonStop future Scenarios for IPS Decision • Scenario 2: switch to NonStop X • Scenario 1: continuation of NonStop i  Change nothing until EoS (01.02.2019) for production  Replace all systems with new technology (primary, backup, test)  Replace the testsystem (investment for just two years) Size matters • HPE only provides performance figures for the cpu • Scenario 2: switch to NonStop X • IPS wants to reduce size of NonStop  Replace all systems with new technology (primary, backup, test)  Need to do Proof of Concept on a production node 12 Unmatched Migration - a NonStop success story * 01/05/2018

  13. Nonstop X for IPS NonStop i NonStop X EC1 IX1 Reduced performance (~ -15 % ) NB54000 NS7 X2 Increased memory 6 Blades 4 Blades quad-core dual-core Increased disc capacity NB54000 NS7-4b2c Increased the usage of SSD Increased comms throughput (IP CLIM) 13 Unmatched Migration - a NonStop success story * 01/05/2018

  14. PoC Criteria specification Required value Measured value Passed 1) Poseidon OLTP Ingenico expects to receive a Ingenico will adjust the configuration of NonStop X Poseidon release the application and database to the their SW Vendor WL. Their reduced NonStop X configuration of expectation is that release will 4CPU/2core and 25 disk volumes. be compiled and ready for all _ _ areas (Online and Batch). It is Ingenico´s responsibility to have the Poseidon release for NonStop L16.05 available for the PoC. Transaction Response Times: 2) Transaction With support of the PDIAG response time of with 650 to 700 -TRX volume of 300 to 400 TPS (measure the Throuhoutput solution, Ingenico will simulate the NonStop X TPS response times) several different OLTP should be better the response - Overall response times should be same range scenarios with various than NonStop i time averages: or better as on current system transactions types. It is the NonStop i 22ms responsibility of Ingenico to NonStop X 9ms provide and setup the PDIAG Volume Test: CPU Busy < 80% max. 1.147 environment. - Use of reduced TRX set TRX/sec - Achieve 1.200 TPS (TRX per sec.) with CPU avg. CPU Busy Busy Rate (not more than 80%) 40% no messages from _ - Poseidon Quene Manager should not the queue manager report significant bottlneck warnings for process increased numner of TRX time outs 14 Unmatched Migration - a NonStop success story * 01/05/2018

  15. PoC Criteria specification Required value Measured value Passed Comparison between current system and 3) Batch Clearing processing needs to PoC system, using: Processing – be finished within certain Day End period (depending on - CPU Busy during execution time see graphic - Processing “Kassenschluss” and “Batch Windows of the Bank”). - Disk I/O Disk Queue < 1 - Complete data set will be loaded onto PoC system to run - TMF TPS no error msg - test scenario. Ingencio will collect for one or more days - Runtime of ZVMAIN processes (part of see graphic - from the current production Poseidon application) environment. - Runtime of all post processing processes see graphic - (KUMUL,SPLIT) - Response time is < 80ms < 80ms 700 TRX/sec 4) Risikoindex / Ingenico´s risk application no time outs OLV “Risikoindex” is involved in each OLV OLTP TRX to detect - Timeout-Quote should not exceed an fraud. average of 1% over a full day < 1% 0% 15 Unmatched Migration - a NonStop success story * 01/05/2018

  16. 4 Going Live

  17. Go live Go LIVE Jul 09 Installation Testsystem Order PoC Sep 01 Feb 24 Installation 2 nd Production System Order Installation PoC April 06 PoC -> PRD NonStop X Oct 14 DR Scenario Dec Mar 31 Aug 20 2016 2017 Nov Dec Jan Mar Jul Aug Oct Feb Apr May Jun Prepare PoC Oct 15 – Nov 01 Nov 01 – Jan 13 PoC Jan 13 – May 01 Regression Test Apr 01 – Jun 20 Performance Test Jun 12 – Jul 09 Data Synchronization 17 Unmatched Migration - a NonStop success story * 01/05/2018

  18. Going live Data Replication to three systems NonStop i Shutdown of all applications Stop of RDF EC1 EC1 EC2 Start of all applications Start of RDF with Data Replication to NonStop i for possible fallback IX1 IX2 IX2 NonStop X 18 Unmatched Migration - a NonStop success story * 01/05/2018

  19. results • Reduce operational costs • Except ISV´s NonStop i NonStop X factor • Faster batch execution time Response time (650TPS) 22ms 9ms - Batch time 04:10:21 h 01:25:49 h 2,91 • Faster response time (example 1, high cpu activity) • Jobs with big I/O are very fast Batch time 0:58:18 h 00:07:57 h 7,33 (example 2, high disk acitivity) • Capacity for future growth 19 Unmatched Migration - a NonStop success story * 01/05/2018

  20. 4 challenges

  21. Synchronisation of data (RDF) Reduction of Volumes Complete new IP Infrastructure No more X.25 (SWANS) 21 Unmatched Migration - a NonStop success story * 01/05/2018

  22. RDF Less volumes means more configuration for replication There are some restrictions in RDF • File replications only with in/excludes possible • Source volume can only be used once in a configuration • Target volume can only be used once in a configuration Target 1 Source File A File A File B Target 1 Three different RDF instances File C File B Target 1 File C 22 Unmatched Migration - a NonStop success story * 01/05/2018

Recommend


More recommend