Symptom
In a System Replication landscape , you may notice frequent log shipping timeouts or even log volume full situations occur for secondary site.
In the indexserver trace on secondary, you see the entry
w PersistenceManag DisasterRecoveryProtocol.cpp(04582) : log buffer takes more than 30000000 us to process and write, this could be caused by write-IO peak.
w PersistenceManag DisasterRecoveryProtocol.cpp(04583) : This trace is intended to clarify frequent "logshipping timeout" situation. If this is the case, then it's probably by write-IO, not by network.
Read more...
Environment
SAP HANA with system replication enabled
Product
Keywords
KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem
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.