PROTECTING SAP HANA WITH DATA DOMAIN BOOST FOR DATABASES AND APPLICATIONS

Transcription

1 PROTECTING SAP HANA WITH DATA DOMAIN BOOST FOR DATABASES AND APPLICATIONS Enabling a Smooth Migration from Physical to Virtualized Environments with One Process and One Solution EMC Solutions Abstract This white paper demonstrates how you can use EMC Data Domain Boost for Databases and Applications (DDBDA) to protect SAP HANA by enabling backup, recovery, and migration across physical and virtualized environments. DDBDA provides you with a simple and effective way to accomplish these operations. January 2015

2 Copyright 2015 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All trademarks used herein are the property of their respective owners. Part Number H

3 Table of contents Executive summary... 5 Business case... 5 Solution overview... 6 Key results/ recommendations... 6 Introduction... 7 Purpose... 7 Scope... 7 Audience... 7 Technology overview... 8 Overview... 8 Hardware resources... 9 Software resources... 9 EMC Data Domain Data Domain Boost for Databases and Applications (DDBDA) DDBDA integration with SAP HANA SAP HANA database Single-host configuration (scale-up) Multi-node cluster configuration (scale-out) SAP HANA persistence SAP HANA on vsphere Testing and validation DDBDA for SAP configuration Migrating from a physical to a virtualized environment using DDBDA Test validation Validation results Virtual HANA backup and recovery with DDBDA Reducing network bandwidth requirements with Data Domain Boost Recovering virtual HANA to its most recent state Validation results Recovering virtual HANA to a specific point in time Validation results Automating backup through CLI and SAP GUI Validation results Conclusion Summary Findings

4 References EMC documentation SAP documentation VMware documentation Appendix

5 Executive summary Business case SAP HANA is an in-memory database that combines transactional data processing, analytical data processing, and application logic processing in memory, delivering real-time business insights that were not previously feasible. Since its launch, SAP HANA has been an extremely successful product. Initially used for SAP Business Warehouse application analytics, it now supports SAP Business Suite, the flagship enterprise resource planning (ERP) application. As well as supporting a wider range of applications, SAP HANA now has more deployment options, such as a factory-configured appliance, tailored datacenter integration (TDI), and virtualization with VMware. Because SAP HANA is so widely used, customers face many challenges as they deploy and expand their SAP HANA environment. IT organizations must ensure that: SAP HANA has the same levels of data protection as a traditional storagebased database management system, while accommodating shrinking backup timeframes. CIOs increase productivity and efficiency in maintaining SAP systems while minimizing the impact of backup processes that storage administrators and infrastructures must support. Administrators address the efficiency challenges posed by the distributed storage of data across different SAP software components and systems (ERP, CRM, and so on). EMC has developed Data Domain Boost for Databases and Applications (DDBDA), a software tool that empowers database administrators to use SAP HANA Studio for managing backup operations, performing restores, and leveraging all the benefits offered by EMC s Data Domain and Data Domain Boost products. In this, we show how DDBDA can enable simple, flexible, efficient, and optimized backups for your SAP HANA environment with the following benefits: A 99 percent reduction in network utilization and backup storage requirements by transferring and storing only unique, deduplicated data Easier migration to virtualized SAP HANA, thus realizing the TCO, agility, and availability advantages of the vsphere environment Compatibility between the DDBDA as your SAP HANA backup solution and the virtual HANA database, including backup, specific backup set restore, mostrecent restore, and point-in-time restore Simpler, more efficient manual or automated backup and restore processes using EMC Data Domain 5

6 Solution overview The solution uses these main components: EMC Data Domain an appliance that provides the main platform Data Domain Boost a software feature that provides performance and availability enhancements Data Domain Boost for Databases and Applications (DDBDA) a further software feature that simplifies and automates backup and restore services for SAP HANA with specific databases and applications This solution was tested and validated in several scenarios, including migration, backup, and restore between both physical and virtual HANA environments. Key results/ recommendations The solution shows that the DDBDA delivers: Easy migration of SAP HANA from a physical to a virtualized environment Over 99 percent network bandwidth savings during backups Simplified scheduling of routine backups with HANA CLI and SAP GUI 6

7 Introduction Purpose The purpose of this is to demonstrate the capabilities of EMC s DDBDA, which can be used to seamlessly back up SAP HANA systems installed in appliances, in TDI environments, and in VMware environments. This paper aims to show that DDBDA can be used to: Back up both physical and virtual SAP HANA systems Restore databases from physical to virtual platforms Deploy physical systems as virtual servers Furthermore, the paper aims to prove that DDBDA is the best tool for organizations where the database administrators own the SAP HANA backup and recovery processes, because it enables consistent practices and fully integrated solutions for both physical and virtualized environments. Scope This document provides test validation of migration, backup, and recovery of virtual SAP HANA with EMC DDBDA and describes the following: Key solution technologies Key business benefits of using DDBDA with virtual SAP HANA How to configure DDBDA for virtual SAP HANA migration and backup How to recover virtual SAP HANA with DDBDA SAP does not currently support incremental or differential data backups. For more information on SAP HANA backup and recovery, please refer to the SAP HANA Administration Guide and SAP Note SAP does not currently support Backint to copy an existing SAP system on SAP HANA. EMC Data Domain supports multiple protocols, such as NFS, and it can be used as a destination for the SAP HANA backup activity with type FILE to restore an SAP application with a different hostname or schema in the target system. This is not included in the scope of this paper. Audience This document is intended for infrastructure architecture and operation owners, as well as SAP HANA datacenter integration architects, and SAP HANA operations teams, who are responsible for defining and implementing backup and recovery solutions for SAP HANA that span both physical and virtualized environments. 7

8 Technology overview Overview Figure 1 provides an overview of the physical and software elements of the solution architecture. Figure 1. Solution architecture In this solution, EMC VNX provides the persistence for data and log volumes for both the physical and virtual HANA systems. EMC Data Domain protects the HANA databases and migrates the databases from the physical environment to the virtualized environment. 8

9 Hardware resources Table 1 describes the hardware components for this solution. Table 1. Solution hardware resources Equipment Quantity Configuration Storage system 1 EMC VNX8000 ESXi host 1 Four 10-core CPUs, 384 GB RAM Physical host 1 Four 10-core CPUs, 384 GB RAM Data Domain 1 EMC Data Domain 670 Ethernet switches 2 10 Gb Ethernet (GbE) SAN switches 2 8 Gb Fibre Channel (FC) Software resources Table 2 describes the software components used in the deployment. Table 2. Solution software resources Software Version Description EMC Data Domain Operation environment for EMC Data Domain EMC PowerPath/VE 5.8 Multipathing software EMC Block Operating Environment SUSE Linux Enterprise Server for SAP Applications 5.33 Operating environment for VNX 11 SP3 Operating system for SAP HANA VMware ESXi Hypervisor VMware vcenter Server vsphere management server EMC Data Domain Boost for Databases and Applications (DDBDA) 1.0 Backup and restore software SAP HANA database SPS08 SAP in-memory database 9

10 EMC Data Domain EMC Data Domain is a deduplication storage system for backup and recovery. Scalable Data Domain systems feature high-speed, inline deduplication and networkefficient replication. Data Domain deduplication storage systems reduce the amount of data to process by only backing up data that have not previously been processed, skipping all unnecessary duplicates in the process. This can reduce backup storage requirements by up to 30 times and can protect up to 28.5 PB (petabytes) of logical capacity. EMC Data Domain (DD) Boost is a software option available for all Data Domain systems, and is a requirement for cloud-enabled infrastructures. DD Boost has two components: a plug-in that runs on the backup server or client and a component that runs on the Data Domain system. DD Boost provides the following main features: Distributed segment processing (DSP), which distributes parts of the deduplication process from the Data Domain system to the backup server or client, increasing backup application performance by up to 50 percent. Managed file replication, which enables backup applications to manage Data Domain replication with full catalog awareness. Advanced load balancing and link failover, which provides link aggregation for load balancing and link failover, eliminating the need for network layer aggregation. Data Domain Boost for Databases and Applications (DDBDA) Data Domain Boost for Databases and Applications (DDBDA) is an EMC product that enables you to perform backups and restores of DB2, SAP HANA, or SAP with Oracle database data with a Data Domain system. You can use database-specific backup and recovery tools to perform other DBA operations. DDBDA performs backups to, and restores from, a Data Domain system by using the DD Boost interface. A backup to a Data Domain system takes advantage of the DD Boost feature by using the following components: The DD Boost library API, which enables the backup software to communicate with the Data Domain system The Distributed Segment Processing (DSP) component, which reviews the data that is already stored on the Data Domain system and sends only unique data for storage. DSP enables the backup data to be deduplicated on the database or application host to reduce the amount of data transferred over the network. During the restore of a backup to the client, the Data Domain system converts the stored data to its original non-deduplicated state before sending the data over the network. DDBDA integration with SAP HANA DDBDA is integrated with the SAP HANA BACKINT interface to back up and recover SAP HANA database data and redo log files. The SAP HANA BACKINT agent enables DD Boost for SAP HANA to directly connect to the HANA database. 10

11 Figure 2. DDBDA for SAP HANA backup procedure Figure 2 shows the following process interactions when a backup is initiated: 1. The SAP HANA database server runs the hdbbackint program, installed as part of DDBDA, and passes a list of pipes to back up. 2. The hdbbackint program processes the SAP HANA parameters from the configuration file and starts the child hdbbackint processes that back up the required data. 3. The child processes send the database data and tracking information to the Data Domain system for storage. The following supported SAP HANA tools with DD Boost for SAP HANA can be used to perform backup and recovery operations in an SAP HANA environment: SAP HANA command line interface (CLI) and the hdbsql commands SAP HANA Studio GUI SAP HANA database SAP HANA is an in-memory database that combines transactional data processing, analytical data processing, and application logic processing in memory. This design enables real-time online application processing (OLAP) analysis on an online transaction processing (OLTP) data structure. SAP HANA can be delivered as an appliance with factory-installed hardware, operating system, and SAP HANA database software. This configuration can be based on either a single node or a multi-node cluster, using certified hardware provided by SAP s hardware partners. It can also be implemented under SAP s Enterprise Shared Storage and Tailored Datacenter Integration program, which allows customers to use their existing infrastructure. The SAP HANA architecture can be deployed in two basic configurations: Single-host (scale-up) Multi-node cluster (scale-out) 11

12 Figure 3. SAP HANA system architecture Single-host configuration (scale-up) In an SAP HANA single-host configuration, all SAP HANA components run on a single server. The persistence layer resides on server internal flash and SAS disks. The scalability of the database is limited by the amount of RAM that can be installed in the server. A single-host configuration does not provide High Availability (HA) functionality. Multi-node cluster configuration (scale-out) In a multi-node cluster configuration, the SAP HANA database is distributed across multiple servers. The scalability of the database is achieved by adding servers to the cluster. Shared storage is required for a multi-node cluster configuration to provide High Availability (HA) functionality. Each node uses its own persistent devices on the shared storage layer. In case of a node failure, the SAP HANA HA feature reassigns the storage persistence to a standby node, which recreates the in-memory database part from the storage persistence. In a distributed scale-out environment, one node (usually the first one installed) is the master node. It handles the workload of the NetWeaver stack, the statistics and the tables located in the row store. For a HANA scale-out database, it is a requirement to have at least three nodes. In a two-node landscape, the table distribution and the degree of parallel processing do not usually provide worthwhile benefits over a single-node configuration. 12

13 SAP HANA persistence The SAP HANA in-memory database holds the bulk of its data in memory for maximum performance but still uses persistent storage to provide for startup and recovery in case of a failure. The SAP HANA persistence resides either on internal disks (single node) or on shared storage (multi-node cluster) and uses two volumes: Data and Log, as shown in Figure 4. Figure 4. The SAP HANA persistence layer Data and log information are automatically saved to disk at regular savepoints as shown in Figure 5 and described in the following sections. Figure 5. Persistence mechanism Data volume Data in memory is asynchronously written to the persistence mechanism as a savepoint every five minutes by default. This data volume capture method uses a locking mechanism to prevent modification of pages while copying modified pages and capturing open transactions before finally increasing the savepoint version and releasing the lock. 13

14 Log volume The log file system captures all database transactions since the last savepoint. It is saved to disk continuously and synchronously after each database transaction commit at the end of the disk write operation, or if the internal log buffer (1 MB) is full. This information allows the database to be rolled back to any point in time, as well as to back out of, or redo, individual transactions. In case of failure, the log volume allows the database to be restored from the last savepoint onwards. SAP HANA on vsphere SAP HANA single host now runs in production on vsphere, the foundation of the VMware vcloud Suite. You can combine the power of the SAP HANA in-memory platform with vsphere to achieve faster time-to-value, better service levels, and lower TCO for your production environments, and take the next step to the software-defined datacenter. As shown in Figure 6, the benefits include: Faster time-to-value Accelerate and automate provisioning and reduce deployment time to hours rather than days. Use template provisioning to ensure consistency and scalability across environments. Better service levels With vsphere vmotion, live-migrate SAP HANA across hosts in minutes with zero downtime and zero data loss. Ensure 99.9 percent high availability and maximize uptime by automatically restarting SAP HANA virtual machines with vsphere High Availability. Automatically manage peak analytic workloads. Lower TCO Reduce capital expenditure (CapEx) by 70 percent and operational expenditure (OpEx) by 56 percent through greater utilization of existing resources and infrastructure. Unify and manage SAP HANA with the rest of your virtualized datacenter. Improve resource utilization through simplified operations management. 14

15 Figure 6. SAP HANA on vsphere benefits For detailed information on virtualizing SAP HANA with VMware vsphere, refer to SAP Note and to the VMware documentation section. A variety of techniques and tools are available to customers when migrating SAP HANA on vsphere. In Migrating from a physical to a virtualized environment with DDBDA, we show how to migrate SAP HANA on vsphere using Data Domain Boost for SAP HANA. 15

16 Testing and validation This section provides detailed information on test scenarios and results. We performed the testing of a single-node HANA backup and restore on a virtualized environment. This testing included the following scenarios: DDBDA for SAP configuration Migration from a physical to a virtualized environment using DDBDA On-demand virtual HANA backup and restore with DDBDA Scheduled backup through HANA CLI and SAP GUI DDBDA for SAP configuration You can use Data Domain Boost for SAP HANA for an online backup of the entire database. After you install the DDBDA software on the operating system of the database host, use the following steps to configure it: 1. Manually create the following subdirectory, if it does not already exist: /usr/sap/<sid>/sys/global/hdb/opt 2. Copy the /opt/ddbda/bin/hdbbackint file to that directory or create a symbolic link that points from the following directory to the executable file: /usr/sap/<sid>/sys/global/hdb/opt/hdbbackint 3. Modify the parameter settings of the following SAP HANA template configuration file: /opt/ddbda/config/sap_hana_ddbda.utl In this solution, we set the parameters as shown in Table 3. Parameter Value Comments DEVICE_HOST e92-dd670-2 Data Domain server hostname DEVICE_PATH /ddbda Name of the Data Domain storage unit DDBOOST_USER adminboost Name of the DD Boost user as defined on the Data Domain server CLIENT PV2 Local client hostname Table 3. Parameter settings of DDBDA configuration file 4. Configure the DDBDA lockbox, which provides encrypted storage of the DD Boost user password by ddbmadmin command, as shown in Figure 7. Figure 7. Configure DDBDA lockbox 16

17 5. Specify the location of the DDBDA configuration file for data and log backup in SAP Studio, as shown in Figure 8. Figure 8. Specify location of DDBDA configuration file in HANA studio For more detailed configuration information, refer to the Product Configuration section in the EMC Data Domain Boost for Databases and Applications Release 1.0 Administration Guide. Migrating from a physical to a virtualized environment with DDBDA This test scenario validates DDBDA for migrating SAP HANA from a physical to a virtual platform with a different OS patch level. As shown in Figure 9, we successfully restored to a virtual SAP HANA database from the backup of a physical HANA saved on Data Domain, using DDBDA. In this solution, the OS patch of the virtual SAP HANA database host is upgraded from SUSE Linux 11 SP2 to SP3 by migration. Figure 9. Physical-to-virtual SAP HANA migration with DDBDA 17

18 Before a physical-to-virtual SAP HANA migration, the system must meet the following prerequisites: A virtual SAP HANA database with the same SID, UID (User ID), and GID (Group ID) as the physical HANA has been installed. Note: To install SAP HANA on vsphere, follow the SAP HANA Server Installation and Update Guide and Best Practices and Recommendations for Scale-up Deployments of SAP HANA on VMware vsphere documentation. DDBDA software with the same parameters settings (including DEVICE_HOST, DEVICE_PATH, DDBOOST_USER, and CLIENT) as the physical HANA has been installed on the virtual HANA server. Note: Follow the DDBDA for SAP configuration section to install and configure DDBDA for virtual SAP HANA. Test validation You can use the following steps to validate the migration: 1. Query the record count of the physical HANA database table and the OS version, as shown in Figure 10. You use this later to validate the results after the virtual HANA restore. Figure 10. Query record count of physical HANA database table and OS version 2. With HANA Studio, initiate a data backup for the physical HANA database, select Backint for Destination Type, and type 4migration for Backup Prefix, as shown in Figure 11. Record the backup name, because you need it next for the virtual HANA restore. Figure 11. Physical HANA backup 18

19 3. Initiate a recovery SAP HANA database to a specific data backup operation through SAP HANA Studio. For virtual HANA recovery, specify the same Destination Type and Backup Prefix settings as the physical HANA backup, as shown in Figure 12. Figure 12. Virtual HANA recovery 4. Start the recovery operation. Validation results We verified the table records count and OS version from the recovered virtual HANA database. Figure 13 shows the table records count matching the physical HANA with the OS patch upgraded. The HANA database is migrated to a virtual machine with a different OS version using DDBDA and the data is validated. Figure 13. Validate table records count and OS version on virtual HANA Virtual HANA backup and recovery with DDBDA This test scenario validates that DDBDA integrated with the SAP HANA BACKINT backup solution is compatible with the virtual HANA database. The testing includes: Reducing network bandwidth requirements with DD Boost Recovering virtual HANA to its most recent time Recovering virtual HANA to a specific point-in-time 19

20 Reducing network bandwidth requirements with DD Boost SAP HANA only supports full database backups that result in a significant amount of data requiring large network bandwidth. Without DD Boost, the backup application sends a full database backup to Data Domain for deduplication. Figure 14 shows the network usage as 130 MiB/s for a virtual HANA backup without DD Boost. Figure 14. Network usage without DD Boost Note: Mebibyte per second (MiB/s) is a unit of data transfer rate equal to 1,048,576 bytes per second. This is almost 5 percent more than the more commonly used megabyte per second (MB/s), equal to 1,000,000 bytes per second. After DD Boost is integrated with the SAP HANA BACKINT, only unique data is transferred through the network. This significantly reduces the network bandwidth requirements. When we performed virtual HANA backup with DD Boost, as shown in Figure 15, the average network usage is only 0.5 MiB/s. Figure 15. Network usage with DD Boost 20

21 Recovering virtual HANA to its most recent state Recovery of virtual HANA to its most recent state is required when database data or log areas become unusable due to an issue, such as data or log files being damaged by false operations, a vsphere data store failure, and so on. In this solution, we validated a virtual HANA recovery to its most recent state with DDBDA by simulating data file corruption. Test procedure You can use the following test validation steps for your recovery: 1. Query how many table records are in the virtual HANA database after 1,000 records are inserted, as shown in Figure 16. You use this later to validate the restore results. Figure 16. Query table records count before database crash 2. Delete one HANA data file manually to simulate a data file crash. 3. Restart the virtual HANA database. Due to the missing data file, the restart fails. 4. In the SAP HANA Studio recovery window, select Recover the database to its most recent state for Specify Recover Type. 5. Specify the log backups location and select the latest available data backup. Figure 17 shows an example of this. Figure 17. Recover virtual HANA database to its most recent time 6. Start the recover operation. 21

22 Validation results After starting the virtual HANA database that was recovered, you can then verify the table records count. For our test scenario, Figure 18 shows how the table records match the values recorded before data file crash. Figure 18. Validate table records count after database recovery Recovering virtual HANA to a specific point in time Recovery of virtual HANA to a specific point in time is required when a logical error occurs such as accidental deletion of table records or a dropped table. In this solution, we delete some table records to simulate a database logic error. Using DDBDA, we then recover the virtual HANA to the time before the table records were deleted. Test procedure You can use the following test validation steps for your recovery: 1. Query the current table records count and timestamp. For example, as shown in Figure 19. Figure 19. Query current table records count and timestamp 2. Drop one table to simulate a database logic error, as shown in Figure 20. Figure 20. Simulate database logic error 3. In the SAP HANA Studio recovery window, select Recover the database to the following point in time as the recovery type and specify the point-in-time from step 1 in the Date and Time fields, as shown in Figure

23 Figure 21. Virtual HANA database point-in-time recover 4. Specify a log backups location and select a latest available data backup. 5. Start the recover operation. Validation results After the recovery, we started the recovered virtual HANA database and verified the table records count. Figure 22 shows that the table records match the values recorded before the table records were deleted. Figure 22. Validate table records number after database point-in-time recovery As our tests validated, DDBDA protects the SAP HANA database with much less network bandwidth consumption and successfully recovers databases to the most recent time or to a specific point-in-time. For full SAP environment protection that includes applications, such as ERP or BI, EMC recommends that you use additional backup software to regularly back up the operating system, instance profile, transport domain configuration file, and other critical files that are located under the /sapmnt, /usr/sap/, and /hana/ shared file systems. 23

24 Automate backup through CLI and SAP GUI SAP HANA database backup can be initiated either through HANA Studio or executing CLI on the HANA database server. To schedule a regular backup automatically, you can either add an entry to the crontab on the database server, or use third-party job scheduling software to call the CLI, such as UC4 or similar. Perform the following steps to configure an SAP HANA scheduled backup of database data with Data Domain: 1. Set the database base parameters in the backup script, as shown in the Appendix, and near the beginning of the script, set the following: hana_sid: Specify the SAP HANA System ID (SID) hana_instance: Specify the SAP HANA instance number hdbsql_cmd: Specify the full path to hdbsql Note: The script in the Appendix provides example parameter settings. 2. Create SAP HANA user key and set credential parameters. The SAP HANA user key takes the higher precedence because it is more secure than the plain username/password (the password can be leaked through the process list). In this script, we use user key BACKUP created by the hdbuserstore command as shown in Figure 23. Figure 23. Create SAP HANA user key 3. Then set the following parameter in the script: hana_key: Specify the SAP HANA user key for backup. 4. Add a crontab entry to enable the automated backup by calling a backup script. The following example entry sets the SAP HANA database backup at 2 AM every day: 0 2 * * * /usr/sap/pv2/home/backuphana.sh The SAP Basis administrator can also schedule a backup of SAP Business Suite on HANA through transaction code DB13 in the SAP GUI: 1. Select BACKINT for Destination Type in the Action Parameters tab, as shown in Figure

25 Figure 24. Select backup destination type in SAP GUI 2. Define a recurrence pattern in the Recurrence tab, as shown in Figure 25. Figure 25. Define recurrence pattern in SAP GUI Test validation The Backup Catalog in HANA Studio logs the status of the scheduled database backups. The green squares indicate a successful backup, as shown in Figure

26 Figure 26. HANA backup status in HANA Studio 26

27 Conclusion Summary Findings EMC Data Domain Boost for SAP HANA gives you, the application owners, direct control over backups to a Data Domain system by integrating the SAP-certified BACKINT API with DD Boost. It enables virtual HANA migration, with backup and restore operations using SAP HANA Studio and SAP HANA CLI. The virtual SAP HANA backup and restore with DDBDA for SAP HANA test results presented in this paper confirm that this solution: Reduces network utilization by up to 99 percent, because DDBDA avoids network resource conflicts, especially for multiple virtual SAP HANA servers on a single ESXi server environment. Easily migrates existing physical SAP HANA databases to virtual HANA databases for more rapid provisioning, zero downtime, and low TCO benefits. Easily restores virtual HANA backups with the most recent or a specific pointin-time backup, including manual and automated backups through CLI and SAP GUI. 27

28 References EMC documentation SAP documentation VMware documentation For additional information, refer to the following on EMC.com and EMC Online Support: EMC Data Domain Deduplication Storage Systems - SAP HANA Data Protection EMC DATA DOMAIN BOOST FOR SAP HANA Technical Review EMC Data Domain Boost for Databases and Applications Administration Guide EMC Data Domain Boost for Databases and Applications -- Configuring SAP HANA Backup, Recovery, and Deletion with SAP HANA Studio For additional information, refer to the following on the SAP website: SAP Note Single SAP HANA VM on VMware vsphere in production SAP Note SAP HANA Support for VMware Virtualized Environments SAP Note FAQ: SAP HANA Database Backup & Recovery SAP Note Homogeneous System Copy Steps on SAP HANA SAP HANA Administration Guide - SAP HANA Platform SPS 08 SAP HANA Server Installation and Update Guide - SAP HANA Platform SPS 08 SAP HANA Guidelines for Being Virtualized with VMware vsphere For additional information, see refer to the following on VMware.com: SAP HANA on VMware vsphere 5.5 Best Practices Resource Guide Best Practices and Recommendations for Scale-up Deployments of SAP HANA on VMware vsphere 28

29 Appendix The following shell script is provided as an example to use Date Domain Boost for a SAP HANA BACKINT backup. It can be called by a crontab entry to enable an automated backup. Shell script: backuphana.sh #!/bin/bash ################################################ # Specify the SAP HANA System ID, SID. For example: # hana_sid=pv2 # # Specify the SAP HANA instance number. For example: # hana_instance=00 # # Specify the full path to hdbsql, for example: # hdbsql_cmd=/usr/sap/pv2/hdb00/exe/hdbsql ################################################ hana_sid= hana_instance= hdbsql_cmd= ################################################ # Specify the SAP HANA user key for backup. This key # is created by the hdbuserstore tool. For example: # hana_key=backup ################################################ hana_key= # Construct the profix for the backup name. # Use backup start time as the profix for backup name bk_start_time=$(date +%Yy_%mm_%dd_%Hh_%Mm) backintpath="/usr/sap/${hana_sid}/sys/global/hdb/backint/" data_bk_cmd="backup data using backint ('${backintpath}${bk_start_time}')" # Construct the credential for backup hana_credential="-i $hana_instance -U $hana_key" # Construct the SAP HANA backup command. run_bk="$hdbsql_cmd $hana_credential \"$data_bk_cmd\"" # Execute backup command $run_bk 29