RECOVERY RECOVER DATA finished with error: [449] recovery strategy could not be determined, [111014] The backup with backup id 'xxxxxxx' cannot be used for recovery

[Former Member]

I'm trying to import all the data from one HANA instance to some other instance using complete data backup. I do not have an access to original instance, all I have is 2 folders:

• 'data' folder with files COMPLETE_DATA_BACKUP_databackup_0_1, 1_1, 3_1, 4_1, HOWEVER there is no file ending with 2_1
• 'log' folder

I have checked the version of HANA from backup files and it was 1.00.102.02.1446663129

Then I have tried to perform a recovery using the following command:

HDBSettings.sh recoverSys.py --wait --command="RECOVER DATA USING BACKUP_ID xxxxx USING LOG PATH ('/some/custom/path/log') USING DATA PATH ('/same/custom/path/data') CLEAR LOG"

I tried to do it on 2 fresh-installed instances of HANA:

• SPS10, 1.00.102.00.1442292917
• SPS11, 1.00.111.00.1454183496

Unfortunately, in both cases the recovery failed with the following messages:

2016-02-29T10:21:52+01:00  P146357      1532c5577cd ERROR   RECOVERY RECOVER DATA finished with error: [449] recovery strategy could not be determined, [111014] The backup with backup id 'xxxxxxx' cannot be used for recovery

2016-02-29T10:21:52+01:00  P146357      1532c5577cd ERROR   RECOVERY RECOVER DATA finished with error: [449] recovery strategy could not be determined, [111014] The backup with backup id 'xxxxxxx' cannot be used for recovery
start system: myhostname failed: start of nameserver failed

recoverSys failed:

Do you have any idea how to fix it?

[Former Member]

Hi Andrey,

Can you provide more information on the landscape from which the backup is taken?

Are you restoring the backup from a Single container(non distributed) to a destination system which is also a single container(non distributed)?

The backup file *2_1* may not be the reason for the failure of this restore as this file used to be the backup volume for the statistics server on a Single container system with Standalone Statistics Server.

So if you had upgraded your source system from Standalone Statistics server to Embedded Statistics Server(ESS) you will see such behavior when the backup volume *2_1* is not generated any more.

Can you check if you had clicked on the check box INITIALIZE LOG AREA during the recovery?

I think this is important for the recovery from one source system to another destination system

Hope this helps

Sunil

[former_member183326]

Hello,

Have you looked at 2088384 - Cannot Recover Database

It seems the log segment you are using was corrupt.