Data center & ERP (SAP/HANA) modernization
Updated on
Modernizing a data center or migrating SAP to HANA without downtime depends on three things: a redundant architecture, a migration plan with tested windows and rollback, and clear RPO and RTO targets. I worked as strategic infrastructure consultant on the CCPR/Itambé spin-off, with two active-active data centers and zero RPO and RTO. Before that, as Servers Sales Manager Sr. at IBM, I worked on projects at FCA and ArcelorMittal.
The problem
The ERP and the servers that run billing have aged. The support contract is ending, performance has dropped or SAP must move to HANA. At the same time, any downtime costs sales, production or service. The project stalls because nobody wants to own the risk.
Signs it is time to modernize
- Equipment out of, or close to the end of, vendor support.
- Maintenance windows that grow longer and harder to negotiate.
- Slow month-end close or overnight processing.
- A vendor deadline to move SAP to HANA.
- No recent disaster recovery test.
- RPO and RTO never agreed with management.
How I work
1. Assessment
I map the inventory, system dependencies, the criticality of each system and acceptable downtime limits.
You get: a map of the environment and RPO and RTO targets agreed with the business.
2. Architecture and plan
I define the platform, the redundancy model (active-active, active-passive or cloud), the migration sequence and the rollback plan.
You get: the technical design, budget and a schedule with change windows.
3. Migration
I run the rehearsals, the migration and the validation with key users, coordinating vendors and the internal team.
You get: follow-up at every step and go/no-go decisions based on data.
4. Stabilization
I follow the first operating cycles, tune performance and document the environment.
You get: a stable, documented environment handed over to operations.
Proof
- CCPR/Itambé: IT spin-off with two in-house data centers running active-active, migration of IT services and SAP to HANA. BRL 27 million budget, zero RPO and RTO, no operational downtime (Sep 2019 – Jul 2020). → Read the case study
- FCA (Fiat Chrysler): the world’s first IBM Power8 platform for SAP HANA, integrating Brazil, the US and Italy. → Read the case study
- ArcelorMittal (Luxembourg): SAP HANA (CO module) upgrade at headquarters, without downtime.
- Unimed-BH: server and storage tech refresh for the hospital environment and the MV ERP.
Frequently asked questions
What should we plan before migrating to SAP HANA?
The inventory of systems and integrations, the target platform, RPO and RTO targets, the downtime windows the business accepts, migration rehearsals and a tested rollback plan. Without these, go-live day becomes a bet.
What are RPO and RTO?
RPO (Recovery Point Objective) is how much data the company can afford to lose in a failure, measured in time. RTO (Recovery Time Objective) is how long it can afford to be down. Zero RPO and RTO mean losing no data and never stopping, which requires full redundancy, such as two data centers running active-active.
What is an active-active data center?
Two data centers running at the same time, each able to take over the other’s load. If one fails, the other carries on without interruption. This architecture is what delivered zero RPO and RTO in the CCPR spin-off.
Let’s talk about your case
Tell me in a few lines what is happening or what you are planning. I reply personally.
Prefer email? james.eustachio@gmail.com · Contact form