why HANA backup check availability or check access fails/timeouts from HANA Studio in Azure Native backup using recovery vault.

Patil, Prafulla B 0 Reputation points
2023-11-07T19:32:43.69+00:00

During HANA DB restore or PIT recovery from HANA Studio, Check availability or check access fails for HANA backup on Azure Native backup using recovery vault.

Restore using full backup-

Check availability of backup- timeouts

PIT recovery- with check access- FAILS

2023-11-06T14:12:35-06:00  P0042494      18ba643fb64 INFO    RECOVERY command: RECOVER DATABASE FOR MDS UNTIL TIMESTAMP '2023-11-06 17:55:00' CLEAR LOG USING CATALOG BACKINT USING LOG PATH ('/usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/') USING DATA PATH ('/usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/') USING BACKUP_ID 1699207215094 CHECK ACCESS USING BACKINT IGNORE DELTA DATA BACKUPS

2023-11-06T14:15:02-06:00  P0042494      18ba643fb64 INFO    RECOVERY using backup catalog 1699294845748 from /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/log_backup_0_0_0_0

2023-11-06T15:08:05-06:00  P0042494      18ba643fb64 ERROR   RECOVERY error in backint: /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_0_1 638348040150950000-1699207215094

2023-11-06T15:08:05-06:00  P0042494      18ba643fb64 ERROR   RECOVERY error in backint: /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_2_1 638348040150950000-1699207215094

2023-11-06T15:08:05-06:00  P0042494      18ba643fb64 ERROR   RECOVERY error in backint: /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_3_1 638348040150950000-1699207215094

2023-11-06T15:08:05-06:00  P0042494      18ba643fb64 INFO    RECOVERY Ignoring unavailable backint backup in strategy: BACKINT inquire job from /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_0_1 failed with error code ERRORBACKINT inquire job from /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_2_1 failed with error code ERRORBACKINT inquire job from /usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/FULL_SCHD_databackup_3_1 failed with error code ERROR

2023-11-06T15:08:05-06:00  P0042494      18ba643fb64 ERROR   RECOVERY RECOVER DATA finished with error: [449] recovery strategy could not be determined, [111014] The backup with backup id '1699207215094' cannot be used for recovery

PIT Recovery without check access- SUCCESS

RECOVER DATABASE FOR MDS UNTIL TIMESTAMP '2023-11-06 17:55:00' CLEAR LOG USING CATALOG BACKINT USING LOG PATH ('/usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/') USING DATA PATH('/usr/sap/MDS/SYS/global/hdb/backint/DB_MDS/') USING BACKUP_ID 1699207215094 IGNORE DELTA DATA BACKUPS

Without check availability, check access- the restore, recovery is successful without issues.

Please let us know why this check availability or check access fails/timeouts from HANA Studio in Azure Native backup using recovery vault.

We use Private End Points to access Azure recovery service vault.

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,490 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator
    2024-02-05T14:44:44.76+00:00

    @Patil, Prafulla B Thank you for your patience and understanding!

    As per support team the issue has been resolved. Sharing the solution with broader community! Issue Details:

    Symptoms: Check Availability action from native restore was failing while normal restores were succeeding.

    Cause: Check Availability was using a different workflow in the extension that was not working with PEs correctly.

    Resolution: Product Group fixed issue in next extension release. It took some time for deployment to complete and get confirmation from our customers.

    @Patil, Prafulla B Confirmed that, Check Availability ran as expected on 1.0.0.89.

    Hope this helps others who might be looking for a solution to similar issues.


    If the response helped, do "Accept Answer" and up-vote it

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.