Mencadangkan instance HANA 1+n dan penyebaran skala HANA
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini mencakup informasi tentang melindungi HANA 1+n dan scale-out HANA.
Melindungi HANA 1+n
Untuk melindungi cluster replikasi HANA 1+n sebagai satu aplikasi, aplikasi
memiliki host cluster sebagai sid name_cluster setelah penemuan aplikasi. Misalnya, jika sr1 adalah instance HANA, maka nama aplikasi adalah sr1 dan nama host adalah sr1_cluster dalam daftar App Manager Applications.
Tujuan pencadangan log HANA harus dibagikan di antara dua node. Saat failover
terjadi, pencadangan database dan log akan otomatis di-failover ke instance
primer saat ini, dan pencadangan log dilakukan dari instance primer saat ini, yang mencatat
log terakhir dari instance primer lama serta log baru dari instance primer baru. Ikuti langkah-langkah persiapan di Menyiapkan database SAP HANA untuk perlindungan.
HANA 1+n selalu ditemukan sebagai aplikasi cluster yang berisi semua detail node dalam metadata. Sebaiknya jalankan penemuan paksa setelah ada perubahan pada konfigurasi node cluster, seperti setelah menambahkan atau menghapus node dari cluster. Jika node dihapus atau ditambahkan setelah penemuan dan perlindungan, konfigurasi tidak akan diperbarui secara otomatis dalam metadata Backup dan DR, dan dapat menyebabkan masalah pencadangan.
Prasyarat untuk melindungi instance dan database SAP HANA 1+n
Sebelum melindungi instance SAP HANA, pastikan hal berikut:
Jika host telah mengonfigurasi IP virtual, tambahkan hanya IP virtual dan nama host
host utama selama penemuan.
Agen Backup and DR harus diinstal di semua node.
Port harus dibuka di host untuk mengizinkan komunikasi di port 5106.
Hal ini memerlukan aturan firewall traffic masuk dengan appliance pencadangan/pemulihan
sebagai sumber, host yang menjalankan agen sebagai target, dan port target
adalah 5106. Selain itu, tidak perlu menambahkan port 5106 ke aturan ingress default yang dibuat untuk appliance, karena hal ini menentukan appliance sebagai target.
Lokasi pencadangan log HANA harus ditetapkan di NFS bersama.
Melindungi penyebaran skala HANA
Prasyarat untuk melindungi instance penyebaran skala SAP HANA
Sebelum melindungi instance penyebaran skala SAP HANA, pastikan hal berikut telah selesai:
Jika host telah mengonfigurasi IP virtual, tambahkan hanya IP virtual dan nama host terkait dari host utama selama penemuan.
Agen Backup and DR harus diinstal di semua node.
Port harus dibuka di host untuk mengizinkan komunikasi di port 5106.
Hal ini memerlukan aturan firewall traffic masuk dengan appliance pencadangan/pemulihan
sebagai sumber, host yang menjalankan agen sebagai target, dan port target
adalah 5106. Selain itu, tidak perlu menambahkan port 5106 ke aturan ingress default yang dibuat untuk appliance, karena hal ini menentukan appliance sebagai target.
Untuk pencadangan berbasis file backint—Penuh+Inkremental—lokasi pencadangan log HANA harus disetel ke bersama—NFS. Lihat
Menambahkan host ke konsol pengelolaan.
Untuk perlindungan snapshot penyimpanan
Volume data dan log tidak dibagikan di semua node
Volume data dan log dikelola oleh pengelola volume logis (LVM)
Pastikan direktori mnt000* ada di titik pemasangan lokal untuk mengidentifikasi node primer dan sekunder
Dokumentasi Backup and DR Service untuk penyebaran skala SAP HANA
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan instance scale-out SAP HANA dengan Layanan Backup 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-11 UTC."],[[["\u003cp\u003eThis page outlines the process of protecting both HANA 1+n replication clusters and HANA scale-out instances using Backup and DR Service.\u003c/p\u003e\n"],["\u003cp\u003eFor HANA 1+n, the cluster is recognized as a single application post-discovery, and log backups automatically failover to the current primary node.\u003c/p\u003e\n"],["\u003cp\u003eProtecting either type requires the Backup and DR agent to be installed on all nodes and for port 5106 to be open for communication between the appliance and the hosts.\u003c/p\u003e\n"],["\u003cp\u003eHANA log backup locations must be shared (NFS) between nodes for both HANA 1+n and scale-out configurations when utilizing file-based backups.\u003c/p\u003e\n"],["\u003cp\u003eForce discovery is recommended after changes to HANA 1+n cluster node configurations to prevent backup issues, and changes should be tracked with logical volume manager change block tracking.\u003c/p\u003e\n"]]],[],null,["# Back up HANA 1+n and HANA scale-out instances\n\nThis page includes information about protecting HANA 1+n and HANA scale-out.\n\nProtect HANA 1+n\n----------------\n\nTo protect a HANA 1+n replication cluster as a single application, the application\nhas the cluster host as sid `name_cluster` after application discovery. For\nexample, if sr1 is the HANA instance, then the application name is sr1 and the\nhostname is sr1_cluster in the **App Manager Applications** list.\n\nThe HANA log backup destination must be shared between two nodes. When failover\noccurs, the database and log backup automatically fails over to the current\nprimary, and log backups are performed from the current primary, capturing the\nlast logs from the old primary as well as new logs from the new primary. Follow\nthe preparation steps in\n[Prepare your SAP HANA databases for protection](/backup-disaster-recovery/docs/configuration/prepare-hana).\n\nHANA 1+n is always discovered as cluster application containing all node\ndetails in the metadata. It is a good idea to run a force discovery after any\nchanges to cluster node configuration---such as after adding or deleting a\nnode from the cluster. If a node is removed or added after discovery and\nprotection, the configuration does not be updated automatically in\nBackup and DR metadata, and may cause backup issues.\n| **Note:** With the failover of the HANA database from primary to secondary and back, the next database backup is low-splash and takes more time to get the incremental changes.\n\n### Prerequisites for protecting SAP HANA 1+n instances and databases\n\nBefore protecting SAP HANA instances, ensure the following:\n\n- If hosts have virtual IPs configured, add only the virtual IP and hostname of the primary host during discovery.\n- The Backup and DR agent must be installed on all nodes.\n- Ports need to be opened on the hosts to allow communication on port 5106. This requires an ingress firewall rule where the backup/recovery appliance is the source, the host running the agent is the target and the target port is 5106. Also, there is no need to add port 5106 to the default ingress rule created for the appliance, as this specifies the appliance as the target.\n- HANA log backup location must be set on shared---NFS.\n\n| **Note:** Activate logical volume manager change block tracking on all the nodes of SAP HANA scale-out cluster by running `/opt/act/cbt/bin/cbt_activate.sh` on the command line as a root user. Verify that logical volume manager change block tracking is activated by running `pgrep cbt`---this should return two processes running for change block tracking.\n\nProtect HANA scale-out\n----------------------\n\n### Prerequisites for protecting SAP HANA scale-out instances\n\nBefore protecting SAP HANA scale-out instances, be sure that the following is complete:\n\n- If hosts have virtual IPs configured, add only the virtual IP and the associated hostname of the primary host during discovery.\n- The Backup and DR agent must be installed on all nodes.\n- Ports need to be opened on the hosts to allow communication on port 5106. This requires an ingress firewall rule where the backup/recovery appliance is the source, the host running the agent is the target and the target port is 5106. Also, there is no need to add port 5106 to the default ingress rule created for the appliance, as this specifies the appliance as the target.\n- For backint file based---Full+Incremental---backup, the HANA log backup location must be set to shared---NFS. See [Add the host to the management console](/backup-disaster-recovery/docs/configuration/otherdb-add-host).\n- For storage snapshot protection\n\n - Data and log volume are non-shared across all nodes\n - Data and log volumes are managed by logical volume manager (LVM)\n - Ensure mnt000\\* directories exist on the local mount points to identify the primary and secondary nodes\n\n | **Note:** The discovered SAP HANA instance shows up under application list with: Application (HANA sid name): Hostname and Friendly path (HANA sid name)_cluster(site id)_(HANA hardware id).\n\n Follow the setup procedures in\n [Prepare your SAP HANA databases for protection](/backup-disaster-recovery/docs/configuration/prepare-sap-hana-scaleout).\n\n| **Note:** Activate logical volume manager change block tracking on all the nodes of SAP HANA scale-out cluster by running `/opt/act/cbt/bin/cbt_activate.sh` on the command line as a root user. Verify that logical volume manager change block tracking is activated by running `pgrep cbt`---this should return two processes running for change block tracking.\n| **Note:** If you are protecting data on a HANA replication cluster, any reboot of the primary HANA node results in a role switch where the secondary node becomes the new primary node. Backup jobs always run from the primary HANA node. If there is a HANA failover to the secondary node, the first backup after the failover is a full copy because CBT from the old primary node is not available on the new primary (old secondary) node.\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)"]]
