Xylos-Farys case: Farys invests in SAP HANA
Inge Opreel
Koen Somers
Introducing Farys/TMVW:• Who is Farys?
• Farys/TMVW business transformation over the years
• Why migrating to S/4 HANA
SAP HANA infrastructure based on HP hardware:• SAP HANA?
• SAP HANA TDI versus appliance model
• HP building blocks of the new “shared environment”
Migration to the new platform:• Implementation timing
• SAP benefits after first migrations and roadmap
• Non-SAP workload benefits on the new “shared platform”
Lessons learned and conclusion
Q&A
Agenda
Who is FARYS?
FARYS delivers products and services to about
650 000 customers in
Flanders
Headquarters are located in Gentand 750 employees
About FARYS/TMVW
Area
Multi Service Company
5 distinct business units:■ Drinkingwaterproduction, -delivery and -sales
■ Services in the public domain
■ SportInfraservices
■ Purchase- and servicecentre
■ AquaDomo and RENI
FARYS/TMVW Business Transformation over the yearsIncreasing Business and IT complexity
PPM
BW/BO/BPC
Mobile (SAP Workmanager)
SAP ERP
ISU
NewGLMigration
Lumira
CRM Service Desk
Orderplatform
SMP 3
Business and IT complexity
2002 2005 2010 2011/12 2015 Q1
Insourcing customer services & billing
Business expansion: Legal, Financial & Stakeholder Reporting
Enterprise portfolio management
Further business expansion& Growth
2015 Q2/Q3
Growth drinkingwater
AquaDOMO & Sewage
Sports Infrastructure Services
Purchase & Service Center
FARYS/TMVW Business Transformation over the years 2015 – Today’s Challenges and the Current Reality
TMVW transforms to FARYS with a more complex structure due to:
• Shared-services organization, complex business partnerships
• Market regularizations
IWVB
IMWV
TMVW
FARYS
IMWV
TMVW
SOLAR
TMVSTMVR
IWVB
…
ORIGIN
DESTIN
ATIO
N
TMVW transforms from a ONE company code organization to a MULTI company organization with FARYS
FARYS/TMVW set up a roadmap for the future
FARYS transformation & further growth
Added value of S/4HANA & Simple Finance (POC)
Sequence (before, during or after the transformation)
FARYS
…<<<< FARYS
transformation
SAP Roadmap for
S/4 HANA
S/4 HANA & Simple Finance
&
WHY migrating to SAP S/4 HANA?
• Investment in hardware (replacement)
• Futureproof SAP-platform
• Faster and realtime reporting
• Solid base for user interface (FIORI apps)
• BW-model and loads are easier and can be combined with realtime data
• Intuitive and performant developments
Introducing Farys/TMVW:• Who is Farys?
• Farys/TMVW business transformation over the years
• Why migrating to S/4 HANA
SAP HANA infrastructure based on HP hardware:• SAP HANA?
• SAP HANA TDI versus appliance model
• HP building blocks of the new “shared environment”
Agenda
SAP HANA FAQ?
What is SAP HANA?
SAP HANA is an in-memory database and application platform, which is for many operations 10-1000x faster than a regular database. HANA, places data to be processed in RAM instead of reading it off disks, adding a performance boost.
Is SAP just a Database?
SAP HANA contains – out of the box – the building blocks for entire enterprise applications. HANA includes transactional databases, reporting databases, integration layers, search, predictive and web. All of this is served up working out the box, with a single installation.
What makes SAP HANA different?
SAP HANA is different by design. It stores all data in-memory, in columnar format and compressed. This can reduce the database footprint by 95%. Everything is calculated on-demand, on the fly, in main memory.
Is SAP HANA disaster tolerant?
Yes it is. HANA writes savepoints to disk at frequent intervals, which contain a snapshot of what is in memory. In-between savepoints, HANA saves a log of each database change to a fast flash disk.
SAP HANA TDI versus appliance modelAppliance model pros and cons
All-in one box approach:
• Standardized and highly optimized• Preconfigured hardware set-up and preinstalled
software package• Fully supported by SAP• SAP HANA, software and hardware support are
fully covered by 1 vendor (for example HPe)
SAP HANA TDI versus appliance modelSAP HANA Tailored Data Center Integration
SAP HANA TDI integration offers more flexibility when you have to select the appropriate hardware for integrating SAP HANA in your data center.
SAP HANA TDI versus appliance modelSAP HANA Tailored Data Center Integration
Farys decided using the TDI approach:
• Flexibility of the new SAP HANA platform is key• Right time replacing the existing EVA based hardware platform for
all other workloads• Central storage instead of distributed systems for all workloads • Reuse of existing IT infrastructure, including straightforward
integration
HP building blocks of the new “shared environment”
SAP HANA
HYPER-V
SHAREPOINT
VMWARE
HP building blocks of the new “shared environment”Situation before migration
FARYS LAN
Storage Area Network
HP Continuous Access
HP
DA
TA P
RO
TECTO
R
HP P6000 HP EVA4400 HP EVA4400HP P6000
HP C7000 with HP Blade servers
HP C7000 with HP Blade servers
HP FLEX-10 for C-class HP FLEX-10 for C-class
HP 8/24c for C-class HP 8/24c for C-class
EMLe tape library
MSL tape library
HP building blocks of the new “shared environment”HP 3PAR StoreServ
When Value MattersStarting at $25K
7200c
When Performance Matters
Up to 900K IOPS @ 0.7ms latency
When Scale MattersUp to 3.2 PB
7400c
7450c
All-Flash Array
7200c All-Flash
Starter Kit
7440c
Polymorphic Simplicity
ONE Architecture
• ONE Operating System
• ONE Interface
• ONE Feature Set
New
HP building blocks of the new “shared environment”HP 3PAR StoreServ
HP building blocks of the new “shared environment”HP 3PAR StoreServ
HP building blocks of the new “shared environment”HP 3PAR StoreServ
NON-SAP HANA Workload Volumes
Tier 0
Tier 1
Tier 2
3PAR Dynamic
Optimization
3PAR Adaptive
Optimization
- Region = 128MB
Sub-LUN Block Movements between Tiers
based on automatic Policies
Manual LUN Movement
between Tiers
CPG 1
CPG 2
CPG 3
CPG A
CPG B
CPG C
SAP HANA VOL
HP building blocks of the new “shared environment”HP StoreOnce
Backup issues:
• Backup windows become a problem (backups take too long)• Mechanical issues with tape drives causes backup failures impact on number of successful backups• High number of tapes needed and manual intervention
There has to be a better way!There is…. HP StoreOnce with inline Deduplication
HP building blocks of the new “shared environment”HP StoreOnce
HP StoreOnce – anyway, anyplace, any scale
StoreOnce in
HP Data Protector
4500 Series
6500 Series
5.5TB usableScalable to
124TB usable
Scalable to
160TB usable
VSA Series 2700 Series
4700Series
4900Series
Scalable to
432TB usable
ONE ArchitectureFrom Small Sites to Enterprise
Backup and Replicate anywhere
Software, Virtual and Hardware Appliances
StoreOnce CatalystBackup App & Source Dedupe
Scalable to
1.7PB usable
HP building blocks of the new “shared environment”HP StoreOnce
• Compares blocks of data being written to the backup device with data blocks previously stored.
• If duplicate data is found, a pointer is established to the original data.
• This removes, or “deduplicates,” the redundant blocks.
• For normal business data sets, a deduplication ratio of 20:1 might be expected after a period of > 3 months:
HP StoreOnce cleverly eliminates duplicate data to reduce the amount of backup data to be stored on disk by typically up to 20x
Backup 1
Backup 2
Backup 3
Backup 4
Unique blocksStored on D2D
HP building blocks of the new “shared environment”HP StoreOnce Catalyst
What’s the HP StoreOnce Catalyst?
Provides a new type of shared backup target – optimized for deduplication appliances –
over Ethernet and FC.
Provides information to backup app about status of backup jobs and subsequent copies
on appliances.
Allows some of dedupe processing (chunking and hashing) to be carried out on the
“source-side” (media server or client server) while rest of processing (match and store) is
done by appliance.
Allows us to replicate data within the backup app without “Re-hydrating” the data. (Low
bandwidth replication).
HP building blocks of the new “shared environment”HP Proliant DL580
1 or 2TB RAM
4x 15core CPUE7-4880V2
4x 1GbE8x 10GbE2x 16Gb FC
HP building blocks of the new “shared environment”New situation
SAP HANA Replication and Backup LAN
FARYS LAN
HP
DA
TA P
RO
TECTO
R
HP StoreOnce 4700
HP Service Guard
HP Service Guard
Storage Area Network
MSL StoreEver MSL6480
DL580 Gen82TB RAM
DL580 Gen81TB RAM
DL580 Gen82TB RAM
DL580 Gen81TB RAM
HP 3PAR StoreServ 7440cHP 3PAR StoreServ 7440c
HP building blocks of the new “shared environment”New situation
HP
DA
TA P
RO
TECTO
R
FARYS LAN
Storage Area Network
3PAR Remote Copy
HP C7000 with HP Blade servers
HP C7000 with HP Blade servers
HP FLEX-10 for C-class HP FLEX-10 for C-class
HP 8/24c for C-class HP 8/24c for C-class
HP 3PAR StoreServ 7440cHP 3PAR StoreServ 7440c
HP StoreOnce 4700
MSL StoreEver MSL6480
Introducing Farys/TMVW:• Who is Farys?
• Farys/TMVW business transformation over the years
• Why migrating to SAP HANA
SAP HANA infrastructure based on HP hardware:• SAP HANA?
• SAP HANA TDI versus appliance model
• HP building blocks of the new “shared environment”
Migration to the new platform:• Implementation timing
• SAP benefits after first migrations and roadmap
• Non-SAP workload benefits on the new “shared platform”
Agenda
Migration to the new platformImplementation timing
2/03/2015
Order new hardware material
26/03/2015
Delivery new hardware material
@ Farys
26/03/2015
Start Hardware implementation
and configuration
20/04/2015
Start SAP HANA installation on
new DL580 platform
25/04/2015
Migration of first SAP DEV DB’s to new SAP
HANA platform
01/06/2015
Go Live first SAP HANA PROD DB’s on new “Shared
platform”
< 1 month implementation time before first SAP HANA migration to the new platform
Migration to the new platformSAP benefits after first migrations
Business benefits actually achieved:
Month end closing drastically faster due to increased performance and implemented optimizations of BW on HANA.
Performance increase (up to >500%) in loading times and reporting response times:
Future business benefits planned:
Further BW on HANA optimization will be done when Business Suite is also on HANA in Q3 2015 Further increased performance in load and report execution time.
Migration to the new platformSAP benefits after first migrations
Business-wise
Faster and more real-time processing
Single source of the truth - universal document,
less replication of data
Business changer - it is faster, real-time, simple
and easy to handle for the business
IT infrastructure-wise
Simplified IT landscape
Reduced database size
Lower TCO on infrastructure (swap hot/cold)
Huge performance improvement
Migration to the new platformRoadmap
Basics
Simple Finance
Q1 2015 Q2 2015 Q3 2015 Q4 2015 Q1 2016 Q2 2016 Q3 2016 Q4 2016
HANA upgrade BW & CRM
New operation model of FARYS
Evaluation ofSimple Finance 2.0*
POC Simple Finance 1.0
Wave 1
Simple Finance 2.0
Technical
SMP3.0S4/HANA migration
Evaluation of Simple Logistics, ...
Wave 0 Wave 2
In continuous alignment with the roadmap of SAP S4/HANA & the overall ICT program
Simple Finance 2.0
Dashboarding, reporting & Fiori
Upgrade MRS 10
Migration to the new platformNon-SAP workload benefits on the new “shared platform”
Non-SAP workload benefits actually achieved:
97TB of Data stored on a footprint of 60TB by using zero detection and thin provisioning on the HP 3PAR StoreServ:
Non-SAP workload benefits actually achieved:
Disk service times minimized to less then 2 ms for SQL DB’s.
On EVA 4400
Migration to the new platformNon-SAP workload benefits on the new “shared platform”
Up to15ms
On HP 3PAR StoreServ
Up to1ms
Non-SAP workload benefits actually achieved:
We have a Deduplication rate of 14:1 by using a retention of 5 weeks for the full backups on disk.
Migration to the new platformNon-SAP workload benefits on the new “shared platform”
Dedup 14:1
Non-SAP workload benefits actually achieved:
Backup window decreased and stability increased by using B2D technology.
Migration to the new platformNon-SAP workload benefits on the new “shared platform”
Future business benefits planned:
• VMware vSphere Metro Cluster based on HP 3PAR StoreServ Peer Persistence
P
S
S
P Primary RC Volume active paths
Secondary RC Volume LUN passive paths
VM
Clustered Application
P
S
Migration to the new platformNon-SAP workload benefits on the new “shared platform”
Introducing Farys/TMVW:• Who is Farys?
• Farys/TMVW business transformation over the years
• Why migrating to S/4 HANA
SAP HANA infrastructure based on HP hardware:• SAP HANA?
• SAP HANA TDI versus appliance model
• HP building blocks of the new “shared environment”
Migration to the new platform:• Implementation timing
• First SAP experiences after migration
• Non-SAP workload benefits on the new “shared platform”
Lessons learned and conclusion
Agenda
Lessons learned
Close collaboration between ICT, business and consultants from different companies is crucial
Frequent meetings with key persons
Compatibility between all platforms (SAP HANA, Storage, HP Service Guard, Backup) can be a challenge
Functional and technical testing is crucial before migration
Additional training for internal IT people is needed (Some new components like Linux, HP ServiceGuard, … )
Conclusion
The business need for SSD “Flash” storage can be an enabler to invest in a new “shared storage platform”
This SSD tier will boost the performance of “ALL” your workloads
Xylos together with HPe can deliver and implement your new environment within a short time window
Top Related