SAP HANA 2.0系统复制教程：实现高可用性的关键步骤

需积分: 11 124 浏览量更新于2024-07-16 收藏 4.68MB PDF 举报

本文档是SAP官方发布的"How to Perform System Replication for SAP HANA 2.0"，针对的是SAP HANA 2.0 SPS00版本及SAP Business Analytics解决方案中的HANA数据库。它旨在为企业提供业务连续性的支持，确保关键业务系统的高可用性，即使在面对故障时也能维持服务。系统复制是SAP HANA的一项重要功能，允许用户在同一个数据中心或跨两个数据中心之间复制HANA系统，从而增强灾难恢复能力。该指南详细阐述了如何在步骤基础上设置和管理SAP HANA的系统复制，确保数据的一致性和可靠性。通过遵循此文档，管理员可以实现以下关键知识点： 1. **背景与目标**：文档强调了在商业环境中保持业务连续性的必要性，尤其是在高可用性和灾难恢复策略中扮演的核心角色。SAP HANA的系统复制功能是实现这一目标的关键手段。 2. **适用范围**：这份指南适用于SAP HANA 2.0 SP00版本以及SAP Business Analytics Appliance，特别适用于2017年1月的SAP HANA 5.0版。它还提供了联系人信息，以便在需要更多信息时获取技术支持。 3. **版权与授权**：文档声明所有权利归SAP SE所有，未经明确许可，不得复制或传输。同时，提到某些软件产品包含第三方供应商的专有组件，如Microsoft的Windows、Excel等。 4. **操作步骤与技术细节**：文章将指导读者进行系统的逐步骤配置，可能涉及的内容包括但不限于选择复制模式（例如实时复制或异步复制）、设置复制周期、验证数据一致性、网络和存储配置、以及监控和维护复制关系。 5. **注意事项**：文档提醒读者，SAP HANA的系统复制可能会涉及到第三方软件的集成，如IBM DB2等，因此在实施过程中可能需要考虑兼容性和集成策略。 6. **安全与合规**：在设置系统复制时，应遵循数据保护法规和最佳实践，确保数据的安全性和隐私合规。通过阅读并遵循这份文档，企业能够有效地提升SAP HANA系统的可用性和容错能力，为业务连续性做好充分准备。同时，了解文档中涉及的技术细节，有助于IT团队更好地应对突发情况，确保业务不受中断。

How To System Replication for SAP HANA

 The primary and secondary systems are both installed and configured. You

have verified that both are independently up and running.

 In HANA 2.0 the System PKI SSFS key and data files were copied from the

primary to the secondary site according to this SAP Note 2369981. The files

can be found here:

$DIR_INSTANCE/../global/security/rsecssfs/data/SSFS_<SID>.DAT

$DIR_INSTANCE/../global/security/rsecssfs/key/SSFS_<SID>.KEY

 The number of nodes in the secondary system has to be equal to the number

of active nodes in the primary system. (As of HANA 1.0 SPS06 the secondary

system does not need to have standby nodes.)

 All configuration steps have to be executed on the master name server node;

for SAP HANA Multitenant Database Containers this means on the System

DB (and not on the tenant DBs).

 The SAP HANA software version of the secondary has to be equal to or newer

than the one on the primary; however, if you want to make use of a read

enabled secondary system in an Active/Active (read enabled) configuration,

the SAP HANA software versions have to be identical.

 The secondary system must have the same SAP system ID, <SID>, and

instance number as the primary system. The primary replicates all relevant

license information to the secondary.

 System replication between two systems on the same host is not supported.

 Changes to the ini file configuration parameters made on one system

should be duplicated on the other system.

As of HANA 1.0 SPS06 the configuration parameter checker reports

differences between primary and secondary parameter settings (generating

alerts in the SAP HANA studio). As of HANA 1.0 SPS12 INI parameters can

be replicated to the secondary system.

 The required ports must be available. The same <instance number> is

used for primary and secondary systems. The <instance number>+1 must

be free on both systems, because this port range is used for system

replication communication.

 An initial data backup or snapshot must be performed on the primary before

the system replication can be activated. In SAP HANA Multitenant Database

Containers all databases must have been backed up, i. e. the system DB as

well as all tenant DBs

For additional port specific information in Multitenant Database Containers running in System Replication please refer to

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf - section:

SAP HANA System Replication with

Multitenant Database Containers

In an already running SAP HANA system replication for a Multitenant Database Container HANA, every newly created

tenant DB has to be backed up for the replication to start.

How To System Replication for SAP HANA

4.2 Distance between data centers

System replication offers synchronous and asynchronous replication modes to

accommodate network latency.

If the distance between your sites is less than 100 km you can use a synchronous

replication mode: SYNC or SYNCMEM.

For all data centers that are more than 100 km apart, the asynchronous replication

mode ASYNC is recommended.

Note

Depending on latency, data volume, volume of changed data records, this

could lead to loss of changes because of missing redo logs. Please also

consider monitoring requirements for asynchronous mode.

4.3 Use secondary site for DEV/QA system

For system replication landscapes not running in an Active/Active (read enabled)

configuration (with operation mode “logreplay_readaccess”) it is possible to

make use of the secondary site for running DEV/QA systems while the primary

system is in production. However, for Active/Active configured systems, this is

currently not supported.

The following prerequisites must be taken into account:

 Additional independent disk volume is needed for DEV/QA systems; since

the secondary requires the same I/O capacity as the primary the additional

systems must not have a negative impact on the secondary’s I/O – thus it is

recommended to have a separated storage infrastructure for each system.

 The SIDs and instance numbers have to be different for DEV/QA. The

<instance number>+1 of the productive system must not be used but

must be free on both sites, because this port range is used for system

replication communication.

 Preload of tables must be switched off on the secondary system:

global.ini/[system_replication]-> preload_column_tables=false

 The takeover process will take longer as no data is preloaded to memory on

the secondary site (could still meet SLAs for disaster recovery)

 DEV/QA systems need to be shut down in case of a takeover.

 Additionally, the global allocation limit on the secondary system must be set

in a way that the available memory covers the memory needed by the

secondary system as well as the DEV/QA systems:

global.ini/[memorymanager]-> global_allocation_limit

As of HANA 1.0 SPS11 the configured operation mode influences the

memory size required on the secondary:

How To System Replication for SAP HANA

operation mode

memory needed on secondary

delta_datashipping

minimum 64 GB

row store size

+ 20 GB (if this sum is

higher)

logreplay

size of loaded column tables (in-memory)

+ row store size

+ 50 GB

logreplay_readaccess

No other systems allowed on read enabled

secondary

If the row store size grows during operation of the primary, it might become

necessary to increase the global_allocation_limit on the secondary

site. As of HANA 1.0 SPS07 it is possible to change the global.ini on the

secondary accordingly and then activate the change with “hdbnsutil –

reconfig” (because no SQL is possible in this state).

4.4 License Validity

The primary system automatically replicates relevant license information to the

secondary. No additional license needs to be installed, since the primary and

secondary have the same SID.

Further information on licensing in SAP HANA system replication can be found in

SAP note 2211663.

5. Configuration steps

This section describes the following steps:

 Perform an initial data backup or a storage snapshot using native HANA

options. An initial data backup or snapshot is mandatory but an up-to-date

backup is highly recommended anyway

 Enable the primary system for system replication

 Establish a connection between secondary and primary system

 Initiate a full data replication by configuring system replication on the

secondary and starting it – thereafter incremental data replication (only in

The row store size can be determined with this SQL statement:

select host, round(sum(page_size*USED_BLOCK_COUNT)/1024/1024/1024,2) as "RowStore Size GB"

from m_data_volume_page_statistics where page_sizeclass = '16k-RowStore' group by host;

If this limit is not set, the HANA database on the secondary site uses as much memory as it can get and possibly takes it

away from the DEV/QA systems, which could run into out-of-memory.

The size of loaded column tables (in-memory) can be found with this SQL statement:

select round(sum(memory_size_in_total)/1024/1024/1024) size_GB from m_cs_tables;

剩余86页未读，继续阅读

xuewanlin

粉丝: 0
资源: 8

SAP HANA 2.0系统复制教程：实现高可用性的关键步骤

How to Perform System Replication for SAP HANA 2.0

Cybersecurity capability maturity model（C2M2）V2.0.pdf

Knowledge-Embedded Routing Network for Scene Graph Generation.pdf

MigrationfromWindowsServer2008and2008R2to2012Howto.pdf 英文原版

How to perform large scale operations efficiently

Factor Graphs for Robot Perception.pdf

LabTalk Programming Guide for Origin 8.5.1.pdf

Python for Finance.pdf

SAP模块化技术与异常处理.pdf

How to Perform SSH Connection in MobaXterm

最新资源