SAP Knowledge Base Article - Preview

3751038 - SAP HANA recovery via BACKINT may appear stalled at high recovery percentage although recovery threads remain active

Symptom

During SAP HANA recovery using BACKINT, the recovery may appear stalled for many hours at a high recovery percentage (for example 80–95%) although no explicit database crash or recovery termination occurs.

Typical observations may include:

  • recovery percentage no longer visibly changes
  • backup.log no longer shows frequent progress updates
  • database services remain in recovery state
  • no clear internal SAP HANA deadlock is visible
  • BACKINT logs may contain long inactive periods
  • restore operation remains active for an extended time

Runtime dumps may show thread states similar to:

AbstractRecoveryExecutor::waitForJobs()
ReadPipeChannel::triggerRead()
MultistreamRestoreCoordinator::run()
BackupSrc_CommonSnapshot::executeRestore()

Recovery-related threads may remain present while SAP HANA waits for responses or restore data through the BACKINT interface.


Read more...

Environment

SAP HANA DB Version 2.0

Product

SAP HANA, platform edition 2.0

Keywords

BACKINT, recovery appears stalled, high recovery percentage, waitForJobs, ReadPipeChannel, multistream restore, delayed restore payload, backup.log, backint.log, prolonged recovery, runtime dump , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , 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.