Skip to Content

HANA Backup fails with "wrong checksum" error

Hello HANA experts,

Our HANA (SPS 7) test database system backup ends with following error:

Could not back up system <SID> backup could not be completed, Wrong checksum: Calculated 1320888980, stored 1611380413.; $ppno$=

Error log contents:

145a59295ef ERROR   BACKUP   SAVE DATA finished with error: [447] backup could not be completed, [3020043] Wrong checksum: Calculated 1320888980, stored 1611380413.; $ppno$=

Further details:

Backup failure is for “index server”; backup for rest of the servers gets successfully completed.

How could I resolve this error?  Any help is highly appreciated.

Thanks in advance,

Shaji

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Apr 28, 2014 at 01:26 AM

    what is your backup destination? does it have enough space?

    Add comment
    10|10000 characters needed characters exceeded

  • May 06, 2015 at 10:45 AM

    Hello Shaji,

    Check if note 1990971 - HANA backup failed with "Wrong Checksum" error helps?

    Regards,

    Ning

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 14, 2015 at 03:25 PM

    Hello,

    did anyone ever find another solution than recovering the last valid backup if this happened on the indexserver datafile? We encounter the same after HANA upgrade from rev. 96 to 97.

    The backup right before the upgrade worked, after the upgrade we get the checksum error. There are no I/O errors on the OSlevel and we could not identify any issue with the database.

    However, a new backup can not be created. We already opened a call with SAP, but since I am running out of ideas I wonder if anyone has ever fixed this without recovery.

    Thank you

    Florian

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Just to update everyone who is reading this message thread. In the end we found no other solution than performing a recovery to most recent state, which resolved the issue. Since we had to roll through almost 20 days of log-backups and the last valid backup was taken before the upgrade to 97, we first recovered it on a Sandbox for validation before we performed the recovery on the actual system. Regards Florian