Skip to main content
NetApp Solutions SAP

SnapCenter backup operations

Contributors kevin-hoke netapp-mschoen
PDFs

You can create an on-demand Snapshot backup and an on-demand block integrity check operation.

Create an on-demand Snapshot backup

Follow these steps to create on-demand Snapshot backups.

  1. In the Resource view, select the resource and double-click the line to switch to the Topology view.

    The Resource Topology view provides an overview of all available backups that have been created by using SnapCenter. The top area of this view displays the backup topology showing the backups on the primary storage (local copies) and, if available, on the off-site backup storage (vault copies).

  2. In the top row, select the Back up Now icon to start an on-demand backup.

    Figure showing input/output dialog or representing written content

  3. From the drop-down list, select the backup policy LocalSnap, and then click Backup to start the on-demand backup.

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

    A log of the previous five jobs is shown in the Activity area at the bottom of the Topology view.

  4. The job details are shown when clicking the job’s activity line in the Activity area. You can open a detailed job log by clicking View Logs

    Figure showing input/output dialog or representing written content

    When the backup is finished, a new entry is shown in the topology view. The backup names follow the same naming convention as the Snapshot name defined in the section “Configure and protect a HANA resource”.

    You must close and reopen the topology view to see the updated backup list.

    Figure showing input/output dialog or representing written content

    In the SAP HANA backup catalog, the SnapCenter backup name is stored as a Comment field as well as External Backup ID (EBID). This is shown in the following figure for the system database and in the next figure for the tenant database PFX.

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

On the FSx for ONTAP file system, you can list the Snapshot backups by connecting to the console of the SVM.

sapcc-hana-svm::> snapshot show -volume PFX_data_mnt00001                                        ---Blocks---
Vserver  Volume   Snapshot                                  Size Total% Used%
-------- -------- ------------------------------------- -------- ------ -----
sapcc-hana-svm
         PFX_data_mnt00001
                  SnapCenter_hana-1_LocalSnap_Hourly_02-22-2022_12.08.54.4516
                                                         126.6MB     0%    2%
sapcc-hana-svm::>

Create an on-demand block integrity check operation

An on-demand block integrity check operation is executed in the same way as a Snapshot backup job, by selecting the policy BlockIntegrityCheck. When scheduling backups using this policy, SnapCenter creates a standard SAP HANA file backup for the system and tenant databases.

Figure showing input/output dialog or representing written content

Figure showing input/output dialog or representing written content

SnapCenter does not display the block integrity check in the same manner as Snapshot copy-based backups. Instead, the summary card shows the number of file-based backups and the status of the previous backup.

Figure showing input/output dialog or representing written content

The SAP HANA backup catalog shows entries for both the system and the tenant databases. The following figures show the SnapCenter block integrity check in the backup catalog of the system and the tenant database.

Figure showing input/output dialog or representing written content

Figure showing input/output dialog or representing written content

A successful block integrity check creates standard SAP HANA data backup files. SnapCenter uses the backup path that has been configured with the HANA database for file-based data backup operations.

hana-1:~ # ls -al /backup/data/*
/backup/data/DB_PFX:
total 7665384
drwxr-xr-- 2 pfxadm sapsys       4096 Feb 22 12:56 .
drwxr-xr-x 4 pfxadm sapsys       4096 Feb 21 15:02 ..
-rw-r----- 1 pfxadm sapsys     155648 Feb 21 15:02 COMPLETE_DATA_BACKUP_databackup_0_1
-rw-r----- 1 pfxadm sapsys   83894272 Feb 21 15:02 COMPLETE_DATA_BACKUP_databackup_2_1
-rw-r----- 1 pfxadm sapsys 3825213440 Feb 21 15:02 COMPLETE_DATA_BACKUP_databackup_3_1
-rw-r----- 1 pfxadm sapsys     155648 Feb 22 12:55 SnapCenter_SnapCenter_hana-1_BlockIntegrityCheck_Weekly_02-22-2022_12.55.18.7966_databackup_0_1
-rw-r----- 1 pfxadm sapsys   83894272 Feb 22 12:55 SnapCenter_SnapCenter_hana-1_BlockIntegrityCheck_Weekly_02-22-2022_12.55.18.7966_databackup_2_1
-rw-r----- 1 pfxadm sapsys 3825213440 Feb 22 12:56 SnapCenter_SnapCenter_hana-1_BlockIntegrityCheck_Weekly_02-22-2022_12.55.18.7966_databackup_3_1
/backup/data/SYSTEMDB:
total 7500880
drwxr-xr-- 2 pfxadm sapsys       4096 Feb 22 12:55 .
drwxr-xr-x 4 pfxadm sapsys       4096 Feb 21 15:02 ..
-rw-r----- 1 pfxadm sapsys     159744 Feb 21 15:01 COMPLETE_DATA_BACKUP_databackup_0_1
-rw-r----- 1 pfxadm sapsys 3825213440 Feb 21 15:02 COMPLETE_DATA_BACKUP_databackup_1_1
-rw-r----- 1 pfxadm sapsys     159744 Feb 22 12:55 SnapCenter_SnapCenter_hana-1_BlockIntegrityCheck_Weekly_02-22-2022_12.55.18.7966_databackup_0_1
-rw-r----- 1 pfxadm sapsys 3825213440 Feb 22 12:55 SnapCenter_SnapCenter_hana-1_BlockIntegrityCheck_Weekly_02-22-2022_12.55.18.7966_databackup_1_1
hana-1:~ #