Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A savepoint writes a consistent database state to persistent storage. A backup provides recoverable copies under the backup strategy; those mechanisms serve different recovery purposes.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP HANA is a database platform. Data models describe how records relate; queries ask for results. Start with the intended result before looking at storage or performance.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP HANA savepoint versus backup: Persistence and recoverability are different
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP HANA Platform persistence, completed savepoints, redo-based restart and separate backup recovery evidence. HANA Cloud monitoring is identified separately; no production restart/recovery or persistence parameter change is executed.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Separate database persistence from recovery protection

Two recovery mechanisms

Savepoint: Consistent persisted state. Backup: Recoverable copy strategy. Failure example: Underlying storage lost. Recovery question: What surviving copy exists?
What to notice: Persistence on the affected storage is not a replacement for the required backup and recovery strategy.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Savepoint
Consistent persisted state
Backup
Recoverable copy strategy
Failure example
Underlying storage lost
Recovery question
What surviving copy exists?
Words you’ll meet in this guide
Query
A request to retrieve or calculate data.
Table
Data organized into rows and columns.
Persistence
Keeping data in storage so it survives beyond memory.
HANA
SAP’s database platform.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Database state → Persistent savepoint → Backup and recovery strategy. Conceptual diagram for SAP HANA savepoint versus backup: Persistence and recoverability are different.
Apply the idea: A manufacturer's operations team reviews database persistence while planning protection for critical purchasing and production data.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Separate database persistence from recovery protection

    A manufacturer's operations team reviews database persistence while planning protection for critical purchasing and production data.

  2. A savepoint supports restart; a backup supports a separate recovery path

    A HANA savepoint persists a consistent database state in the data volumes.

  3. Separate committed work from the last persisted savepoint image

    A savepoint and a transaction commit are different events.

  4. Worked case: restart after a change made between savepoints

    Imagine tenant SALES with a completed savepoint observed at 09:55.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.