Compute Engine 인스턴스의 SAP HANA용 SAP HANA savepoint API (영구 디스크 스냅샷)
백업 및 DR은 영구 디스크 스냅샷을 사용하여 애플리케이션 일관성을 유지하면서 영구 디스크의 데이터와 로그 볼륨을 증분 방식으로 백업합니다.
백업 및 DR은 데이터 무결성을 보장하는 자동 체크섬을 사용하여 각 스냅샷의 복사본 여러 개를 여러 위치에 저장합니다.
백업 및 DR은 SAP HANA 2.0 확장 및 SAP HANA 2.0 HA (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 호스트에 매핑된 스테이징 디스크로 백업을 전송합니다. 두 접근 방식 모두 주기적인 전체 백업이 있으며 캡처된 데이터는 블록 형식이 아닌 독점 백업 형식입니다.
다양한 SAP HANA 구성의 백업 및 DR 지원 가능 여부
백업 및 DR은 다음을 가상화하고 보호할 수 있습니다.
전용 단일 컨테이너 시스템 (HANA 1.0 또는 2.0): 단일 컨테이너 시스템에서는 시스템 데이터베이스와 테넌트 데이터베이스가 단일 단위로 간주되며 하나로 관리됩니다.
다중 컨테이너 시스템 (HANA 2.0): 단일 SAP HANA 시스템에 격리된 여러 데이터베이스가 있습니다. 이를 멀티 테넌트 데이터베이스 컨테이너라고 합니다. 멀티 컨테이너 시스템에는 항상 중앙 시스템 관리에 사용되는 시스템 데이터베이스가 하나뿐이며 테넌트 데이터베이스라고도 하는 멀티테넌트 데이터베이스는 원하는 개수만큼 있을 수 있습니다 (0 포함).
이 표에는 지원되는 모든 HANA 구성과 각 구성에 적용되는 백업 방법이 나와 있습니다.
HANA SavePoint API 메서드는 공유 스토리지를 사용한 수평 확장을 제외한 모든 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"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\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)"]]
