IT IS CLASSIFIED AS “CUSTOMER” AND MAY ONLY BE SHARED WITH A THIRD PARTY IN VIEW OF AN ALREADY EXISTING OR FUTURE BUSINESS CONNECTION WITH SAP. THE CONENT OF THIS DOCUMENT IS SUBJECT TO CHANGE AND NO THIRD PARTY MAY LAY LEGAL CLAIM TO THE CONTENT OF THIS DOCUMENT. Legal Disclaimer THIS DOCUMENT IS PROVIDED FOR INFORMATION PURPOSES ONLY AND DOES NOT MODIFY THE TERMS OF ANY AGREEMENT. 29 Recommendations for the Storage Zone Networks. 27 System replication host name resolution. 25 Recommendations for the Internal Zone Networks. 25 Client reconnect for SAP HANA XS applications (http/https). 23 Connectivity suspend of the application server. 22 Client reconnect in SAP HANA system replication. 22 Client reconnect with the Secure User Store (hdbuserstore). 19 Recommendations for the Client Zone Network. Scenario: SAP BW on SAP HANA with system replication. 14 Shared-nothing architecture with Cluster File Systems. _ SAP HANA Development Team Ĭontents Legal Disclaimer. This paper discusses the SAP HANA network requirements using an SAP BW on SAP HANA system as an example. As an in-memory database, SAP HANA uses multiple network connections to transfer data, for example, from clients to the database during standard operations, between the nodes in a scale-out solution, and between data centers and to persistent storage in a disaster tolerant solution.