SAP Knowledge Base Article - Preview

3217342 - Parameter 'logshipping_async_buffer_size' doesn't take effect in secondary site of a 3-tiers landscape


In 3-tiers (site A-> site B-> site C) replication landscape, you set logshipping_async_buffer_size = 2147483648 ( 2*1024*1024*1024 = 2GB) on secondary site (site B), and then restart tertiary site (site C) HANA to re-active the connection. But via hdbcons 'replication info' on the secondary (site B), you find the logshipping_async_buffer_size is still 268435456 ( 256*1024*1024 = 256 MB)(default value).

hdbcons 'replication info'
System Replication Primary Information
System Replication Primary Configuration
 [system_replication] logshipping_async_buffer_size               = 268435456  

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."



  • SAP HANA, platform edition 2.0
  • 3-tiers (site A-> site B-> site C) system replication landscape


SAP HANA, platform edition 2.0


logshipping_async_buffer_size, Asynchronous log shipping buffer full, secondary, HANA replication, offline, online parameter , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.