SnapCenter operations
Contributors
Suggest changes
PDFs
This chapter summarizes the backup, restore and recovery, SAP system refresh and asynchronous replication operations with SnapCenter.
Backup operations
Backup operations are executed in the same way as described in Learn about backup operations for SAP HANA Snapshot in SnapCenter.
|
If no consistency group is configured for the storage unit, SnapCenter creates a consistency group and a child consistency group with the first Snapshot backup operation. The HANA data storage is then assigned to the child consistency group. SnapCenter Snapshot backups are listed within the child consistency group. |
Restore and recovery
Restore and recovery operations are executed in the same way as described Restore and recover SAP HANA databases with SnapCenter.
Asynchronous storage replication
For the HANA data volume, an asynchronous storage replication has been configured.
The replication has been configured with the MirrorAndVault policy.
The MirrorAndVault policy includes different SnapMirror labels and retentions.
In SnapCenter a policy has been configured to match the SnapMirror label "daily" of the ONTAP MirrorAndVault policy.
When using the ONTAP MirrorAndVault policy, SnapCenter shows separated Vault and Mirror copies, even though the Snapshot backups are only available once at the target storage.
SAP system refresh
More detailed information on SAP system refresh and cloning operations using SnapCenter can be found at Automating SAP HANA System Copy and Clone Operations with SnapCenter.
SnapCenter workflow
Operation details and pre-requisites are described in SAP HANA system refresh with SnapCenter. Specifically, the target system must be added to SnapCenter before you can execute the first refresh/cloning operation.
With the first step in the cloning workflow the target host and target SID must be provided.
Protocol selection must be "FCP".
Optionally you can add the sc-system-refresh.sh script to automate the recovery operation.
The below screenshot shows the job log of the cloning workflow.
The following output shows the log file of the sc-system-refresh.sh script.
sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # tail -100 sc-system-refresh-QM1.log 20260212092224###sapcc-hana-tst-03###sc-system-refresh.sh: ********************************************************************************** 20260212092224###sapcc-hana-tst-03###sc-system-refresh.sh: Script version: 3.0 20260212092224###sapcc-hana-tst-03###sc-system-refresh.sh: ******************* Starting script: recovery operation ************************** 20260212092224###sapcc-hana-tst-03###sc-system-refresh.sh: Recover system database. 20260212092224###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/HDB22/exe/Python/bin/python /usr/sap/QM1/HDB22/exe/python_support/recoverSys.py --command "RECOVER DATA USING SNAPSHOT CLEAR LOG" 20260212092245###sapcc-hana-tst-03###sc-system-refresh.sh: Wait until SAP HANA database is started .... 20260212092246###sapcc-hana-tst-03###sc-system-refresh.sh: Status: GRAY 20260212092256###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260212092306###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260212092317###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260212092327###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260212092337###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260212092347###sapcc-hana-tst-03###sc-system-refresh.sh: Status: GREEN 20260212092347###sapcc-hana-tst-03###sc-system-refresh.sh: HANA system database started. 20260212092347###sapcc-hana-tst-03###sc-system-refresh.sh: Checking connection to system database. 20260212092347###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/SYS/exe/hdb/hdbsql -U QM1KEY 'select * from sys.m_databases;' 20260212092348###sapcc-hana-tst-03###sc-system-refresh.sh: Succesfully connected to system database. 20260212092348###sapcc-hana-tst-03###sc-system-refresh.sh: Tenant databases to recover: BM1 20260212092348###sapcc-hana-tst-03###sc-system-refresh.sh: Found inactive tenants(BM1) and starting recovery 20260212092348###sapcc-hana-tst-03###sc-system-refresh.sh: Recover tenant database BM1. 20260212092348###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/SYS/exe/hdb/hdbsql -U QM1KEY RECOVER DATA FOR BM1 USING SNAPSHOT CLEAR LOG 20260630072033###sapcc-hana-tst-03###sc-system-refresh.sh: ********************************************************************************** 20260630072033###sapcc-hana-tst-03###sc-system-refresh.sh: Script version: 3.0 20260630072033###sapcc-hana-tst-03###sc-system-refresh.sh: ******************* Starting script: recovery operation ************************** 20260630072033###sapcc-hana-tst-03###sc-system-refresh.sh: Recover system database. 20260630072033###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/HDB22/exe/Python/bin/python /usr/sap/QM1/HDB22/exe/python_support/recoverSys.py --command "RECOVER DATA USING SNAPSHOT CLEAR LOG" 20260630072101###sapcc-hana-tst-03###sc-system-refresh.sh: Wait until SAP HANA database is started .... 20260630072101###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260630072111###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260630072122###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260630072132###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260630072142###sapcc-hana-tst-03###sc-system-refresh.sh: Status: YELLOW 20260630072152###sapcc-hana-tst-03###sc-system-refresh.sh: Status: GREEN 20260630072152###sapcc-hana-tst-03###sc-system-refresh.sh: HANA system database started. 20260630072152###sapcc-hana-tst-03###sc-system-refresh.sh: Checking connection to system database. 20260630072152###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/SYS/exe/hdb/hdbsql -U QM1KEY 'select * from sys.m_databases;' DATABASE_NAME,DESCRIPTION,ACTIVE_STATUS,ACTIVE_STATUS_DETAILS,OS_USER,OS_GROUP,RESTART_MODE,FALLBACK_SNAPSHOT_CREATE_TIME "SYSTEMDB","SystemDB-QM1-22","YES","ACTIVE","","","DEFAULT",? "QM1","QM1-22","NO","ACTIVE","","","DEFAULT",? 2 rows selected (overall time 18.501 msec; server time 800 usec) 20260630072153###sapcc-hana-tst-03###sc-system-refresh.sh: Succesfully connected to system database. 20260630072153###sapcc-hana-tst-03###sc-system-refresh.sh: Tenant databases to recover: QM1 20260630072153###sapcc-hana-tst-03###sc-system-refresh.sh: Found inactive tenants(QM1) and starting recovery 20260630072153###sapcc-hana-tst-03###sc-system-refresh.sh: Recover tenant database QM1. 20260630072153###sapcc-hana-tst-03###sc-system-refresh.sh: /usr/sap/QM1/SYS/exe/hdb/hdbsql -U QM1KEY RECOVER DATA FOR QM1 USING SNAPSHOT CLEAR LOG 0 rows affected (overall time 25.154634 sec; server time 25.151309 sec) 20260630072219###sapcc-hana-tst-03###sc-system-refresh.sh: Checking availability of Indexserver for tenant QM1. 20260630072219###sapcc-hana-tst-03###sc-system-refresh.sh: Recovery of tenant database QM1 succesfully finished. 20260630072219###sapcc-hana-tst-03###sc-system-refresh.sh: Status: GREEN 20260630072219###sapcc-hana-tst-03###sc-system-refresh.sh: ******************* Finished script: recovery operation ************************** sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh #
Storage view
At the storage layer the FlexClone volume has been created and mapped to the target host.
Host view
At the host the new FlexClone volume has been discovered and mounted.
sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # sanlun lun show controller(7mode/E-Series)/ device host lun vserver(cDOT/FlashRay) lun-pathname filename adapter protocol size product --------------------------------------------------------------------------------------------------------------------------- a30-hana-primary BM1_data_mnt00001_1_Clone_0630260725394127 /dev/sdab host21 FCP 250g cDOT a30-hana-primary BM1_data_mnt00001_1_Clone_0630260725394127 /dev/sdaa host21 FCP 250g cDOT a30-hana-primary BM1_data_mnt00001_1_Clone_0630260725394127 /dev/sdw host20 FCP 250g cDOT a30-hana-primary BM1_data_mnt00001_1_Clone_0630260725394127 /dev/sdm host20 FCP 250g cDOT a30-hana-primary QM1_shared_1 /dev/sdz host21 FCP 250g cDOT a30-hana-primary QM1_log_mnt00001_1 /dev/sdy host21 FCP 250g cDOT a30-hana-primary QM1_data_mnt00001_1 /dev/sdx host21 FCP 250g cDOT a30-hana-primary QM1_shared_1 /dev/sdv host21 FCP 250g cDOT a30-hana-primary QM1_log_mnt00001_1 /dev/sds host21 FCP 250g cDOT a30-hana-primary QM1_data_mnt00001_1 /dev/sdq host21 FCP 250g cDOT a30-hana-primary QM1_shared_1 /dev/sdh host20 FCP 250g cDOT a30-hana-primary QM1_log_mnt00001_1 /dev/sdg host20 FCP 250g cDOT a30-hana-primary QM1_data_mnt00001_1 /dev/sdf host20 FCP 250g cDOT a30-hana-primary QM1_shared_1 /dev/sdk host20 FCP 250g cDOT a30-hana-primary QM1_log_mnt00001_1 /dev/sdj host20 FCP 250g cDOT a30-hana-primary QM1_data_mnt00001_1 /dev/sdi host20 FCP 250g cDOT sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # multipath -ll 3600a098038323537342b596e5566674d dm-7 NETAPP,LUN C-Mode size=250G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 20:0:7:3 sdw 65:96 active ready running |- 20:0:9:3 sdm 8:192 active ready running |- 21:0:9:3 sdaa 65:160 active ready running `- 21:0:10:3 sdab 65:176 active ready running a30-hana-primary-QM1-data-mnt00001 (3600a098038323537342b596e55666739) dm-4 NETAPP,LUN C-Mode size=250G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 20:0:7:0 sdf 8:80 active ready running |- 20:0:9:0 sdi 8:128 active ready running |- 21:0:9:0 sdq 65:0 active ready running `- 21:0:10:0 sdx 65:112 active ready running a30-hana-primary-QM1-log-mnt00001 (3600a0980383235324a245a4749384948) dm-6 NETAPP,LUN C-Mode size=250G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 20:0:7:1 sdg 8:96 active ready running |- 20:0:9:1 sdj 8:144 active ready running |- 21:0:9:1 sds 65:32 active ready running `- 21:0:10:1 sdy 65:128 active ready running a30-hana-primary-QM1-shared (3600a098038323537342b596e5566672d) dm-5 NETAPP,LUN C-Mode size=250G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 20:0:7:2 sdh 8:112 active ready running |- 20:0:9:2 sdk 8:160 active ready running |- 21:0:9:2 sdv 65:80 active ready running `- 21:0:10:2 sdz 65:144 active ready running sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh # df -h | grep hana /dev/mapper/a30-hana-primary-QM1-shared 250G 18G 233G 7% /hana/shared /dev/mapper/a30-hana-primary-QM1-log-mnt00001 250G 3.5G 247G 2% /hana/log/QM1/mnt00001 /dev/mapper/3600a098038323537342b596e5566674d 250G 8.2G 242G 4% /hana/data/QM1/mnt00001 sapcc-hana-tst-03:/mnt/sapcc-share/SAP-System-Refresh #