h13937 Saphana Networker Wp

7/25/2019 h13937 Saphana Networker Wp

1/26

White Paper

EMC Solutions

Abstract

This White Paper validates the functionality of EMC NetWorker as a tool forprotecting SAP HANA systems through NetWorker Module for SAP (NMSAP),while continuing to protect other data center systems, on both physical andvirtualized environments, with comprehensive, integrated backup and restorefacilities.

February 2015

PROTECTING SAP HANA WITH EMCNETWORKER

Efficient SAP HANA migration from physical to virtualizedenvironments

Easy scheduling of routine backup


2/26

Protecting SAP HANA with EMC NetWorker

White Paper

2

Copyright 2015 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of itspublication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes norepresentations or warranties of any kind with respect to the information in thispublication, and specifically disclaims implied warranties of merchantability orfitness for a particular purpose.

Use, copying, and distribution of any EMC software described in thispublication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC CorporationTrademarks on EMC.com.

All trademarks used herein are the property of their respective owners.

Part Number H13937


3/26

3Protecting SAP HANA with EMC NetWorker

White Paper

Table of contents

Executive summary ............................................................................................................................... 5

Business case .................................................................................................................................. 5

Solution overview ............................................................................................................................ 5

Key results/ recommendations ........................................................................................................ 5

Introduction.......................................................................................................................................... 6

Purpose ........................................................................................................................................... 6

Scope .............................................................................................................................................. 6

Audience ......................................................................................................................................... 6

Technology overview ............................................................................................................................ 7

Overview .......................................................................................................................................... 7

Hardware resources..................................................................................................................... 8

Software resources ...................................................................................................................... 8

EMC NetWorker ................................................................................................................................ 8

EMC NetWorker Module for SAP (NMSAP) ......................................................................................... 8

NMSAP features specific to SAP HANA.............................................................................................. 9

SAP HANA database ......................................................................................................................... 9

Single-host configuration (scale-up) .......................................................................................... 10

Multi-node cluster configuration (scale-out) .............................................................................. 10

SAP HANA persistence ................................................................................................................... 11

SAP HANA on vSphere .................................................................................................................... 12

Testing and validation ........................................................................................................................ 14NMSAP for SAP HANA configuration ............................................................................................... 14

Migrating from a physical to a virtualized environment using NMSAP ............................................. 16

Test validation steps ................................................................................................................. 17

Validation results ...................................................................................................................... 18

Virtual HANA backup and recovery with HANA Studio and NMSAP .................................................. 18

Recovering virtual HANA to its most recent state ........................................................................ 18


Recovering virtual HANA to a specific point in time .................................................................... 20


Automate backup through NetWorker console and SAP GUI ........................................................... 21


Conclusion ......................................................................................................................................... 25

Summary ....................................................................................................................................... 25

Findings ......................................................................................................................................... 25


4/26


White Paper

4

References.......................................................................................................................................... 26

EMC documentation ....................................................................................................................... 26

SAP documentation ....................................................................................................................... 26

VMware documentation ................................................................................................................. 26


5/26


White Paper

Executive summary

When adding SAP HANA to the data center portfolio, a key concern is the need fornew procedures and tools for its effective implementation. This concern is justified,as experienced IT professionals know that dispersion of technology stacks, tools, andprocesses can entail a greater risk of IT failure, more difficulty when implementing

change, and higher operational cost and complexity.

In many organizations, IT processes are organized so that a central tool is used toprotect and recover data within the data center, along with consistent processes tomanage backup and restore. These tools and processes are usually operated by ateam implementing a company-wide data protection strategy based on the keyservice-level objectivesRecovery Time Objective (RTO) and Recovery Point Objective(RPO).

With earlier versions of SAP HANA, organizations usually had to add yet more tools,processes, and skillsets to back up and restore SAP HANA, since the built-in optionswere quite limited.

With SAP HANA SPS05 came the HANA BACKINT interface, which enables integrationwith third-party backup tools. This allowed EMC to develop that integration into EMCNetWorker, enabling customers to keep their data center practices consistent byusing a single tool to protect SAP HANA and other data center applications, acrossboth physical and virtualized environments.

EMC NetWorker Module for SAP (NMSAP) is an add-on module for the NetWorkerserver and client that provides backup and recovery services for SAP HANA. Databaseadministrators can continue to use existing, familiar workflows to protect virtual SAPHANA with NMSAP. The solution described in this paper covers NMSAP configuration,and automatic backup and test validation including virtual SAP HANA migration,

backups, and recovery.

This solution shows that the NMSAP delivers:

Easy migration of SAP HANA from a physical to a virtualized environment

Compatibility between the NMSAP backup solution and the virtual HANAdatabase

Easy scheduling of routine backups by the NetWorker console

Business case

Solution overview

Key results/recommendations


6/26


White Paper

6

Introduction

This White Paper demonstrates the functionality of EMC NetWorker for backup andrestore of SAP HANA applications on both physical and virtualized environments,using SAP HANA Studio or SAP NetWeaver DBA Cockpit, and NetWorkers GUI. Thepaper aims to show that EMC NetWorker Module for SAP (NMSAP) can enable

organizations to consolidate scheduling, management, and reporting of backup andrecovery across the data center, using a single tool that also backs up SAP HANAdatabases.

This document provides test validation of migration, backup, and recovery of virtualSAP HANA with NMSAP and serves the following purposes:

Introducing the key solution technologies

Describing the key business benefits of using NMSAP with virtual SAP HANA

Describing how to configure NMSAP for virtual SAP HANA migration andbackup

Describing how to recover virtual SAP HANA with NMSAP

SAP does not currently support incremental or differential data backups. For moreinformation on SAP HANA backup and recovery, refer to the SAP HANA AdministrationGuideand SAP Note 1642148.

To refresh or repurpose a SAP application running on HANA (with SID changed), SAP

does not currently support backint.

This document is intended for data center architects who define backup and recoverystandards for the data center (including SAP HANA systems), as well as for SAP

system administrators who wish to integrate SAP HANA with EMC NetWorker. Thisdocument may also be useful to architects and administrators responsible forimplementing backup and recovery strategies for SAP HANA across physical andvirtualized environments.

Purpose

Scope

Audience


7/26


White Paper

Technology overview

In this solution, an external storage array provides the persistence for data and logvolumes of both the physical and virtual HANA systems, as shown inFigure 1.EMCNetWorker is used to back up and restore the HANA database, and to migrate it froma physical environment to a virtualized environment.

Figure 1.

Solution architecture

Overview


8/26


White Paper

8

Hardware resources

Table 1 describes the hardware components used in the deployment.

Table 1.

Solution hardware resources

Equipment Quantity Configuration

Storage 1 EMC VNX8000

ESXi host 2 Four 10-core CPUs, 384 GB RAM

Physical host 1 Four 10-core CPUs, 384 GB RAM

Ethernet switches 2 10 Gb Ethernet (GbE)

SAN switches 2 8 Gb FC

Software resources

Table 2 describes the software components used in the deployment.

Table 2.

Solution software resources

Software Version Description

EMC NetWorker 8.2 Backup and restoresoftware

EMC NetWorker Module forSAP

8.2 NetWorker Module for SAPbackup and recover

EMC PowerPath/VE 5.8 Multipathing software

EMC Block OperatingEnvironment

5.33 Operating environment forVNX

SUSE Linux 11 SP3 Operating system for SAPHANA

VMware ESXi 5.5.0 Hypervisor

VMware vCenter Server 5.5.0 vSphere managementserver

SAP HANA database SPS08 SAP in-memory database

EMC NetWorker is a storage management software suite that provides backup,recovery, and other services to hosts with a wide variety of operating systems anddata types. NetWorker products for different operating systems are interoperable.

NetWorker provides the flexibility to design a storage management system that worksbest with the current computing environment.

EMC NetWorker Module for SAP (NMSAP) is an add-on module for the NetWorkerserver and client that provides backup and recovery services for SAP HANA and SAPwith Oracle data. NMSAP provides a backup-restore interface between the SAP

EMC NetWorker

EMC NetWorkerModule for SAP(NMSAP)


9/26


White Paper

backup and restore interfaces, the NetWorker server, and the NetWorker ManagementConsole (NMC).

A SAP HANA database holds most of the data in memory but also uses persistentstorage on disk. During normal database operations, the data is automatically savedfrom memory to the disk at regular intervals. All data changes are also captured in theredo log on disk, which is updated after each committed database transaction. Thedata on disk must be backed up to ensure protection against disk failure. NMSAP is

integrated with the SAP HANA BACKINT interface program, hdbbackint, to provide thebackup, deletion, inquiry, and recovery services for SAP HANA database data andredo logs. Based on the features that SAP HANA supports, NMSAP supports thefollowing SAP HANA data operations:

Manual and scheduled backups

Online backups

Full database backups

Redo log backups

Recovery of a database to its most recent state, a specific point in time, aspecific data backup, or a log position

Recovery to the original host or an alternate host

Deduplication backups and restores with a Data Domain system

Client Direct backups to an advanced file-type device (AFTD)

Configuration with the Backup Configuration Wizard

NMSAP works with the following SAP HANA interfaces on the database server toperform backup and restore operations:

SAP HANA command line interface (CLI) with the hdbsqlcommand SAP HANA Studio GUI

SAP DBA Cockpit in the Computing Center Management System (CCMS) GUI

SAP HANA is an in-memory database that combines transactional data processing,analytical data processing, and application logic processing in memory. This designenables real-time online application processing (OLAP) analysis on an onlinetransaction 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 bySAPs hardware partners. It can also be delivered under SAPs Enterprise SharedStorage and Tailored Data center Integration program, which allows customers to usetheir existing infrastructure.

NMSAP featuresspecific to SAPHANA

SAP HANAdatabase


10/26


White Paper

1

As shown inFigure 2,the SAP HANA architecture can be deployed in two basicconfigurations:

Single-host (scale-up)

Multi-node cluster (scale-out)

Figure 2.

SAP HANA system architecture

Single-host configuration (scale-up)

In an SAP HANA single-host configuration, all SAP HANA components run on a singleserver. The persistence layer resides on server internal flash and SAS disks. Thescalability of the database is limited by the amount of RAM that can be installed inthe 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 acrossmultiple servers. The scalability of the database is achieved by adding servers to thecluster. Shared storage is required for a multi-node cluster configuration to provideHA functionality. Each node uses its own persistent devices on the shared storagelayer. 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 thestorage persistence.

In a distributed scale-out environment, one node (usually the first one installed) isthe master node. It handles the workload of the NetWeaver stack, the statistics andthe tables located in the row store. For a HANA scale-out database, it is a requirementto have at least three nodes. In a two-node landscape, the table distribution and thedegree of parallel processing do not usually provide worthwhile benefits over asingle-node configuration.


11/26


White Paper

The SAP HANA in-memory database holds the bulk of its data in memory for maximumperformance but still uses persistent storage to provide for startup and recovery incase of a failure. The SAP HANA persistence uses two volumes, Data and Log, asshown inFigure 3.

Figure 3.

The SAP HANA persistence layer

Data and log information are automatically saved to disk at regular savepoints asshown inFigure 4 and described in the following sections.

Figure 4.

Persistence mechanism

Data Volume

Data in memory is asynchronously written to the persistence mechanism as asavepoint every five minutes by default. This data volume capture method uses alocking mechanism to prevent modification of pages while copying modified pagesand capturing open transactions before finally increasing the savepoint version andreleasing the lock.

SAP HANApersistence


12/26


White Paper

1

Log Volume

The log file system captures all database transactions since the last savepoint. It issaved to disk continuously and synchronously after each database transactioncommit at the end of the disk write operation, or if the internal log buffer (1 MB) isfull. This information allows the database to be rolled back to any point in time, aswell as to back out of, or redo, individual transactions. In case of failure, the logvolume allows the database to be restored from the last savepoint onwards.

SAP HANA now runs in production on vSphere, the foundation of the VMware vCloudSuite. You can combine the power of the SAP HANA in-memory platform with vSphereto achieve faster time-to-value, better service levels and lower TCO for yourproduction environments, and take the next step to the software-defined data center.

As shown inFigure 5,the benefits include:

Faster Time-to-ValueAccelerate and automate provisioning and reducedeployment time to hours rather than days. Use template provisioning toensure consistency and scalability across environments.

Better Service LevelsWith vSphere vMotion, live-migrate SAP HANA acrosshosts in minutes with zero downtime and zero data loss. Ensure 99.9% highavailability and maximize uptime by automatically restarting SAP HANA virtualmachines with vSphere High Availability. Automatically manage peak analyticworkloads.

Lower TCOReduce capital expenditure (CapEx) by 70% and operationalexpenditure (OpEx) by 56% through greater utilization of existing resourcesand infrastructure. Unify and manage SAP HANA with the rest of yourvirtualized data center. Improve resource utilization through simplifiedoperations management.

SAP HANA onvSphere


13/26


White Paper

Figure 5.

SAP HANA on vSphere benefits

For detailed information on virtualizing SAP HANA with VMware vSphere, refer to SAPNote 1788665 and to theVMware documentationsection.

A variety of techniques and tools are available to customers when migrating SAP

HANA on vSphere. InMigrating from a physical to a virtualized environment usingNMSAP,we show how to migrate SAP HANA on vSphere using NMSAP.


14/26


White Paper

1

Testing and validation

This section provides the detailed information on test scenarios and results. Weperformed the testing of a single-node HANA backup and restore on a virtualizedenvironment. The test scenarios included:

NMSAP for HANA configuration

Migration from a physical to a virtualized environment using NMSAP

On-demand virtual HANA backup and recovery with NMSAP

Automated backup through the NetWorker console and SAP GUI

NMSAP is an add-on module for the NetWorker server and client software. In thissolution, we use the followings steps to configure the NMSAP for SAP HANA afterinstalling the NetWorker client and NMSAP software on the SAP HANA node.

1. Create a SAP HANA user key and set the credential parameters. The SAP HANAuser key takes the higher precedence because it is more secure than thestandard username/password combination, as a password can be leakedthrough the process list.

Create a user key BACKUP with the hdbuserstorecommand, as shown inFigure 6.This key is then used in step 3.

Figure 6.

Using the hdbuserstore command

2. Log in to the NetWorker console and right-click Clientsin the Configurationview under the NetWorker server name. Select

New Client Wizard

as shown inFigure 7.

Figure 7.

Create a NetWorker client on the NetWorker console

3. Specify the options and values required for the backup configuration on eachwizard page that appears. In this solution, we specify S P H N asapplication type and the user key B CKUP, as created in step 1. The SID,

NMSAP for SAPHANAconfiguration


15/26


White Paper

instance number, and hdbsql directory are detected automatically by theNMSAP module, as shownFigure 8.

Figure 8.

Specify options in New Client Wizard

4. Create a new group for the new client in the wizard.

5.

On the HANA node, manually create the /usr/sap//SYS/global/hdb/optsubdirectory if it does not already exist.

6. Copy the /usr/sbin/hdbbackint file to that directory or create a symbolic linkthat points from /usr/sap//SYS/global/hdb/opt/hdbbackint to theexecutable file.

7. Modify the parameter settings of the /etc/init_hana_nmsap.utl file, which isthe NMSAP for SAP HANA template configuration file. In this solution, we setthe parameters as shown inTable 3.

Table 3.

Parameter settings of NMSAP for SAP HANA configuration file

Parameter Value Comments

server nw82.sap.sse.local Hostname of the NetWorker server

client saphandb Hostname of the NetWorker client

pool datadomain Any pool defined in the NetWorker server

Note: HANA full backups can be directed to any device supported by NetWorkersuch as tape drives, virtual disk library, basic file, or Data Domain. In this solution,Data Domain is recommended since SAP HANA full backups benefit greatly fromdata deduplication.


16/26


White Paper

1

8.

Enable the hdbbackintparameter file in SAP HANA Studio. As shown inFigure9,the location of the parameter file /etc/init_hana_nmsap.utl is specified on

the Configurationtab of the HANA Studio Backup console. Select Use thesame parameter file data backup and log backupto use thesameconfiguration file for both data and log backup.

Figure 9.

Specify the location of NMSAP configuration file in HANA Studio

For full SAP environment protection (including applications such as ERP, BI, and soon), we strongly recommend using NetWorker's powerful features to schedule regularVMware image and critical files backup. This can include the instance profile, thetransport domain configuration file, and other critical files under the /sapmnt,/usr/sap/, and /hana/shared file systems. Additional NetWorker clients can becreated for virtual machines for either traditional backup or VMware ConsolidatedBackup (VCB).

For detailed configuration information, refer to the documents EMC NetWorkerModule for SAP Administration Guideand EMC NetWorker Administration Guide

Release 8.2.

This test scenario validates that NMSAP can be used for migrating SAP HANA from aphysical to a virtual platform with a different OS patch level. Beyond that particularvalidation, this scenario can also be used to restore the backup to a different host forrepurposefor example, using the restored SAP system as a TEST system with thesame SID but using a different hostname.

In this solution, we restore to a virtual SAP HANA database from the backup of aphysical HANA saved on Data Domain using NMSAP. The OS patch of the virtual SAPHANA database upgrades from SUSE Linux 11 SP2 to SP3 by migration.

Before you perform a physical-to-virtual SAP HANA migration, the followingprerequisites must be met:

A virtual SAP HANA database with the same SID, UID (User ID), and GID (GroupID) as the physical HANA has been installed.

Note: Follow the SAP HANA Server Installation and Update Guideand Best Practicesand Recommendations for Scale-up Deployments of SAP HANA on VMware vSpheredocuments to install SAP HANA on vSphere.

Migrating from aphysical to avirtualizedenvironment usingNMSAP


17/26


White Paper

NMSAP software with the same parameter settings (including server, client,and pool) as the physical HANA has been installed on the virtual HANA server.

Note: FollowNMSAP for SAP HANA configurationon page14 to install and configureNMSAP for virtual SAP HANA.

Test validation steps

Perform the following steps to validate:

1.

Query the record count of the physical HANA database table and OS versionas shown inFigure 10.This information is later used to validate the resultafter the virtual HANA restore.

Figure 10.

Query the record count of the physical HANA database table and OS version

2. In HANA Studios physical HANA backup console, perform data backup forphysical HANA. Select Backintfor Destination Typeand type 4migrationforthe backup name in the Backup Prefixtext box, as shown inFigure 11.Thebackup name is later used for the virtual HANA restore.

Figure 11.

Backup physical HANA through HANA Studio

3. In HANA Studios virtual HANA backup console, initiate a recovery SAP HANAdatabase to a specific data backup operation through HANA Studio. For

virtual HANA recovery, specify the same Destination Typeand Backup Prefixsettings as the physical HANA backup, as shown inFigure 12.


18/26


White Paper

1

Figure 12.

Virtual HANA recover

4. Start the recovery operation.

Validation results

We verified the table records count and OS version from the recovered virtual HANAdatabase.Figure 13 shows the table records count matching the values recorded onthe physical HANA with the OS patch upgraded. The HANA database is migrated to avirtual machine with a different OS version using NMSAP for HANA and the data isvalidated.

Figure 13.

Validate table records count and OS version on virtual HANA

This test scenario validates that NMSAP integrated with the SAP HANA BACKINTbackup solution is compatible with a virtual HANA database. The testing includes:

Recovering virtual HANA to its most recent state

Recovering virtual HANA to a specific point-in-time

Recovering virtual HANA to its most recent state

Recovery of virtual HANA to its most recent state is required when database data orlog areas become unusable. This can happen if data or log files are damaged by afalse operation, a vSphere data store failure, and so on. In this solution, we validatevirtual HANA recovery to its most recent state with HANA Studio and NMSAP bysimulating data file corruption.

irtual HANAbackup andrecovery withHANA Studio and

NMSAP


19/26


White Paper

Test procedure

1.

Query how many table records are in the virtual HANA database after 1,000records are inserted, as shown inFigure 14.This number is later used tovalidate the restore result.

Figure 14.

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

4.

In the SAP HANA Studio Specify Recovery Typewindow, select Recover thedatabase to its most recent statefor the recovery type.

5. Specify the log backup location and select the latest available data backup,as shown inFigure 15.

Figure 15.

Recover virtual HANA database to its most recent state


Validation results

We started the recovered virtual HANA database and verified the table records count.Figure 16 shows that the table records match the values recorded before the table

records were deleted.

Figure 16.

Validate table records count after database recovered


20/26


White Paper

2

Recovering virtual HANA to a specific point in time

Recovery of virtual HANA to a specific point in time is required when a logical erroroccurs such as accidental deletion of table records or a dropped table. In thissolution, we delete one table to simulate a database logic error. Using HANA Studioand NMSAP, we then recover the virtual HANA to the point in time before the tablewas dropped.

Test procedure

1. Query the current table records count and timestamp, as shown inFigure 17.

Figure 17.

Query current table records count and timestamp

2. Drop one table to simulate a database logic error, as shown inFigure 18.

Figure 18.

Simulate database logic error

3. In the SAP HANA Studio Specify Recovery Typewindow, select Recover the

database to the following point in timeas the recovery type. Specify the point

in time from step 1 in the Dateand Timefields, as shown inFigure 19.

Figure 19.

Virtual HANA database point-in-time recovery

4. Specify the log backup location and select the latest available data backup.



21/26


White Paper

Validation results

We started the recovered virtual HANA database and verified the table records count.Figure 20 shows that the table records match the values recorded before the tablerecords were deleted.

Figure 20.

Validate table records number after database point-in-time recovery

SAP HANA database backup can be initiated either through HANA Studio or throughthe NetWorker console. The NetWorker console enables centralized management ofNetWorker components (including NetWorker server, various clients, and backupdevices) and comprehensive data protection options within the enterprise. This testscenario validates that automating the backup solution is compatible with a virtualHANA database.

Test procedure

1.

In HANA Studio, ensure Enable Automatic Log Backupis selected, as showninFigure 21.

Figure 21.

Enable Automatic Log Backup setting

2. In the NetWorker console, open the group properties of the virtual HANAclient.

3. Set the Start time ofthe group, as shown inFigure 22.The NetWorker client inthe backup group begins automatic scheduled backups according to the starttime of the group.

Figure 22.

Set Start time in the NetWorker console

Automate backupthrough NetWorkerconsole and SAPGUI


22/26


White Paper

2

4. Set a schedule for the group. NetWorker software ships with preconfiguredschedules to meet varied backup requirements. New schedules also can be

created to accommodate specific needs. We used Full Every Dayfor SAPHANA data protection, as shown inFigure 23.

Figure 23.

Set schedule in the NetWorker console

The SAP Basis administrator can also schedule backup of SAP Business Suite onHANA through transaction code DB13 in the SAP GUI, as follows:

1. Select BACKINTfor Destination Typein theAction Parameterstab, as showninFigure 24.


23/26


White Paper

Figure 24.

Select backup destination type in SAP GUI

2. Define a recurrence pattern in the Recurrencetab, as shown inFigure 25.

Figure 25.

Define a recurrence pattern in SAP GUI


24/26


White Paper

2

Validation results

Check the Save Sets of the NetWorker volumes, as shown inFigure 26.SAP HANAdata and log backup are automatically saved at the time scheduled.

Figure 26.

Volume Save Sets view in NetWorker console


25/26


White Paper

Conclusion

EMC NMSAP for HANA is an add-on module for the NetWorker server and client thatprovides backup and recovery services for SAP HANA. It enables virtual HANAmigration, backup and restore operations with SAP HANA Studio, and automatedbackup.

The test results for virtual SAP HANA backup and restore with NMSAP for HANApresented here confirm the following:

NetWorker is an enterprise-class data protection solution that meets specificneeds. NMSAP for HANA enables comprehensive SAP HANA data protectionoptions within the enterprise.

NMSAP enables easy migration to virtual SAP HANA using existing physicalSAP HANA database backup. Migrating to a virtualized environment providesthe benefits of rapid provisioning, zero downtime, and low TCO.

The NMSAP backup solution is compatible with a virtual HANA database

including manual and automated backup, specific backup set restore, mostrecent restore, and point-in-time restore.

Summary

Findings


26/26

References

For additional information, see the following EMC documents (available on EMC.comand on the EMC online support website):

EMC NetWorker Module for SAP Installation Guide

EMC NetWorker Module for SAP

Administration Guide

EMC NetWorker and EMC Data Domain Boost Deduplication DevicesIntegration Guide

EMC NetWorker Release 8.2 Administration Guide

EMC NetWorker Software Compatibility Guide

EMC NetWorker Module for SAP Release 8.2 and Service Packs

For additional information, see the SAP documents listed below.

SAP Note 1995460 - Single SAP HANA VM on VMware vSphere in production

SAP Note 1788665 - SAP HANA Support for VMware Virtualized Environments

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 the VMware documents listed below.

SAP HANA on VMware vSphere 5.5 Best Practices Resource Guide

Best Practices and Recommendations for Scale-up Deployments of SAP HANAon VMware vSphere

EMCdocumentation

SAPdocumentation

Mwaredocumentation

h13937 Saphana Networker Wp

Documents

Transcript of h13937 Saphana Networker Wp