Manage and monitor backed up SAP HANA databases
This article describes common tasks for managing and monitoring SAP HANA databases that are running on an Azure virtual machine (VM) and that are backed up to an Azure Backup Recovery Services vault by the Azure Backup service. You'll learn how to monitor jobs and alerts, trigger an on-demand backup, edit policies, stop and resume database protection and unregister a VM from backups.
If you haven't configured backups yet for your SAP HANA databases, see Back up SAP HANA databases on Azure VMs.
Monitor manual backup jobs in the portal
Azure Backup shows all manually triggered jobs in the Backup jobs section on Azure portal.
The jobs you see in this portal include database discovery and registering, and backup and restore operations. Scheduled jobs, including log backups aren't shown in this section. Manually triggered backups from the SAP HANA native clients (Studio/ Cockpit/ DBA Cockpit) also don't show up here.
View backup alerts
Alerts are an easy means of monitoring backups of SAP HANA databases. Alerts help you focus on the events you care about the most without getting lost in the multitude of events that a backup generates. Azure Backup allows you to set alerts, and they can be monitored as follows:
Sign in to the Azure portal.
On the vault dashboard, select Backup Alerts.
You will be able to see the alerts:
Click on the alerts to see more details:
Today, Azure Backup allows the sending of alerts through email. These alerts are:
- Triggered for all backup failures.
- Consolidated at the database level by error code.
- Sent only for a database's first backup failure.
Azure Backup makes management of a backed-up SAP HANA database easy with an abundance of management operations that it supports. These operations are discussed in more detail in the following sections.
Run an ad-hoc backup
Backups run in accordance with the policy schedule. You can run a backup on-demand as follows:
- In the vault menu, click Backup items.
- In Backup Items, select the VM running the SAP HANA database, and then click Backup now.
- In Backup Now, use the calendar control to select the last day that the recovery point should be retained. Then click OK.
- Monitor the portal notifications. You can monitor the job progress in the vault dashboard > Backup Jobs > In progress. Depending on the size of your database, creating the initial backup may take a while.
Run SAP HANA native client backup on a database with Azure backup enabled
If you want to take a local backup (using HANA Studio / Cockpit) of a database that's being backed up with Azure Backup, do the following:
- Wait for any full or log backups for the database to finish. Check the status in SAP HANA Studio/ Cockpit.
- Disable log backups, and set the backup catalog to the file system for relevant database.
- To do this, double-click systemdb > Configuration > Select Database > Filter (Log).
- Set enable_auto_log_backup to No.
- Set log_backup_using_backint to False.
- Take an on-demand full backup of the database.
- Wait for the full backup and catalog backup to finish.
- Revert the previous settings back to those for Azure:
- Set enable_auto_log_backup to Yes.
- Set log_backup_using_backint to True.
You can change the underlying policy for an SAP HANA backup item.
In the vault dashboard, go to Backup items:
Choose SAP HANA in Azure VM
Choose the backup item whose underlying policy you want to change
Click on the existing Backup policy
Change the policy, choosing from the list. Create a new backup policy if needed.
Save the changes
Policy modification will impact all the associated Backup Items and trigger corresponding configure protection jobs.
Any change in the retention period will be applied retrospectively to all the older recovery points besides the new ones.
Incremental backup policies cannot be used for SAP HANA databases. Incremental backup is not currently supported for these databases.
Stop protection for an SAP HANA database
You can stop protecting an SAP HANA database in a couple of ways:
- Stop all future backup jobs and delete all recovery points.
- Stop all future backup jobs and leave the recovery points intact.
If you choose to leave recovery points, keep these details in mind:
- All recovery points will remain intact forever, all pruning shall stop at stop protection with retain data.
- You will be charged for the protected instance and the consumed storage. For more information, see Azure Backup pricing.
- If you delete a data source without stopping backups, new backups will fail.
To stop protection for a database:
On the vault dashboard, select Backup Items.
Under Backup Management Type, select SAP HANA in Azure VM
Select the database for which you want to stop protection on:
On the database menu, select Stop backup.
On the Stop Backup menu, select whether to retain or delete data. If you want, provide a reason and comment.
Select Stop backup.
Resume protection for an SAP HANA database
When you stop protection for the SAP HANA database, if you select the Retain Backup Data option, you can later resume protection. If you don't retain the backed-up data, you will not be able to resume protection.
To resume protection for an SAP HANA database:
Open the backup item and select Resume backup.
On the Backup policy menu, select a policy, and then select Save.
Upgrading from SAP HANA 1.0 to 2.0
Learn how to continue backup for an SAP HANA database after upgrading from SAP HANA 1.0 to 2.0.
Upgrading without a SID change
Learn how to continue backup of an SAP HANA database whose SID has not changed after upgrade.
Unregister an SAP HANA database
Unregister an SAP HANA instance after you disable protection but before you delete the vault:
On the vault dashboard, under Manage, select Backup Infrastructure.
Select the Backup Management type as Workload in Azure VM
In Protected Servers, select the instance to unregister. To delete the vault, you must unregister all servers/ instances.
Right-click the protected instance and select Unregister.