Who says the primary SAP HANA instance must be in one location? We are accustomed to the idea of “follow the sun” with technical support teams on critical matters. Why not consider this for operational matters as well?
Let’s expand on the global reporting scenario and revisit the global electronics manufacturer with operations in Asia, Europe, Africa, and the North America. The primary role in the SAP HANA system replication topology can be reassigned to another SAP HANA instance with the replication connections re-established to the secondary tier instances (multi-targets). Instead of the primary or leading SAP HANA instance always in Europe, over a 24 hours period, the location of the leading SAP HANA instance could change based on business requirements.
Below, Diagram 1 shows that the leading SAP HANA instance is based in Asia. The SAP HANA instances in Europe, Africa and the North America are in the secondary tier and read accessible with the SAP HANA active/active read-enabled option.
Diagram 1 – Leading SAP HANA instance in Asia
As the work day comes to an end in Asia, role of “Primary” or “Leading” can be assigned to the Europe SAP HANA instance. In diagram 2, the leading SAP HANA instance would be in Europe, the SAP HANA instances in Asia, Africa, and the North America would be in the secondary tier and accessible for pure reads.
Diagram 2 – Leading SAP HANA instance in Germany
As you would expect for this example, as the work day comes to an end in Europe, the role of “Primary” or “Leading” can be assigned to the SAP HANA instance in the North America. In diagram 3, the leading SAP HANA instance would be in the North America, and the SAP HANA instances in Asia, Africa, and Europe would be in the secondary tier and accessible for pure reads.
Diagram 3 – Leading SAP HANA instance in the North America