We've come a long way. With both On-Prem and Cloud options discussed, it's now time to think how we could mash these together in a hybrid solution. But before we do that, we'll recap the options we've covered so far.
On Prem Appliance - A single part number containing everything required to run either Scale Up or Scale Out HANA. Installed by the vendor or trained partner. A safe pair of hands.
On Prem TDI - The same as an appliance but with the storage layer removed. This allows the customer to integrate their preferred enterprise storage. Also, includes networking if working with a scale-out system. On-Prem TDI maintains Appliance performance whilst providing additional flexibility.
Private Cloud - HANA appliances or TDI systems that can be provisioned at will, either natively or as virtual machines. All the performance of standard On-Prem with the advantage of cloud-style provisioning. Usually very expensive.
Public Cloud - The use of public cloud containers by vendors such as Azure and AWS that have been certified by SAP for use as production HANA systems. Great flexibility, but limited in scale.
Some deployments of HANA will fit neatly into an On-Prem option. Others are a better match for one of the cloud options. Some systems. however, will span both cloud and On-Prem.
There are a number of reasons why a customer would consider deploying a Hybrid Cloud for HANA. The most common reason is when the production system must remain On Prem. Despite this, the customer still wants the flexibility and rapid deployment features of the public cloud for their non-production instances. The list of reasons why customers may feel they need their production systems to remain On-Prem is long and varied and too complex to discuss here.
Using HANA in the cloud can speed up deployment. The creation of sandbox and test systems can be heavily automated, saving time and allowing development and test teams to work rather than wait. Backups of cloud systems can be committed to cloud storage, leaving the On-Prem backup solutions dedicated to production workloads.
Despite these, and many other advantages of cloud systems, there are some downsides. The production system will not match the cloud instances. To fulfil best practice, a similarly specced pre-production system should be available On-Prem for full load testing. Data refreshes can also be problematic, as large data footprints are copied from the customer's site up into the cloud.
Another, less common approach to Hybrid Cloud for HANA is where production is done in the cloud and non-production is done On-Prem. Again there are some good reasons for this. Cloud providers can provision containers in different geographic regions. This allows customers with only a single data centre to move production to the cloud and gain an effective disaster recovery strategy without hosting physical hardware in a third party data centre. The non-production HANA systems could be hosted On-Prem within a conventional VM farm (if the VM farm meets the requirements for HANA).
That's it. We've summarised all the current options for deploying productive SAP HANA workloads and, albeit brief, discussed where hybrid solution could be used.
Exactly what option is right for a any particular customer will always depend on their requirements and budget. Centiq specialises in helping customers design, implement and support SAP HANA landscapes. We use our collective experience to create solutions that meet and exceed customer requirements. Our services also extend to long term management of SAP HANA and BASIS services. Get in touch for more information.