Best Practices of Huawei SAP HANA TDI Active-Passive DR Solution Using BCManager. Huawei Enterprise BG, IT Storage Solution Dept Version 1.

Transcription

1 Best Practices of Huawei SAP HANA TDI Active-Passive DR Solution Using BCManager Huawei Enterprise BG, IT Storage Solution Dept Version 1.0

2 Contents 1 About This Document Overview Purpose Intended Audience Key Components Huawei SAP HANA TDI Active-Passive DR Solution Installation Scheme Customer Benefits Quick Service Recovery Visualized Management and Maintenance Storage Interconnection and Communication Solution Architecture Solution Flowchart SAP HANA TDI DR Configuration Best Practice Software Configuration Required Software Hardware Configuration Server Planning Storage Planning Other Hardware Planning DR Configuration and Management Configuring BCManager ereplication DR Management Appendix Reference Documents Glossary Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2

3 1 About This Document 1.1 Overview This document describes the Huawei disaster recovery (DR) solution based on OceanStor V3 and Dorado V3 storage systems, as well as OceanStor BCManager for services in the SAP HANA TDI architecture. This document will also provide best practices for SAP services. 1.2 Purpose This document helps Huawei partners and customers understand Huawei SAP HANA TDI Active-Passive DR Solution based on OceanStor V3 and Dorado V3 storage systems and BCManager. Working with the value-added features of Huawei storage products, this solution ensures service consistency during DR, simplifies DR service configuration, monitors the DR service status, facilitates data recovery and DR tests, and reduces O&M risks. 1.3 Intended Audience This document is intended for Huawei employees, partners, and customers. Knowledge of the following technologies and products helps understand this document: Huawei OceanStor Dorado V3 enterprise-level all-flash storage Huawei OceanStor V3 enterprise-level converged storage system SAP HANA database 1.4 Key Components Huawei OceanStor Dorado V3 enterprise-level all-flash storage OceanStor Dorado V3, Huawei's new-generation all-flash storage, provides a stable latency as low as 500 μs and % availability and is the first-choice for enterprises requiring quality storage for critical service systems. In addition to providing enterprise users with high-performance and efficient storage services, the OceanStor Dorado V3 storage system supports advanced data backup and disaster recovery technologies, ensuring secure and smooth operation of data services. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3

4 OceanStor Dorado V3 also offers various methods for easy-to-use management and convenient local and remote maintenance, reducing management and maintenance costs. Huawei OceanStor V3 enterprise-level converged storage system Huawei OceanStor V3 converged storage systems (OceanStor V3 for short) are next-generation unified storage products designed for enterprise-class applications. Leveraging its storage operating system towards cloud architecture, it features a robust new-generation hardware platform and rich intelligent management software. OceanStor V3 is widely applied in scenarios such as large online transaction processing (OLTP)/online analytical processing (OLAP) database, file sharing, and cloud computing. Meanwhile, OceanStor V3 can provide a wide range of efficient and flexible backup and disaster recovery solutions to ensure business continuity and data security, as well as excellent storage services. OceanStor BCManager ereplication DR and backup management software OceanStor BCManager ereplication is designed to manage DR services of data centers for enterprises. Its high application-aware capability and the value-added features of Huawei storage products ensure service consistency during DR, simplify DR service configuration, support the monitoring of DR service status, and facilitate data recovery and DR tests. SAP HANA in-memory database SAP HANA is released by SAP in 2011 and applies to in-memory computing and enterprise-level analysis. It is composed of a memory computing engine and a HANA modeling tool and combines the functions of databases and application platforms in its memory. Supporting local and cloud deployment, the SAP HANA high-performance computing platform is an innovative product powered by an SAP HANA in-memory database. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4

5 2 Huawei SAP HANA TDI Active-Passive DR Solution This chapter describes the Huawei SAP HANA TDI Active-Passive DR Solution based on OceanStor V3, Dorado V3, and OceanStor BCManager ereplication, and covers solution background, architecture, and benefits for customers. 2.1 Installation Scheme The SAP HANA system adopts persistent storage systems to save data in memory, ensuring optimal performance of the system and preventing data loss caused by memory faults such as power failures. The backup memory data can be restored to the HANA system in case any data is lost. In many cases, data corruption may still occur despite such memory backup features because of failures in all-in-one boxes and storage systems. With SAP HANA TDI architecture and value-added functions of Huawei storage systems, data loss is effectively reduced. Huawei SAP HANA TDI data protection solution includes the following: Active-Passive DR Solution Active-Active Data Center Solution Geo-Redundant DR Solution Table 2-1 Analysis of SAP HANA TDI DR solutions DR Solution Active-Passive DR Solution Active-Active Data Center Solution Geo-Redundant DR Solution Characteristics Lower cost, near-zero RPO, and small RTO. Benefiting from the one-click switchover function of BCManager, RTO in this solution is approximately the sum of startup time in HANA database and SAP applications. At the application layer, if a device or even a data center malfunctions, no data loss or service interruption occurs (RPO = 0, RTO = 0). Active-Active Data Center Solution can be upgraded to Geo-Redundant DR Solution, saving costs and improving reliability. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5

6 This document focuses on Active-Passive DR Solution based on BCManager ereplication. This solution is applicable to local and remote DR. The production center and DR center work in active-passive mode. Under normal conditions, the DR center does not provide services for external applications. If an unforeseen disaster occurs, the DR center quickly takes over services from the production center, ensuring optimal service continuity. The replication relationship is established between storage systems used by host services for intra-city or remote DR. 2.2 Customer Benefits Quick Service Recovery BCManager supports one-click switchover, script-based configuration interfaces, and automatic database and service recovery, simplifying operation procedure and shortening service recovery time Visualized Management and Maintenance BCManager provides a visualized DR topology display that supports real-time DR system monitoring, making maintenance easier and greatly improving system usability. Comprehensive login and operation logs facilitate follow-up audit. This solution enables one-stop management of servers, storage systems, and network resources in the production and DR centers, as well as access devices of clients, simplifying system management. The customizable Dashboard can display the following collected information: DR-related figures and reports, statistics about RPO satisfaction, RTO pre-evaluation, and DR test status Storage Interconnection and Communication Huawei storage devices interwork to support DR services at different performance levels in the production and DR centers. By appropriately choosing storage systems based on actual working conditions, users can reduce their investment in disaster recovery by over 50%. Storage systems use the DR replication technology and implement DR data replication at the storage layer. By doing so, DR services do not affect the performance of production servers. 2.3 Solution Architecture This solution enhances IT system availability by establishing an intra-city or remote DR center. If a disaster occurs in the production center, the DR center quickly takes over production services to minimize service interruption. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6

7 Figure 2-1 Architecture of the active-passive DR solution for SAP services 1. BCManager ereplication server connects to servers and storage systems through the management network. 2. You are advised to install OceanStor BCManager ereplication Server on a virtual machine (VM) or physical server that is not used by the production center. This solution deploys the DR management server on a VM in the DR center. If you deploy the server in the production center, DR management is not supported if the production center fails. 2.4 Solution Flowchart Before implementing this solution, ensure that the production and DR systems are running properly, check the status of SAP applications and SAP HANA database, and configure remote replication on the storage system. Figure 2-2 is the flowchart of the solution. Figure 2-2 Flowchart 1. To ensure smooth recovery of SAP services in the DR center, it is good practice to configure the service systems in the production center and DR center identically. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7

8 2. You are required to configure only basic items for the storage system in the DR center. Other configuration items are complete in the production center. 3. For details about DR management, see section 3.3. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8

9 3 SAP HANA TDI DR Configuration Best Practice This chapter describes configuration examples of Huawei SAP HANA TDI Active-Passive DR Solution based on data from a lab environment. The best practice described in this document is based on results conducted in a lab environment. 3.1 Software Configuration Required Software Table 3-1 lists software required for a test environment. Table 3-1 Software planning System Software Type Software Production/DR system SAP server (RH5885H) Storage system (Dorado V3) SUSE Linux Enterprise 11 SP4 for SAP SAP ERP6.0 incl. EHP8 on HANA SAP HANA Database 1.0 SPS12 HyperReplication software license HyperSnap software license SmartThin software license 3.2 Hardware Configuration Server Planning When planning servers, consider the following aspects: 1. Number and type of CPUs and memory size Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9

10 2. Rack server or blade server 3. Required interface cards Based on specifications of the tested application systems, Table 3-2 lists server planning. Table 3-2 Server planning System Type Model and Number of Servers Type and Number of CPUs Memory Model and Number of Interface Cards Productio n system DR system 1 x RH5885H V3 4 x E V4 1 x RH5885H V3 4 x E V4 512 GB 1 x QLogic 8 Gbit/s FC Dual-Port HBA 512 GB 1 x QLogic 8 Gbit/s FC Dual-Port HBA Storage Planning When planning storage, consider the following aspects: 1. Performance requirement (model, disk type, and disk number) 2. Capacity requirement (hot spare policy and RAID level) 3. Networking requirement (different interface modules for FC, IPSAN, and NAS) 4. Value-added functions For the best practice described in this document, Huawei OceanStor Dorado5000 V3 is used in the test environment. Dorado V3 is an all-flash storage system that generally features more than 10 configured NVMe SSDs. The solid performance of SSDs means that you can focus on capacity and not worry about service continuity. Ten 2 TB NVMe SSDs are used with RAID-TP and high hot spare policy to meet storage requirements of the test environment. Table 3-3 Storage planning Storage Model Controller Configuration Disk Type Hot Spare Policy RAID Level Huawei OceanStor Dorado5000 V3 Dual controller 256 GB for each controller 10 x 2 TB NVMe SSDs High RAID-TP System Type Table 3-4 Remote replication planning Disk Domain Storage Pool LUN LUN Capacity Consistency Group Production system DiskDomain01 StoragePool01 LUN_SHARE 512 GB ConsistentGroup002 LUN_DATA 1 TB LUN_LOG 512 GB Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10

11 System Type Disk Domain Storage Pool LUN LUN Capacity Consistency Group LUN_ERP01 LUN_ERP GB 50 GB DR system DiskDomain01 StoragePool01 LUN_SHARE_s 512 GB LUN_DATA_s LUN_LOG_s LUN_ERP01_s LUN_ERP02_s 1 TB 512 GB 200 GB 50 GB Other Hardware Planning In addition to the storage devices and servers, Fibre Channel switches are required as well. Plan other hardware based on actual system requirements. 3.3 DR Configuration and Management You are advised to deploy OceanStor BCManager ereplication Server, DR management software for the solution, on a VM or physical server that is not used by the production center. If you deploy the server in the production center, DR management is not supported if the production center fails. For ereplication Server installation and deployment, refer to references in Appendix Configuring BCManager ereplication Before using OceanStor BCManager ereplication for DR management, complete basic configurations for ereplication. Figure 3-1 shows the basic configuration procedure. Figure 3-1 ereplication basic configuration procedure Checking before configuration: Check whether protected objects in the production and DR systems are working properly and whether storage configurations meet DR requirements. Creating a site: Configure two local sites in ereplication for DR protection in the production and DR centers. Adding resources: Based on the type of planned protected objects, ereplication discovers resources by IP address, port, user name, and password. Four types of resources, namely storage, host, FusionSphere, and vcenter server, can be added to each site. Creating a protected group: Create a protected group for the DR protected objects. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11

12 Figure 3-2 shows this option in the solution software. Figure 3-2 ereplication protected group Data synchronization is the default operation for protected group execution by ereplication and includes freezing and unfreezing. Users can define freezing and unfreezing scripts by themselves. ereplication also allows users to customize execution operations of a protected group. Specifically, users can add operation steps before or after freezing and unfreezing to ensure normal operation of the protected group. For example, checking database status. Creating a recovery plan: Based on the protected group that you have created, implement one-click disaster recovery testing, failback, and scheduled migration based on the recovery plan, and start applications on a specified host in the DR center. Figure 3-3 ereplication recovery plan DR Management Table 3-5 lists operation subitems of BCManager DR management and application scenarios. Table 3-5 DR operations and application scenarios Operation Description DR Testing Planned Migration of Services in the Production Application Scenario Before DR operations, DR tests are implemented to verify the availability of data or snapshots replicated to the DR center. The test process has no adverse impact on the production site. After a test is complete, the test data generated at the DR site needs to be cleared and resources need to be restored to the status before the test to facilitate future DR or planned migration. If services in the production center are interrupted due to anticipated risks (such as outage and routine maintenance), Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12

13 Operation Description Center Planned Switchback of Services in the DR Center Fault/Disaster-Caused Migration of Services in the Production Center Fault/Disaster-Caused Failback of Services in the DR Center Self-defined DR Plan Execution Steps Self-defined Startup Parameters for a Protected Object Application Scenario a specific recovery plan can be executed to implement planned migration. The entire migration process is automatic. The DR site automatically takes over services. After migration, the services can be protected by implementing reprotection on the recovery plan. After services are switched from the production center to the DR center through planned migration, the services must be switched back to the production center based on a drill plan. If data or applications in the production center become unavailable due to unexpected disasters or faults, you must quickly recover the data or applications from the DR center. Before a fault recovery, at least one recovery plan test must be executed successfully. You can only perform this operation on the ereplication system in the DR center. Services are migrated from the production center to the DR center in scenarios of a recoverable fault such as an unexpected power failure. After the production center recovers from the fault, you must synchronize data generated during the DR period from the DR center to the production center and switch services back to the production center. During DR, if you want to reset the DR network at the DR site or stop some services at the DR site to release system resources for smooth service recovery, you can customize the execution steps. This operation can only be performed on ereplication in the DR center. If upper-layer services have special requirements on the startup sequence of databases or VMs, you can modify startup parameters based on live network conditions before performing DR. The aim of doing this is to ensure that databases or VMs can start services after DR. This operation can be performed only in the DR management system in the DR site DR Testing DR tests are implemented to verify the availability of data or snapshots replicated to the DR center. The test process has no adverse impact on the production site. Figure 3-4 ereplication DR test procedure Before performing the test, confirm that data synchronization of remote replication is completed. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13

14 During a DR test, read/write operations cannot be retained. These read/write operations are rolled back after the clearing operation is performed. One-click clearing operations restore the data to the status before the test to facilitate future DR or planned migration. After the test is completed, the administrator can still perform read/write operations on applications on the DR server based on requirements. Close the applications after the test Planned Migration and Failback If services in the production center are interrupted due to anticipated risks (such as outage and routine maintenance), a specific recovery plan can be executed to implement planned migration. Services are migrated from the production center to the DR center and are restarted in the DR center. Figure 3-5 ereplication planned migration and failback Before migration, ensure that applications in the production center are stopped and the mapping between the production host and production storage is removed. After migration is completed, the administrator needs to log in to the database server in the DR center, scan for and mount disks, and check whether data and applications are normal. BCManager provides interfaces for the administrator to develop and deploy scripts independently for disk scanning, application startup, and application testing. Perform the following steps to start HANA and ERP: Step 1 Switch to the database administrator account. Step 2 Use the HDB start command to start the HANA database. Step 3 Switch to the administrator account of the application server. Step 4 Run the startsap r3 command to start ERP application services. ----End Once HANA and ERP are running and migration is completed, the services can be protected by implementing reprotection on the recovery plan. After services are switched from the production center to the DR center through planned migration, the services must be switched back to the production center based on a drill plan. Operations for switching services from the secondary to the primary storage are the same as those for primary-to-secondary storage switchover Fault/Disaster-Caused Migration and Failback of Services If data or applications in the production center become unavailable due to unexpected disasters or faults, you must quickly recover the data or applications from the DR center. Before a fault recovery, at least one recovery plan test must be executed successfully. For Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14

15 protected groups that use asynchronous remote replication, the DR center must have at least one copy of intact service data. For information about how to start services in the DR center after the migration, see section Figure 3-6 ereplication service migration and failback after a fault recovery 1. Operations before a failback include a primary/secondary switchover and canceling write protection on the secondary storage. 2. By refreshing resources and protected groups registered with ereplication, ereplication detects that the replication relationship is adjusted and updates the status of invalid protected groups. 3. Before the services are switched back, you need to perform a DR test to verify the data availability to ensure success rate of service failback. In scenarios of unexpected failures and disasters, services are migrated from the production center to the DR center. After the production center recovers from the fault, you must synchronize data generated during the DR period from the DR center to the production center and switch services back to the production center. The failback process is as follows: Step 1 Log in to the service system of the original production center and confirm that applications in the production center are stopped. Step 2 Uninstall disks on application hosts. Step 3 Log in to the storage system of the DR center and perform a primary/secondary switchover on the remote replication pair or consistency group that is in split status. Step 4 Enable write protection of the secondary resource. Step 5 On the storage management page of the DR center, run the Synchronize command for the remote replication pair and consistency group that are in split status. ----End The best practice in this chapter provides typical configuration and DR management operations to facilitate understanding of the solution. Before implementing the solution, confirm requirements and refer to documents in the Appendix. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 15

16 4 Appendix 4.1 Reference Documents OceanStor Dorado5000 V3&Dorado6000 V3 Storage System V300R001 Product Description 03 OceanStor Dorado5000 V3&Dorado6000 V3 Storage System V300R001 Basic Storage Service Configuration Guide 03 OceanStor Dorado5000 V3&Dorado6000 V3 Storage System V300R001 Remote Replication Feature Guide 03 OceanStor BCManager V200R001C10 ereplication User Guide Glossary Table 4-1 Glossary Term HANA ERP BCManager FC Description SAP HANA in-memory database SAP ERP management system OceanStor BCManger DR and backup management software Fibre Channel Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16

17 Copyright Huawei Technologies Co., Ltd All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademark Notice, HUAWEI, and are trademarks or registered trademarks of Huawei Technologies Co., Ltd. Other trademarks, product, service and company names mentioned are the property of their respective owners. General Disclaimer The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice. HUAWEI TECHNOLOGIES CO., LTD. Huawei Industrial Base Bantian Longgang Shenzhen , P.R. China Tel: Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 17