Best Practices of Huawei SAP HANA TDI Backup Solution Using Third-Party Backup Software

Transcription

1 Best Practices of Huawei SAP HANA TDI Solution Using Third-Party Huawei Enterprise BG, IT Storage Solution Version 1.0

2 Contents 1 About This Document Huawei SAP HANA Solution Overview Scenarios Solution Overview Solution Architecture Networking Policy Procedure Preparing the Environment Installing the Proxy Setting Parameters Best Practice of Huawei SAP HANA Solution Configuration Planning System Planning Hardware Planning Storage Planning Network Planning Service Verification Verification Content Verification Conclusion Appendix Reference Document Acronyms and Abbreviations Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2

3 1 About This Document Overview Purpose Intended Audience Key Components This document provides best practices for Huawei SAP HANA TDI backup solution using third party software. In this document, the SAP HANA +Commvault V11 + OceanStor V3 storage environment is used as an example. This document aims to provide references for Huawei partners and customers by describing the OceanStor solutions and architecture that Huawei provides for SAP HANA backup, including typical scenarios and recommended configurations. This document is intended for: Huawei marketing, sales, and customer training personnel who would promote Huawei SAP HANA backup solution System or storage administrators, customers, and partners who need to master how to perform SAP HANA backup using the third-party backup software Commvault SAP HANA Studio The SAP HANA Studio is a collection of applications for SAP HANA. It enables technical users to manage the SAP HANA database, to create and manage user authorizations, and to create new or modify existing models of data in the SAP HANA database. It is a client tool, which can be used to access local or remote SAP HANA databases. On HANA Studio, you can add several SAP HANA instances at the same time. System administrators can configure and start backup and system replication functions on HANA Studio. Commvault Simpana V11 Commvault Simpana is not only a backup system, but also an enterprise-level data management platform. It can manage data in file systems, systems, databases, virtual machines (VMs), application systems, desktop computers, and online storage systems. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3

4 The Simpana architecture is called Common Technology Engine (CTE). It helps with data migration, storage, query and management as well as system expansion to meet changing service requirements. Designed for all data management scenarios, it employs common software services to create value for users. Huawei OceanStor 2600 V3 backup storage Huawei OceanStor V3 series storage systems are a new generation of storage products designed for enterprise-level applications. Leveraging a storage operating system built on a cloud-oriented architecture, a powerful new hardware platform, and suites of intelligent management software, the V3 series converged storage systems deliver industry-leading functions, performance, efficiency, reliability, and ease-of-use. They provide data storage for applications such as large-database Online Transaction Processing (OLTP)/Online Analytical Processing (OLAP), file sharing, and cloud computing, and can be widely applied to industries such as government, finance, telecommunication, energy, and media. In addition, OceanStor V3 series converged storage systems can provide a wide range of efficient and flexible backup and disaster recovery solutions to ensure business continuity and data security, delivering excellent storage services. Huawei RH2288H V3 backup/media server Huawei launched the 2U dual-socket RH2288H V3 rack server to meet the requirements of the Internet, Internet Data Center (IDC), cloud computing, enterprise markets, and telecom service applications. With advantages such as high-performance computing, large-capacity storage, low power consumption, powerful expansion capabilities, robust reliability, easy deployment and management, and support for virtualization, RH2288H V3 is appropriate for storage services including distributed storage, data mining, electronic photo albums, and videos, basic applications of enterprises, and telecom service applications. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4

5 2 Huawei SAP HANA Solution Overview 2.1 Scenarios can protect HANA databases against storage failures and other physical or logical errors. The recovery point objective (RPO) is determined by the HANA backup interval and can range from several minutes to several days. The recovery time objective (RTO) may be several hours. During HANA recovery, backup data is recovered from the backup storage system to the primary storage system. Then the backup data is read by the host memory and provided to the database for recovery. Huawei SAP HANA TDI backup solutions include: File-level backup, which writes backup data to the file system of the local storage system Data volume protection using storage snapshots Interconnection with third-party centralized backup software using the Backint API (a streaming backup interface defined by SAP). Table 2-1 错误! 未指定书签 lists strengths and weaknesses of the three backup solutions. Table 2-1 Comparison of SAP HANA backup solutions Solution HANA Studio File-level Enterprise-level Local Based on Snapshot Scenario 1. Only SAP services 1. Enterprise-level unified 1. Quick backup need independent backup platform for and rollback backups centralized service to work around 2. No enterprise-level backup software backup 2. Enterprise-level backup mis-operations or logic errors 3. No requirements on RPO or RTO software such as CV is available 2. No backup software 3. High requirements on 3. does not RPO and RTO affect services Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5

6 Solution HANA Studio File-level Enterprise-level Local Based on Snapshot Strength 1. Simple configuration and O&M 2. Reusing existing NAS devices to save costs An enterprise-level backup platform for centralized backup and management of various services 1. Second-level snapshot and lossless snapshot minimize RPO and RTO 2. Test system established using snapshot Weakness A large volume of data needs replication. services may compete with production services for resources. 1. High cost 2. Demanding on maintenance skills Local backup cannot provide protection against device faults. This document focuses on the SAP HANA backup solution using third-party backup software. In this solution, SAP HANA interconnects with the professional backup software using the Backint API to implement enterprise-level backup management. This solution is applicable to the following scenarios: Full backup of the database and service configurations is required to avoid data damages caused by mis-operations, logical errors, and device faults. There are strict requirements on data backup, which must be satisfied by enterprise-level backup software. In extreme scenarios, performance deterioration and RPO increase caused by the backup and data replication can be tolerated. For details about the other two backup solutions, see the following: Best Practices of Huawei SAP HANA TDI Solution Using HANA Studio Best Practices of Huawei SAP HANA TDI Solution Using Storage Snapshot 2.2 Solution Overview Solution Architecture SAP HANA can be backed up using any third-party backup software certified by SAP. Huawei SAP HANA backup solution uses Commvault Simpana 11.0 to create a unified backup domain to protect SAP HANA, files, and applications. The backup software uses the Backint API to back up and recover HANA databases. Users are unaware of the process. Alternatively, users can also use SAP HANA Studio or other SAP tools to perform backup or recovery. Figure 2-1 错误! 未指定书签 shows the backup architecture. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6

7 Figure 2-1 SAP HANA backup architecture Each HANA database has a unique system identifier (SID). The HANA system can be deployed in either sing-node mode or multi-node mode. The multi-node HANA system has concurrent processing capabilities and can be deployed in high availability (HA) mode for failover. Each HANA node has a maximum of four services: NameServer StatisticsServer XS Engine IndexServer The four services have their own data volumes and log volumes. In single-node deployment, when the workload increases, you can add memory and CPU resources to the local node to expand its processing capabilities. Figure 2-2 shows the configuration diagram of single-node mode. Figure 2-2 Configuration diagram of single-node backup Alternatively, you can improve processing capabilities of SAP HANA by adding more nodes and distributing a SAP HANA database on multiple nodes. A production system can have only Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7

8 one SID (one database), while a non-production system can have multiple SIDs (multiple databases). Figure 2-3 错误! 未指定书签 shows the configuration diagram of multi-node mode. Figure 2-3 Configuration diagram of multi-node backup Networking In the backup architecture of Huawei SAP HANA solution using third-party backup software, OceanStor V3 storage is connected to an independent media proxy server (MediaAgent). MediaAgent (MA) connects to SAP HANA nodes through IP networks. SAP HANA data to be backed up is transmitted to MA through IP networks and then backed up to OceanStor V3 storage. The following describes the SAP HANA backup networking in LAN-base single data center and multiple data centers. The LAN-base backup architecture uses an independent server to provide MA services. Compared with the LAN-free backup architecture, backup services in the LAN-base backup architecture have less impact on production services. Figure 2-4 networking of a single data center Production storage SAN storage CS MA ida management service media service proxy SAN GE FC 10GE A ida ida File server Application server Data center HANA01 HANA02 Service network MA MA media server data center CS management server Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8

9 HANA01 and HANA02 are installed with SAP HANA and the backup client (idataagent). The CommServe server (a backup management server) can be installed on a separate server or on the server where MA installed to provide CommCell Console services, manage and maintain metadata databases, and record configuration information and data storage information. The MA server (a media proxy server) is installed with MA components. Each CommCell contains one or multiple MAs for data transmission between client computers and storage media. 10GE links are used on the local area network (LAN) for communication between servers. The 10GE LAN is used to transfer data between the HANA server and MA. The FC SAN network or 10GE LAN is used to transfer data between the HANA server and the production storage and between the MA server and the backup storage. When there are multiple data centers, backup network components need to be deployed at multiple sites. For example, if there is one local data center site and two remote sites, all sites contain application servers and HANA nodes. The backup data in two remote data centers is replicated to the local data center. All backup data in the local data center is replicated to the remote data center 2 that serves as a disaster recovery (DR) data center. Figure 2-5 networking of multiple data centers Production storage SAN SAN storage S management service M media service A proxy GE FC 10GE A A A File server Application server Data center HANA01 HANA02 Service network M media server M data center S management server WAN Service and backup network Remote site 1 Remote site 2 and service network and DR data center M All-in-one backup device Application server HANA03 A A HANA04 HANA05 A A HANA06 M media server SAN Production storage storage If there are three sites, the physical topology of the backup solution consists of a local data center, remote data center 1, and remote data center 2. The local data center includes the backup management node, backup service node, backup storage, 10GE switch, and Ethernet switch (optional). The backup management service component is installed on the backup management node to manage the backup system. The backup media service component is installed on the backup service node to write the backup data and read the recovered data. The backup storage stores the backup data. The 10GE switch is used to interconnect HANA Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9

10 2.2.3 Policy nodes and servers or the storage (NAS) and servers. The Ethernet switch (existing Ethernet switch can be used) interconnects the backup system with the production system, which is optional. The remote data center 1 includes the all-in-one backup node and Ethernet switch (optional). The all-in-one backup node integrates the functions of a backup service node and backup storage, and stores all backup data. The optional Ethernet switch (existing Ethernet switch can be used) interconnects the backup system with the production system. The remote data center 2 includes the backup service node, backup storage, and Ethernet switch (optional). The backup service node houses the backup media service component to write the backup data and read the recovered data. The backup storage stores the backup data. The optional Ethernet switch (existing Ethernet switch can be used) interconnects the backup system with the production system. If you want to back up the operating systems of VMs running databases on the VMware virtual platform, not only back up the operating systems, but also the applications running on the VMs. SAP HANA databases support full backup, incremental backup, differential backup, and log backup. You can orchestrate proper backup policies as instructed in Figure 2-6. Figure 2-6 modes Details about backup modes are as follows. Mode Full backup Incremental backup Differential backup Description of all data files, tablespace, and logs. It is usually performed on weekend and has little impact on the system. of changed data and logs after the last full backup. It can be performed multiple times each day, for example, before settlement in the morning, at noon, and in the evening. Differential backup refers to the backup of changed data after the last full backup. It is performed after settlement every day at night. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10

11 Mode Log backup Description Data volume is backed up manually or according to the backup plan, while the backup of logs is performed automatically. By default, logs are backed up every 15 minutes. The backup interval can be modified based on user requirements. Log backup is important because logs cannot be deleted from persistent storage devices unless they have been backed up. If log backup is not used, logs will fill up the log storage area, resulting in a database lockup. 2.3 Procedure Preparing the Environment Using OS Commands Before constructing the backup environment, you need to check whether SAP HANA is running properly by using OS commands or HANA Studio. Run the HANA SQL command on any HANA node and invoke the SAP HANA configuration script to check whether the host status is OK. If it is OK, HANA is running properly and you can proceed to the next step. Using HANA Studio You can run the following commands to check the HANA status: [hana001~]# su - anaadm hana001:/usr/sap/ana/hdb00> cdpy hana001:/usr/sap/ana/hdb00/exe/python_support> python landscapehostconfiguration.py On a PC with HANA Studio installed, connect HANA Studio to HANA through the OS management interface or service interface. Then you can check the HANA status using either of the following methods: On the Overview tab page of HANA Studio, check whether HANA is running properly. If Operation Status is All services started, HANA is running properly. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11

12 On HANA Studio, choose Landscape > Hosts, and check whether HANA hosts are running properly. If the status of all hosts is OK, HANA is running properly and you can proceed to the next step. Preparing for the Installation Before deploying the SAP HANA backup solution, install the Commvault platform, configure MA, media library, as well as storage policies. For more details, refer to the Commvault online manual. Then, add the host name and IP address of the HANA node to the CS and MA hosts files, and add the host name and IP address of backup servers CS and MA to the HANA node's hosts files. For details, see sections 1.1, 2.1, 4.3, 4.6, and 11.2 in the BC&DR Solution V200R001C10 Commvault Operation Guide (). When deploying the HANA backup solution, you need to find the SID of HANA, and use the SID to create or find the following two directories on the server where HANA is installed: /usr/sap/<sid>/sys/global/hdb/opt: The SAP HANA EXE directory is used to save the Symbolic Link connecting to the Commvault backup proxy. /usr/sap/<sid>/sys/global/hdb/opt/hdbconfig: The directory for saving the Backint configuration file of the HANA backup proxy Installing the Proxy SAP HANA Agent of Commvault must be installed on every node of the HANA system. The agent can be installed by using local command lines or push-installed by the Commvault console. For detailed operations, see the BC&DR Solution V200R001C10 Commvault Operation Guide () Setting Parameters After the backup proxy is installed, perform configurations to continue the backup and recovery operations: Step 1 Create Symbolic Link to a parameter file in the client system. Step 2 On the CommCell GUI, create a Pseudo Client. Step 3 On SAP HANA Studio, connect backups to Commvault. ----End Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12

13 For detailed steps about installation and configuration, visit the following website: Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13

14 3 Best Practice of Huawei SAP HANA Solution The best practices of the Commvault-based centralized backup for SAP HANA described in this document provide references for project planning. For detailed configurations of a project, contact backup system architects for professional opinions. 3.1 Configuration Planning System Planning Customizing Policy Table 3-1 错误! 未指定书签 shows typical backup policies for SAP HANA backup solutions. The policies are modifiable according to the actual situation. Table 3-1 policies Object Full Interval Retention Duration for Full Data (Day) Incremental Interval Retention Duration for Incremental Data SAP HANA production system SAP HANA non-production system One day 15 days N/A N/A One week One month N/A N/A SAP application One week Three months One day Three months VM One month Three months One day Three months Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14

15 Calculating Capacity Object Initial Capacity Capacity Growth Rate Data Deduplication Ratio SAP HANA production system SAP HANA non-production system Memory capacity x 0.6 Memory capacity x 0.6 N/A 2:1 N/A 2:1 SAP application 300 GB 1% per month 3:1 VM Determined by the actual situation 1% per month 2:1 Determining Media Server Quantity A media server can back up a maximum of 120 TB data after deduplication. If a data center has 96 TB data to be backed up after deduplication, it is recommended that two media servers be deployed to ensure security and load balancing of the backup system. Calculating Performance and Bandwidth Required According to production data conditions of the customer, the customer is advised to perform full data backup within 48 hours after the backup system is constructed. The required backup time window is X hours (backup at off-peak hours). The required bandwidth for the backup solution is as follows: bandwidth = Maximum full backup data volume per hour/ time window/bandwidth usage (usually 80%) Hardware Planning For hardware in the Huawei HANA backup solution using Commvault, you can choose all-in-one backup or centralized backup, as listed in Table 3-2. Table 3-2 Hardware of SAP HANA backup solutions using Commvault Category All-in-one Centralized Application scenario Local backup of small- and medium-sized business (SMB) Local backup of small-sized branches Local backup of data centers Centralized backup of multiple branches Hardware Recommended configuration All-in-one backup device FusionServer RH2288H V3 If the capacity of data to be backed up is less than 32 TB, you need to configure SSDs to enable FusionServer RH2288H V3 OceanStor 2600 V3/5500 V3 OceanStor 9000 If the capacity of data to be backed up is larger than 300 TB, OceanStor 9000 is recommended. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 15

16 Category All-in-one Centralized deduplication. If not, OceanStor 2600 V3/5500 V3 is recommended. Function Supports file backup and application backup in Windows, Linux, and UNIX. Supports backup of VMware and Hyper-V VMs. Table 3-3 错误! 未指定书签 错误! 未指定书签 lists software and hardware required for the test. The hardware and software are modifiable according to the actual situation. Table 3-3 Software and hardware planning Type Quantity Configurations Production storage Production server (backup client) 1 OceanStor V3: 8 x Intel 6-core 2.1 GHz + 4 x 256 GB memory + 96 x 600 GB SAS disks 8 x SmartIO cards 2 RH5885H V3: 4 x Intel Xeon CPU E v GB memory OS: SLE-11-SP4 Software: Commvault V11SP6 and SAP HANA-related software packages storage 1 OceanStor 2600 V3: 32 GB memory + 96 x 4 TB NL-SAS disks 2 x 8 Gbit/s Fibre Channel cards management server service server (backup proxy) 1 RH2288H V3: 2 x Intel Xeon CPU E v GB memory OS: Windows 2012 R2 Software: Commvault V11SP6 1 RH2288H V3: 2 x Intel Xeon CPU E v GB memory OS: SLE-11-SP4 Software: Commvault V11SP6 10GE switch 2 CE6850 Fibre Channel switch 2 SNS2124 You need to configure the number of backup servers and the capacity of backup media based on the volume of data to be backed up. Table 3-4 lists recommended configurations. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16

17 Table 3-4 Recommended configurations of backup components Scale Volume of HANA Data to Be Backed Up Media Server (MediaAgent) Xsmall 0.5 TB 10 TB 2 x 4 CPU cores + 24 GB RAM Small 10 TB 30 TB 2 x 4 CPU cores + 32 GB RAM Medium 30 TB 60 TB 2 x 6 CPU cores + 32 GB RAM Large 60 TB 150 TB 2 x 8 CPU cores + 64 GB RAM Xlarge 150 TB 200 TB Two MAs, 2 x 8 CPU cores GB RAM Others More than 200 TB Multiple MAs, 2 x 8 CPU cores GB RAM Storage Planning In Commvault V11, four paths are mounted to a disk library. Each path is configured with a LUN with a capacity of 5 TB. Table 3-5 错误! 未指定书签 shows configuration planning of the backup storage. Table 3-5 Disk domain, storage pool, and LUN planning of the backup storage LUN Name Pool Name Disk Domain Name Number of Disks RAID LUN01 StoragePool01 DiskDomain01 24 RAID 6 LUN02 StoragePool02 DiskDomain02 24 LUN03 StoragePool03 DiskDomain03 24 LUN04 StoragePool04 DiskDomain04 24 This document describes configuration planning of two HANA nodes. For multiple HANA nodes, you need to add two disk domains, two storage pools, and two LUNs for each node. If a standby HANA node is added to the HANA node cluster, no extra storage resources are needed. Performance optimization for a backup system involves optimizations in the HANA database, backup software, data transmission links, and backup media. Parameter settings may vary with the production environment. Therefore, you must adjust parameter settings according to the actual situation Network Planning To ensure optimal network performance of LAN-base backup architecture, you are advised to adopt the following common best practices: Deploy the backup network on the local area network (LAN) due to the following: Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 17

18 The latency of a LAN is less than 1 ms, while the latency of a wide area network (WAN) may be greater than 50 ms. Growth of the latency deteriorates the network transmission capability. Reduce the length and quantity of network cables. Create VLANs for the backup network on switches. A VLAN can limit broadcast packets to effectively control network broadcast storms, save network bandwidth, and improve the network processing capability. Do not use routers on the backup network because they will increase the network latency. Use 10GE links or NIC bonding to increase the network bandwidth. GE links are not recommended because they are likely to become performance bottlenecks on the backup network. 3.2 Service Verification Verification Content In this document, you need to perform the following steps to test SAP HANA backup solutions: 1. Back up SAP HANA. 2. Recover SAP HANA. 3. Compare space saving rates when deduplication and compression are not enabled and enabled. 4. Compare the average full backup performance when deduplication and compression are not enabled and enabled. 5. Compare the performance when deduplication and compression are enabled at MA and clients. 6. Compare space saving rates when deduplication and compression are enabled at MA and clients Verification Conclusion Backing Up SAP HANA After deployment of the HANA backup solution using third-party software, you can perform backup operations. You can use Commvault to back up data in various methods. Two common methods are as follows: Backing up data on CommCell GUI After deployment of the HANA backup solution using third-party software, a subclient named default is created in CommCell. You can use this subclient or create another subclient to perform backup operations. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18

19 For differential backup and incremental backup, you must use SAP HANA SPC10 or a later version. You can configure the backup plan on the subclient or using backup policies. Only HANA Studio can initiate log backup. Right-click the subclient that has been created, and choose from the short-cut menu. In the displayed Options for Subclient: sap-backup-nodedup window, select Full, Incremental, or Differential in the Select Type area. Select Immediate or Schedule in the Job Initiation area, as shown in the following figure. On the Commvault GUI, you can view information about backup jobs. As shown in the following figure, the Operation Type is Application Command Line, and you can view information about log backups in backup jobs. Backing up data on SAP HANA Studio Full, incremental, and differential database backups can be initialed from SAP HANA Studio GUI. Alternatively, a shell script using the respective HANA "hdbsql" command can be used. This document describes backups initiated from SAP HANA Studio GUI. Step 1 On the SAP HANA Studio GUI, choose the HANA instance to be backed up, right-click, and choose System on the displayed short-cut menu. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19

20 Step 2 In the displayed of System ANA window, choose Backint from the drop-down list of Destination Type, and choose Complete Data, Differential Data, or Incremental Data from the drop-down list of Type. (Optional) Specify the Prefix, and click Next. On the displayed page, click Finish. The backup is started. ----End On the Catalog tab page of SAP HANA Studio, you can also view the backup history. Specifically, you click a backup job, and detailed information about the backup job is displayed. In EBID columns, the last half part is the ID of a backup job using Commvault. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20

21 Recovering SAP HANA You can perform recovery operations on the Commvault GUI or using SAP HANA Studio. This document describes recovering SAP HANA on Commvault GUI. If you perform recovery operations on the Commvault GUI, Commvault automatically invokes the interface to stop HANA. Step 1 As shown in the following figure, right-click the HANA instance, and choose All Tasks > Browse and Restore. Currently, you can only recover an entire database. However, you can choose to recover the database to the recent status or to a specified point in time. Alternatively, you can choose only to recover data (you need to specify Prefix). In this case, logs in the log area will be deleted. By default, the format of Prefix is <job_id>_complete_data_backup. For example, the backup prefix is 6701_COMPLETE_DATA_BACKUP. If the customer wants to customize Prefix, the following format must be used: <job_id>_customprefix. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21

22 Step 2 On the displayed Restore Options for All Selected Items window: perform the following: To check whether all backups required for recovery are available, select Check access. If you need to initialize the log area, select Initialize log area. If you need to use the incremental data backup, select Use Delta s (Recommended). Confirm the settings and click OK. jobs are started. ----End Comparing Space Saving Rates When Deduplication and Compression Are Enabled and Not Enabled If you use Commvault V11 to back up 814 GB SAP HANA data, Figure 3-1 shows space saving rates when deduplication and compression are enabled at clients. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 22

23 Figure 3-1 Comparison of space saving rates when deduplication and compression are enabled and not enabled Comparison of space saving rates Full backup when deduplication and compression are disabled First full backup when deduplication and compression are enabled Second full backup when deduplication and compression are enabled In the first deduplication and compression, the space saving rate is the data compression rate because there is no duplicate data. In the second deduplication and compression, the space saving rate soars due to the duplicate data. Comparing the Average Full Performance When Deduplication and Compression Are Enabled and Not Enabled If you use Commvault V11 to back up 814 GB SAP HANA data, Figure 3-2 shows the full backup performance when deduplication and compression are enabled and not enabled at the client. Figure 3-2 performance comparison Average performance comparison (GB/hr) Full backup when deduplication and compression are disabled First full backup when deduplication and compression are enabled Second full backup when deduplication and compression are enabled Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23

24 The full backup speed with deduplication and compression disabled is GB/hr while the first and second full backup speeds with deduplication and compression enabled are GB/hr and GB/hr respectively. The backup performance when deduplication and compression are not enabled is better than that when deduplication and compression are enabled, because the deduplication and compression algorithm consumes huge memory and CPU resources, impairing the backup performance. The backup performance when deduplication and compression are enabled for the second time is improved a little, because header information is added to data blocks during the transmission of SAP HANA data. In this case, the number of data blocks during transmission remains unchanged but data written to the backup storage becomes less, resulting in no improvement in the transmission rate. Therefore, when deduplication and compression are enabled, the backup performance improves as hardware configurations of the server improve. Comparing the Performance When Deduplication and Compression Are Enabled At MA and At Clients If you use Commvault V11 to back up 814 GB SAP HANA data, Figure 3-3 shows backup performance (GB/hr) when deduplication and compression are enabled at MA and at clients. Figure 3-3 performance comparison when deduplication and compression are enabled at MA and at clients First full backup when deduplication and compression are enabled Second full backup when deduplication and compression are enabled Client MA According to the test result, the backup performance with deduplication and compression enabled at clients is better than that with deduplication and compression enabled at MA. Because server hardware configurations at clients are better than those at MA, and data is processed faster at clients. Comparing Space Saving Rates When Deduplication and Compression Are Enabled At MA and Clients Figure 3-4 shows space saving rates when deduplication and compression are enabled at MA and clients. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24

25 Figure 3-4 Comparison of space saving rates when deduplication and compression are enabled at MA and clients First full backup when deduplication and compression are enabled Second full backup when deduplication and compression are enabled Client MA In the first and second full backups, space saving rates by deduplication and compression vary significantly because header information is added to data blocks during the transmission of SAP HANA data. When SAP HANA backups are deduplicated at clients, the signature for determining duplicate data is generated at clients. In this case, HANA data received by Commvault is close to raw data (with simple header information). If the data is not changed, Commvault determines based on the generated signature that data backup and transfer are not required, contributing to high deduplication rate. When deduplication is enabled at MA for SAP HANA backups, clients receive HANA data, encapsulate data, and transmit the data to MA. Then, the signature for determining duplicate data is generated at MA. Different from raw data, the data is added with a large amount of HANA header information. Even though raw data is consistent, the different head information misleads Commvault into determining that the data packets are different and the backup transfer is required, resulting in low deduplication rate. To optimize backup performance and space saving rates, it is recommended that deduplication and compression be enabled on client servers with better performance than MA. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25

26 4 Appendix 4.1 Reference Document BC&DR Solution V200R001C10 Commvault Operation Guide () and Recovery Guide for SAP HANA via Commvault Simpana SAP HANA Best Practices Guide SAP HANA SPS12 and Recovery (Overview) SAP HANA Commvault Official Document 4.2 Acronyms and Abbreviations Table 4-1 Acronyms and abbreviations Term Backint Configuration file Data volume Log volume Recovery catalog SAP HANA Studio SID Description A backup interface used to interconnect SAP HANA with the backup software ini. files that contain configuration parameters of the HANA system A file saved on the disk, containing all data of the database and undo information A file saved on the disk, containing all transactions of the database A catalog where all log backups are saved. Log backups contain all backup information. A HANA application used to manage and monitor HANA. It provides console management, modeling, lifecycle management, and data backup and recovery solutions. System identifier. A non-production device may have more than one SID. Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 26

27 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. 27