Sweet, Simple . . . and Explosive?

[Former Member]

Suite on HANA, Simple Finance, and a really cool explosion video as a bonus.

The recent parallel announcements of SAP Simple Finance and HP Converged System 900 for SAP HANA (CS900) motivated my blog on saphana.com about the increasing business value of Suite on HANA and the ability to run such a mission critical system in a low risk fashion. The blog covers following topics in quite some detail:

• SAP Simple Finance
  The blog explains the new SAP Simple Finance solution, the “trick” that it is using and the resulting business and IT benefits.
  
  
• Customer Example: HP IT
  To put the move to SAP Business Suite on HANA into perspective, the blog gives a glimpse into the data sizing and preparation underway within the HP IT team.
  
  
• HP ConvergedSystem 900 for SAP HANA (CS900) - see diagram below
  It also talks about the breakthrough HP CS900 system, the largest and most robust of its type with up to 12TB of RAM in a single system.
  
  
• SAP HANA Datacenter readiness including comparison of storage and system level replication - see table below
  Most importantly, the blog busts any doubts that SAP HANA is not data center ready. With a broad offering of high availability and disaster recovery offerings from HP and other vendors, business continuity of SAP HANA is ensured; if need be in a fully automated fashion.
  
  

And the explosion? – A video shows a live datacenter failing over to a remote site within seconds, triggered by a small load of TNT.

For the full content, please read the detailed blog on saphana.com. – Kindly share your thoughts on SAP Simple Finance, HANA datacenter readiness, and HP Converged System 900 for SAP HANA and I will be sure to reply to your comments.

Thanks,

Swen

Picture: System family for HP ConvergedSystem 900 for SAP HANA

	Storage Replication	System Replication
Vendors	HP, IBM, Hitachi, CISCO, Dell, Fujitsu, NEC, VCE, Huawei, Lenovo (China only)	- HP ServiceGuard - SUSE Linux Cluster (in beta)
Supported HANA use cases	- Scale-up - Scale-out	- Scale-up - Scale-out (only HP)
Replication strategies	- Synchronous - Asynchronous	- Synchronous - Asynchronous
Bandwidth requirements	Higher -  Replication of partial transactions results in costly roll-backs when transaction is cancelled, e.g. due to failure	Lower - No transmission of cancelled transactions; replication only after full commit - Sync mode: only log files are transferred continuously with transaction commit, rest async driving lower bandwidth
Disaster recovery (*) - Performance optimized: - Cost optimized:	- Slow - Slow	- Fast - Medium
Openness	Hardware vendor dependent	Infrastructure agnostic
Additional capabilities	n/a	- Zero downtime management (aka NetWeaver connectivity suspend) - Cascading multi-tier system replication (only HP)
Key roadmap capabilities	n/a	Active/Active Operation (read only reporting on secondary fail over site)
(*) Performance optimized - Secondary system completely used for the preparation of a possible take-over - Resources used for data pre-load on secondary - Take-overs and Performance Ramp shortened maximally Cost optimized - Operating non-prod systems on secondary - Resources freed (no data pre-load) to be offered to one or more non-prod installations - During take-over the non-prod operation has to be ended - Take-over performance similar to cold start-up

Table: High level comparison between storage and system level replication with SAP HANA