3719920 - Tenant recovery via BACKINT may stop due to delayed or missing BACKINT response (service_start_max_retry timeout)

During tenant recovery using BACKINT, the recovery does not progress and eventually fails with errors similar to:

• recovery could not be completed
• Found service neither active nor starting for recovery
• Tenant database stops during recovery

The issue typically occurs when executing:

RECOVER DATA FOR <tenant> USING SOURCE '<SID>@<SID>' USING BACKINT ('<backup_id>') CLEAR LOG;

Observed behavior:

• SAP HANA starts the recovery
• BACKINT process is triggered
• Recovery appears to hang for a long period (often around 10–25 minutes)
• Afterwards SAP HANA stops the tenant database

HANA traces show that BACKINT connection or response occurs significantly later than the recovery start timestamp.

The issue is commonly observed during system refresh or restore to a restore target system.
The tenant services may appear correctly configured and present in the system topology.

SAP HANA DB Version 2.0

SAP HANA, BACKINT, RECOVER DATA, tenant recovery, system refresh, restore, service_start_max_retry, recovery timeout, backup.log, nameserver trace, Veritas, recovery stopped, Found service neither active nor starting for recovery , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , Problem