Configure the backup method for SAP HANA scale-out instances
Stay organized with collections
Save and categorize content based on your preferences.
The policy template and the resource profile that make up the backup plan define
the type of data capture to perform and where to store the captured image.
Based on the required RPOs and backup storage location you must create
Templates and Profiles. The policy part of the template
provides additional backup configuration such as enabling logs backups.
A resource profile defines the backup/recovery appliances that are identified as
the primary (local) appliance hosting the disk pool to use for snapshots,
and a remote appliance for remote backup to be used for disaster recovery
operations. The profile also defines the OnVault pools to be used to send
backup data to Cloud Storage.
Apply policy templates and resource profiles to discovered databases
Once you have discovered one or more applications, apply a policy template
and resource profile to the application to capture data operations.
You can choose between two very different backup methods in the
Application Details & Settings:
Use volume level backup (SAP HANA Savepoint API). Use volume level LVM
snapshots with CBT on Linux to a block-based staging disk. This option
lets you create incremental-forever backups.
Use full+incremental backup (SAP Backint API). This file-dump method
does not support the creation of virtual databases.
You can select this for both block and NFS staging disks, and this method
only supports full backup and physical recovery.
When creating a snapshot policy as part of creating a template,
you have the option of also capturing its log files at a specified frequency.
Details are in Create a policy template
Replicate database logs to a remote backup/recovery appliance or to an
OnVault. Use the logs at the remote site for any database image within
the retention range of the replicated logs. Log replication uses StreamSnap
technology to perform the replication between the local and remote
backup/recovery appliances; log replication goes directly from the local
snapshot pool to the snapshot pool on the remote appliance.
For a log replication job to run, there must be a replication policy
included in the template, and at least one successful replication of
the database must first be completed.
Backup and DR Service documentation for SAP HANA scale-out
This page is one in a series of pages specific to protecting and recovering
SAP HANA scale-out instances with Backup and DR Service.
You can find additional information in the following pages:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 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)"]]