Optimize your SAP environment and save costs

The move to RISE with SAP or any S/4HANA system can increase your data requirements exponentially. S/4HANA implementations are more data-hungry, and the sizing of hardware is not just about disk space; it's also memory. These come packaged either as a pre-built appliance, or you can leverage hyperscalers who provide T-shirt sizing for consumption.

To help you calculate potential reduction in costs using EPI-USE Labs’ solutions, we have built a calculator based on AWS pricing demonstrating Data Sync Manager (DSM)’s slicing capabilities. Note that with the HANA database you are recommended to increase the size of the appliance when it reaches a certain capacity, so the appliance size will be larger than your data usage.

Typically, with Client Sync, part of the DSM Suite, we see a reduction of 75%. So a non-production system could leverage an appliance a quarter of the size of Production. As the Production system grows (with more years of history), the non-production appliances will grow far more slowly. So your test landscape can remain on the same size of appliance, even as Production increases its hardware spend.

Find out how much you could save per HANA device using Data Sync Manager (DSM)

Current Production size

Non-production size

Number of non-production devices

Calculate

You could realise potential savings of 50-75% per appliance.

Please complete the form so we can give you a detailed analysis.

« Recalculate

Estimated cost savings per HANA device

Production size:
Non-production size:
Number of non-production devices:

Annual savings per device

Total savings in year 1

Total savings over 3 years

Total savings over 5 years

Current and future spend per instance

Current: without DSM
Future: with DSM slicing non-production

Future savings per device

Future consumption vs. current consumption

Current and future spend per instance

Current: without DSM
Future: with DSM slicing non-production

Future savings per device

Future consumption vs. current consumption

Supporting information

Typical DSM Client Sync implementations realise a 75% reduction in diskspace, and therefore memory, compared to a full copy of the Production system. By entering the appliance sizes listed here, we are providing a calculation based on the current pricing for AWS in North America:

AWS Instance	vCPU	Memory	Storage Estimate	Instance + Storage Price (annual)	Quote
256 GB r5.8xlarge	32	256	640	$12,304	Link
512 GB r5.16xlarge	64	512	1,024	$24,121	Link
1TB r6i.32xlarge	128	1,024	2,048	$50,442	Link
2TB x2idn.32xlarge	128	2,048	3,584	$78,370	Link
4TB x2iedn.32xlarge	128	4,096	6,656	$102,106	Link
6TB u-6tb1.56xlarge	224	6,144	9,728	$268,040	Link
9TB u-9tb1.112xlarge	448	9,216	14,336	$302,449	Link
12TB u-12tb1.112xlarge	448	12,288	18,944	$402,977	Link

Actual reductions can vary from company to company, based on industry, age of the SAP system and implementation decisions made along the way. The test systems created with Client Sync behave exactly like a copy of Production, but without any historical date from before the slice date (unless it is referenced by data within the slice). As such, the non-production instances can grow year-on-year at a far slower rate than Production. This means tremendous future savings compared to full copies of Production, where the increased hardware costs are mirrored to all non-production copies.

More information on SAP HANA sizing.

Costings within RISE with SAP are less clear, but predicted savings are likely to be higher than those shown here, given that the management and support costs are also likely to increase based on the total system size of the landscape.

book a discovery call Save as PDF « Recalculate