How to design your SAP HANA disaster recovery | CHANGE as a Service

Awesome! Emilio thanks for sharing this really good post. IMHO the best way to replicate is thru HANA itself with Bandwidth Optimizers on both sides. also, you have to consider the rest of the applications like BO, or maybe, it’s a suite on HANA, it would be nice how this kind of architecture change. Thanks again for so awesome note.

This scenario will work for both HANA appliances with internal disk, and also for configurations with external storage. It’s based on functionality offered by SAP on HANA since SPS 05. In this setup each individual HANA node replicates to corresponding standby HANA node on the remote data center. What it does basically is send the logs to the standby node to be replayed. Can be configured to work synchronously, asynchronously or asynchronous in-memory.

via How to design your SAP HANA disaster recovery | CHANGE as a Service.

One thought on “How to design your SAP HANA disaster recovery | CHANGE as a Service

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s