Skip to main content
NetApp solutions for SAP
简体中文版经机器翻译而成，仅供参考。如与英语版出现任何冲突，应以英语版为准。

SnapCenter 操作

贡献者 netapp-nbauer
PDF

本章总结了使用 SnapCenter 执行的备份、还原和恢复、SAP 系统刷新和异步复制操作。

备份操作

备份操作的执行方式与 "在SnapCenter中了解 SAP HANA 快照的备份操作"中所述的相同。

备注 如果未为存储单元配置一致性组，则 SnapCenter 将使用第一个 Snapshot 备份操作创建一致性组和子一致性组。然后将 HANA 数据存储分配给子一致性组。SnapCenter 快照备份列在子一致性组中。

width=601,height=191

width=601,height=205

还原和恢复

还原和恢复操作的执行方式与所述相同 "使用SnapCenter恢复 SAP HANA 数据库"。

异步存储复制

对于 HANA 数据卷，已配置异步存储复制。

宽度=601，高度=180

已使用 MirrorAndVault 策略配置复制。

width=601,height=206

该 MirrorAndVault 策略包含不同的 SnapMirror 标签和保留期。

width=601,height=235

在 SnapCenter 中，已配置一个策略来匹配 ONTAP MirrorAndVault 策略的 SnapMirror 标签 "daily"。

width=378,height=354

使用 ONTAP MirrorAndVault 策略时，SnapCenter 显示分隔的 Vault 和 Mirror 副本，即使快照备份在目标存储中仅可用一次。

宽度=601，高度=294

SAP 系统更新

有关使用 SnapCenter 进行 SAP 系统刷新和克隆操作的更多详细信息，请参见 "利用 SnapCenter 自动执行 SAP HANA 系统复制和克隆操作"。

SnapCenter 工作流

操作详细信息和先决条件在 "使用SnapCenter 更新SAP HANA系统"中进行了描述。具体来说，必须先将目标系统添加到 SnapCenter，然后才能执行第一次刷新/克隆操作。

在克隆工作流程的第一步中，必须提供目标主机和目标 SID。

width=333,height=313

协议选择必须为"FCP"。

width=334,height=312

您可以选择添加 sc-system-refresh.sh 脚本来自动执行恢复操作。

width=352,height=331

下面的屏幕截图显示了克隆工作流的作业日志。

width=379,height=468

以下输出显示了 sc-system-refresh.sh 脚本的日志文件。

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 #

存储视图

在存储层，已创建 FlexClone 卷并将其映射到目标主机。

width=601,height=295

宽度=601，高度=294

主机视图

在主机上，已发现并挂载了新 FlexClone 卷。

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 #