Mengonfigurasi metode pencadangan untuk instance SAP HANA yang di-scale-out
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Template kebijakan dan profil resource yang membentuk rencana pencadangan menentukan jenis pengambilan data yang akan dilakukan dan tempat menyimpan gambar yang diambil.
Berdasarkan RPO yang diperlukan dan lokasi penyimpanan cadangan, Anda harus membuat
Template dan Profil. Bagian kebijakan template
memberikan konfigurasi pencadangan tambahan seperti mengaktifkan pencadangan log.
Profil resource menentukan perangkat cadangan/pemulihan yang diidentifikasi sebagai
perangkat utama (lokal) yang menghosting kumpulan disk untuk digunakan dalam snapshot,
dan perangkat jarak jauh untuk pencadangan jarak jauh yang akan digunakan untuk operasi
pemulihan dari bencana. Profil ini juga menentukan kumpulan OnVault yang akan digunakan untuk mengirim
data cadangan ke Cloud Storage.
Menerapkan template kebijakan dan profil resource ke database yang ditemukan
Setelah Anda menemukan satu atau beberapa aplikasi, terapkan template kebijakan dan profil resource ke aplikasi untuk merekam operasi data.
Anda dapat memilih antara dua metode pencadangan yang sangat berbeda di
Detail & Setelan Aplikasi:
Gunakan pencadangan tingkat volume (SAP HANA Savepoint API). Gunakan snapshot LVM tingkat volume
dengan CBT di Linux ke disk staging berbasis blok. Opsi ini
memungkinkan Anda membuat pencadangan inkremental secara terus-menerus.
Gunakan pencadangan penuh+inkremental (SAP Backint API). Metode dump file ini tidak mendukung pembuatan database virtual.
Anda dapat memilih ini untuk disk penyiapan blok dan NFS, dan metode ini hanya mendukung pencadangan penuh dan pemulihan fisik.
Saat membuat kebijakan snapshot sebagai bagian dari pembuatan template,
Anda memiliki opsi untuk juga merekam file log-nya dengan frekuensi yang ditentukan.
Detailnya ada di Membuat template kebijakan
Mereplikasi log database ke alat pencadangan/pemulihan jarak jauh atau ke
OnVault. Gunakan log di situs jarak jauh untuk semua image database dalam rentang retensi log yang direplikasi. Replikasi log menggunakan teknologi StreamSnap untuk melakukan replikasi antara appliance pencadangan/pemulihan lokal dan jarak jauh; replikasi log dilakukan langsung dari kumpulan snapshot lokal ke kumpulan snapshot di appliance jarak jauh.
Agar tugas replikasi log dapat berjalan, harus ada kebijakan replikasi
yang disertakan dalam template, dan setidaknya satu replikasi database yang berhasil
harus diselesaikan terlebih dahulu.
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\u003eBackup plans for SAP HANA Scale-Out instances are defined by policy templates and resource profiles, which specify data capture methods and storage locations.\u003c/p\u003e\n"],["\u003cp\u003eResource profiles designate primary and remote backup/recovery appliances, as well as OnVault pools for cloud storage, to ensure data availability and disaster recovery.\u003c/p\u003e\n"],["\u003cp\u003eWhen backing up applications there is the option to select between volume-level backup utilizing LVM snapshots or full+incremental backup through the SAP Backint API.\u003c/p\u003e\n"],["\u003cp\u003eDatabase logs can be captured at specified frequencies and replicated to remote appliances or OnVault for added redundancy, using StreamSnap technology for efficient replication.\u003c/p\u003e\n"],["\u003cp\u003eApplying a policy template and resource profile to a discovered application enables the capture of its data operations, and there is an existing policy to use or to create new ones.\u003c/p\u003e\n"]]],[],null,["# Configure the backup method for SAP HANA scale-out instances\n\nThe policy template and the resource profile that make up the backup plan define\nthe type of data capture to perform and where to store the captured image.\nBased on the required RPOs and backup storage location you must create\n**Templates** and **Profiles**. The policy part of the template\nprovides additional backup configuration such as enabling logs backups.\n\nA resource profile defines the backup/recovery appliances that are identified as\nthe primary (local) appliance hosting the disk pool to use for snapshots,\nand a remote appliance for remote backup to be used for disaster recovery\noperations. The profile also defines the OnVault pools to be used to send\nbackup data to Cloud Storage.\n\nUse the existing template and profile to protect the application or\nrefer to [Create a policy template](/backup-disaster-recovery/docs/create-plan/create-template) and [Create a resource profile](/backup-disaster-recovery/docs/concepts/resource-profiles#create-profile) to\ncreate a new template and profile.\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\nApply policy templates and resource profiles to discovered databases\n--------------------------------------------------------------------\n\nOnce you have discovered one or more applications, apply a policy template\nand resource profile to the application to capture data operations.\n\nYou can choose between two very different backup methods in the\n**Application Details \\& Settings**:\n\n- **Use volume level backup (SAP HANA Savepoint API).** Use volume level LVM\n snapshots with CBT on Linux to a block-based staging disk. This option\n lets you create incremental-forever backups.\n\n- **Use full+incremental backup (SAP Backint API).** This file-dump method\n does not support the creation of virtual databases.\n You can select this for both block and NFS staging disks, and this method\n only supports full backup and physical recovery.\n\n | **Note:** If there is third party backup outside the scheduled backups, then database restore will fail. Manual recovery can be done by rebuilding the catalog. Force a full backup whenever the third party backup is run.\n\nWhen creating a snapshot policy as part of creating a template,\nyou have the option of also capturing its log files at a specified frequency.\nDetails are in [Create a policy template](/backup-disaster-recovery/docs/create-plan/create-template)\n\nReplicate database logs to a remote backup/recovery appliance or to an\nOnVault. Use the logs at the remote site for any database image within\nthe retention range of the replicated logs. Log replication uses StreamSnap\ntechnology to perform the replication between the local and remote\nbackup/recovery appliances; log replication goes directly from the local\nsnapshot pool to the snapshot pool on the remote appliance.\nFor a log replication job to run, there must be a replication policy\nincluded in the template, and at least one successful replication of\nthe database must first be completed.\n\nWhat's Next?\n------------\n\n[Set application details and settings for SAP HANA databases.](/backup-disaster-recovery/docs/backup/app-details-settings-sap-hana)\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)"]]
