适用于 Compute Engine 实例上 SAP HANA 的 SAP HANA savepoint API（Persistent Disk 快照）
Backup and DR Service 使用 Persistent Disk 快照以增量方式备份永久性磁盘中的数据和日志卷，并确保应用一致性。备份和灾难恢复在多个位置存储每个快照的多个副本，并利用自动校验和来确保数据完整性。Backup and DR 支持 SAP HANA 2.0 扩容和 SAP HANA 2.0 高可用性 (1+1) 复制系统。
SAP HANA savepoint API（卷级备份）
此方法基于存储在数据卷区域和 Linux 更改块跟踪中的保存点，利用 SAP HANA 数据库内部快照来进行高效、节省空间的增量永久备份。
SAP HANA 数据会根据指定的备份计划以应用优先格式捕获。系统会创建并存储一次该数据的黄金副本，然后仅在增量永久模型中使用更改的数据块对其进行增量更新。这具有 SAP HANA 数据库可即时挂载和恢复的优势。数据的虚拟副本可立即供使用，而无需繁衍实体副本并占用额外的存储基础架构。
SAP Backint API（完整备份+增量备份）
备份 SAP HANA 的旧方法是使用 hdbsql 使用 Backint API。Backint API 会通过 iSCSI 或 NFS 将备份发送到映射到 SAP HANA 主机的暂存磁盘。在这两种方法中，都会定期进行完整备份，并且捕获的数据采用专有备份格式，而不是采用块格式。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eThis document details protection methods for SAP HANA Scale-Out instances using Backup and DR Service, with distinct methods available for Scale-Up and HA 1+1 configurations.\u003c/p\u003e\n"],["\u003cp\u003eThe preferred protection method for SAP HANA Scale-Out is either the SAP HANA \u003ccode\u003esavepoint\u003c/code\u003e API (LVM backup) or the SAP \u003ccode\u003ebackint\u003c/code\u003e API (Full+Incremental backup), particularly for application-aware mounts or mount-and-migrate capabilities.\u003c/p\u003e\n"],["\u003cp\u003eBackup and DR Service utilizes Persistent Disk snapshots for data and log volume backups, ensuring application consistency and storing multiple data integrity-checked snapshot copies.\u003c/p\u003e\n"],["\u003cp\u003eSAP HANA configurations supported include single container systems (HANA 1.0 or 2.0) and multiple-container systems (HANA 2.0), with the \u003ccode\u003eSavePoint\u003c/code\u003e API method being generally preferred except for scale-out with shared storage.\u003c/p\u003e\n"],["\u003cp\u003eHANA log backups are automatically handled across all supported configurations and options, irrespective of the chosen backup method, for both single and multiple-container systems.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for SAP HANA Scale-Out\n\n| **Note:** This information is for SAP HANA Scale-Out instances. For Scale-Up and HA 1+1 configurations, see [Backup and DR Service for SAP HANA](/backup-disaster-recovery/docs/concepts/backupdr-for-sap-hana).\n\nProtection methods\n------------------\n\nThe most common protection method for SAP HANA databases and logs in\nBackup and DR is the SAP HANA `savepoint` API (Persistent Disk snapshot)\nfor SAP HANA on a Compute Engine instance.\n\nYou can also protect HANA databases using either of the two following alternative\nprotection methods:\n\n- SAP HANA `savepoint` API (LVM backup)\n- SAP `backint` API (Full+Incremental backup)\n\nThese methods are preferable only if you require HANA Scale-Out or if you have\nneed for application-aware mounts or mount-and-migrate ability for HANA\ndatabases.\n\nIf you can use the Persistent Disk snapshot backup method, then go to [Backup and DR Service for SAP HANA](/backup-disaster-recovery/docs/concepts/backupdr-for-sap-hana).\n\n### SAP HANA `savepoint` API (Persistent Disk snapshot) for SAP HANA on a Compute Engine instance\n\nBackup and DR uses Persistent Disk snapshots to incrementally back up data\nand log volume from your persistent disks with application consistency.\nBackup and DR stores multiple copies of each snapshot across multiple\nlocations with automatic checksums to ensure the integrity of your data.\nBackup and DR supports SAP HANA 2.0 Scale-up and SAP HANA 2.0 HA (1+1)\nreplication system.\n\n### SAP HANA `savepoint` API (volume-level backup)\n\nThis method leverages an SAP HANA database internal snapshot based\non savepoint stored in the data volumes area and in Linux change block tracking\nto take an efficient, space saving, incremental forever backup.\n\nSAP HANA data is captured in application first format, according to a specified\nbackup plan. A golden copy of that data is created and stored once, and is then\nupdated incrementally with only the changed blocks of data in an incremental\nforever model. This provides the advantage of instantaneous mount and recovery\nof SAP HANA databases. Virtual copies of the data can be made available\ninstantly for use, without proliferating physical copies and taking up\nadditional storage infrastructure.\n\n### SAP `Backint` API (Full+Incremental backup)\n\nThe older way of backing up SAP HANA is using the Backint API using\nhdbsql. The Backint API sends backups to a staging disk mapped to the SAP HANA\nhost over iSCSI or NFS. In both approaches, there is a periodic full backup and\nthe data captured is in a proprietary backup format and not in block\nformat.\n\n### Backup and DR supportability of different SAP HANA configurations\n\n| **Note:** See the important information at [SAP HANA studio, metadata, and backup images](/backup-disaster-recovery/docs/access-data/recover-sap-hana#SAP-HANA-studio,-metadata,-and-backup-images).\n\nBackup and DR can virtualize and protect the following:\n\n- **Single container system (HANA 1.0 or 2.0) dedicated**: In a\n single-container system the system database and tenant database are seen as a\n single unit and are administered as one.\n\n- **Multiple-container systems (HANA 2.0)**: Multiple isolated databases in a\n single SAP HANA system. These are referred to as multi-tenant database\n containers. A multiple-container system always has exactly one system\n database used for central system administration, and any number of\n multi-tenant databases (including zero), also called tenant databases.\n\nThis table lists all the supported HANA configurations and the backup methods\nthat apply with each one.\n\n- HANA `SavePoint` API method is the preferred method when available, for all HANA\n configurations except for scale-out with shared storage.\n\n- The `backint` method is available for all HANA configurations.\n\n- HANA log backups are always handled automatically for all configurations and\n options.\n\nWhat's next\n-----------\n\n[Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/prepare-sap-hana-scaleout)\n\nBackup and DR Service documentation for SAP HANA Scale-Out\n----------------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nSAP HANA Scale-Out instances with Backup and DR Service.\nYou can find additional information in the following pages:\n\n- [Backup and DR for SAP HANA Scale-Out](/backup-disaster-recovery/docs/concepts/backupdr-for-sap-hana-scaleout)\n- [Prepare SAP HANA Scale-Out instances for backup](/backup-disaster-recovery/docs/configuration/prepare-sap-hana)\n- [Add an SAP HANA Scale-Out host, and discover and protect its databases](/backup-disaster-recovery/docs/configuration/discover-sap-hana-scaleout)\n- [Configure staging disk format and backup method for SAP HANA Scale-Out](/backup-disaster-recovery/docs/backup/backup-method-staging-disk-sap-hana-scaleout)\n- [Set application details and settings for SAP HANA Scale-Out instances](/backup-disaster-recovery/docs/backup/app-details-settings-sap-hana-scaleout)\n- [Back up HANA 1+n and HANA scale-out databases](/backup-disaster-recovery/docs/backup/back-up-sap-hana-scaleout)\n- [Restore and recover SAP HANA Scale-Out instances](/backup-disaster-recovery/docs/restore-data/restore-sap-hana-scaleout)\n- [Mount an SAP HANA Scale-Out backup as a standard mount](/backup-disaster-recovery/docs/access-data/mount-sap-hana)\n- [Mount an SAP HANA Scale-Out backup as a virtual database](/backup-disaster-recovery/docs/access-data/mount-sap-hana-virtualdb)\n- [Mount and migrate an SAP HANA Scale-Out backup for instant recovery to any target](/backup-disaster-recovery/docs/access-data/mount-and-migrate-sap-hana)"]]
