Layanan Backup dan DR untuk Penyebaran Skala SAP HANA
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Metode perlindungan
Metode perlindungan yang paling umum untuk database dan log SAP HANA dalam
Pencadangan dan DR adalah SAP HANA savepoint API (Snapshot Disk Permanen)
untuk SAP HANA di instance Compute Engine.
Anda juga dapat melindungi database HANA menggunakan salah satu dari dua metode perlindungan
alternatif berikut:
SAP HANA savepoint API (cadangan LVM)
SAP backint API (Pencadangan Lengkap+Inkremental)
Metode ini hanya direkomendasikan jika Anda memerlukan HANA Scale-Out atau jika Anda membutuhkan pemasangan yang sesuai dengan aplikasi atau kemampuan pemasangan dan migrasi untuk database HANA.
SAP HANA savepoint API (Snapshot Persistent Disk) untuk SAP HANA di instance Compute Engine
Pencadangan dan DR menggunakan snapshot Persistent Disk untuk mencadangkan data dan volume log secara bertahap dari persistent disk Anda dengan konsistensi aplikasi.
Cadangan dan DR menyimpan beberapa salinan setiap snapshot di beberapa lokasi dengan checksum otomatis untuk memastikan integritas data Anda.
Pencadangan dan DR mendukung sistem replikasi SAP HANA 2.0 Scale-up dan SAP HANA 2.0 HA (1+1).
SAP HANA savepoint API (pencadangan tingkat volume)
Metode ini memanfaatkan snapshot internal database SAP HANA berdasarkan
titik simpan yang disimpan di area volume data dan di pelacakan blok perubahan Linux
untuk melakukan pencadangan inkremental terus-menerus yang efisien dan menghemat ruang.
Data SAP HANA diambil dalam format aplikasi pertama, sesuai dengan rencana cadangan
yang ditentukan. Salinan emas data tersebut dibuat dan disimpan sekali, lalu
diupdate secara bertahap hanya dengan blok data yang diubah dalam model
inkremental selamanya. Hal ini memberikan keuntungan pemasangan dan pemulihan database SAP HANA secara instan. Salinan virtual data dapat disediakan
secara instan untuk digunakan, tanpa memperbanyak salinan fisik dan menggunakan
infrastruktur penyimpanan tambahan.
SAP Backint API (Pencadangan Lengkap+Inkremental)
Cara lama untuk mencadangkan SAP HANA adalah menggunakan Backint API menggunakan
hdbsql. Backint API mengirim cadangan ke disk staging yang dipetakan ke host SAP HANA melalui iSCSI atau NFS. Dalam kedua pendekatan tersebut, ada pencadangan penuh berkala dan
data yang diambil dalam format cadangan eksklusif, bukan dalam format
blok.
Dukungan pencadangan dan DR untuk berbagai konfigurasi SAP HANA
Backup and DR dapat memvirtualisasi dan melindungi hal berikut:
Sistem penampung tunggal (HANA 1.0 atau 2.0) khusus: Dalam
sistem penampung tunggal, database sistem dan database tenant dilihat sebagai
satu unit dan dikelola sebagai satu unit.
Sistem multi-penampung (HANA 2.0): Beberapa database terisolasi dalam
satu sistem SAP HANA. Ini disebut penampung database multi-tenant. Sistem multi-penampung selalu memiliki tepat satu database sistem
yang digunakan untuk administrasi sistem pusat, dan sejumlah
database multi-tenant (termasuk nol), yang juga disebut database tenant.
Tabel ini mencantumkan semua konfigurasi HANA yang didukung dan metode pencadangan
yang berlaku untuk setiap konfigurasi.
Metode API SavePoint HANA adalah metode pilihan jika tersedia, untuk semua konfigurasi
HANA kecuali untuk penyebaran skala dengan penyimpanan bersama.
Metode backint tersedia untuk semua konfigurasi HANA.
Cadangan log HANA selalu ditangani secara otomatis untuk semua konfigurasi dan
opsi.
Dokumentasi Backup and DR Service untuk SAP HANA Scale-Out
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan
instance SAP HANA Scale-Out dengan Layanan Pencadangan dan DR.
Anda dapat menemukan informasi tambahan di halaman berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 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)"]]
