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.
Use the existing template and profile to protect the application or refer to Create a policy template and Create a resource profile to create a new template and profile.
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.
What's Next?
Set application details and settings for SAP HANA databases.
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:
- Backup and DR for SAP HANA scale-out
- Prepare SAP HANA scale-out instances for backup
- Add an SAP HANA scale-out host, and discover and protect its databases
- Configure staging disk format and backup method for SAP HANA scale-out
- Set application details and settings for SAP HANA scale-out instances
- Back up HANA 1+n and HANA scale-out databases
- Restore and recover SAP HANA scale-out instances
- Mount an SAP HANA scale-out backup as a standard mount
- Mount an SAP HANA scale-out backup as a virtual database
- Mount and migrate an SAP HANA scale-out backup for instant recovery to any target