Symptom
The recovery of a file based backup is failing with this error, which can be seen in the backup.log:
Backup ID : 1492655459448
Status : Successful
Backup Type : Data Backup
Destination Type : File
Location : /usr/sap/XYZ/HDB00/backup/data/
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY command: RECOVER DATABASE UNTIL TIMESTAMP '2017-04-20 02:32:00' USING DATA PATH ('/usr/sap/XYZ/HDB00/backup/data/') USING LOG PATH ('/hana/shared/XYZ/HDB00/backup/data','/usr/sap/XYZ/HDB00/backup/data','/hana/shared/XYZ/HDB00/backup/log') USING BACKUP_ID 1492655459448 CHECK ACCESS USING FILE
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryExecuteCatalogRecoveryInProgress
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryError
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryExecuteCatalogRecoveryInProgress
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryError
2017-05-04T12:31:33+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryExecuteCatalogRecoveryInProgress
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f INFO RECOVERY state of service: nameserver, hanaserver:32001, volume: 0, RecoveryExecuteCatalogRecoveryFinished
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f INFO RECOVERY using backup catalog 1493874536214 from file /hana/shared/XYZ/HDB00/backup/log/log_backup_0_0_0_0.1493874536214
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493778609422
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493692208618
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493605807842
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493519406995
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493433006307
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493346605467
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493260204651
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493173803887
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493087403094
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1493001001937
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1492914601293
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1492828200390
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1492741859820
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY Backup /usr/sap/XYZ/HDB00/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 has Backup ID 1493865010220, but is expected to have Backup ID 1492655459448
2017-05-04T12:31:34+05:30 P043222 15bd2438b2f ERROR RECOVERY RECOVER DATA finished with error: [449] recovery strategy could not be determined, [111014] The backup with backup id '1492655459448' cannot be used for recovery
Read more...
Environment
- SAP HANA 1.0
- SAP HANA 2.0
- HANA Studio
Product
Keywords
COMPLETE_DATA_BACKUP, recovery could not be completed , 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.