Download - Best Practices · SAP Best Practices This document summarizes operation practices in common SAP application scenarios. Each practice provides detailed solution description and operation

SAP

Best Practices

Issue 02

Date 2019-07-12

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,information, and recommendations in this document are provided "AS IS" without warranties, guaranteesor representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 02 (2019-07-12) Copyright © Huawei Technologies Co., Ltd. i

Contents

1 SAP Best Practices................................................................................................................... 1

2 Best Practices for Uploading SAP Backups to the OBS Bucket.....................................22.1 Overview.................................................................................................................................................................................... 22.1.1 Object Storage Service....................................................................................................................................................... 22.1.2 Script........................................................................................................................................................................................ 22.1.3 Dependency........................................................................................................................................................................... 32.2 Preparations Before the Upload......................................................................................................................................... 32.2.1 Preparing the Environment.............................................................................................................................................. 32.2.2 Downloading Software...................................................................................................................................................... 32.2.3 Modifying the Configuration File................................................................................................................................... 42.2.4 Initializing obsutil................................................................................................................................................................ 62.3 Uploading Backups to the OBS Bucket............................................................................................................................72.3.1 Manually Running the Script........................................................................................................................................... 72.3.2 Calling by Other Scripts..................................................................................................................................................... 82.3.3 Configuring Scheduled Tasks........................................................................................................................................... 82.4 FAQs............................................................................................................................................................................................. 82.4.1 How Do I Download a Backup File of a Day from the OBS Bucket?................................................................ 92.4.2 How Can I Periodically Delete Backup Files from a Bucket or Change the Storage Class of BackupFiles?................................................................................................................................................................................................. 10

3 Best Practices of SAP with Enterprise Project Management...................................... 113.1 Overview.................................................................................................................................................................................. 113.2 Preparing Resources............................................................................................................................................................. 123.2.1 Obtaining Software...........................................................................................................................................................123.2.2 Configuring an Agency.................................................................................................................................................... 133.2.3 Uploading Software Packages...................................................................................................................................... 143.3 Creating an Enterprise Project..........................................................................................................................................163.4 Managing Templates........................................................................................................................................................... 183.4.1 Example Templates........................................................................................................................................................... 183.4.2 My Templates......................................................................................................................................................................213.5 Creating an Application...................................................................................................................................................... 253.5.1 Provisioning an SAP HANA Database........................................................................................................................ 253.5.2 Provisioning an SAP S/4HANA Application System............................................................................................... 303.5.3 Provisioning SAP Business One..................................................................................................................................... 30

SAPBest Practices Contents

Issue 02 (2019-07-12) Copyright © Huawei Technologies Co., Ltd. ii

3.6 (Optional) Managing Applications................................................................................................................................. 303.7 SAP Full Screen Monitoring...............................................................................................................................................323.7.1 Overview...............................................................................................................................................................................323.7.2 Installing SAP Monitoring Plug-ins............................................................................................................................. 333.7.2.1 SAP HANA (Single-Node Deployment Without HA Required)...................................................................... 333.7.2.2 SAP HANA (Single-Node Deployment With HA Required).............................................................................363.7.2.3 SAP S/4HANA (Single-Node Deployment Without HA Required)................................................................363.7.2.4 SAP S/4HANA (Single-Node Deployment With HA Required)...................................................................... 393.7.2.5 SAP S/4HANA (Distributed Deployment with HA Required)..........................................................................393.7.2.6 SAP S/4HANA (Distributed Deployment Without HA Required).................................................................. 403.7.2.7 SAP Business One...........................................................................................................................................................413.7.2.8 SAP ECC............................................................................................................................................................................. 423.7.3 (Optional) Upgrading Monitoring Plug-ins..............................................................................................................443.7.4 Adding a Monitoring Panel............................................................................................................................................ 453.7.5 Viewing the SAP Full Screen Monitoring Page....................................................................................................... 483.7.6 Viewing the Server Monitoring Page..........................................................................................................................533.7.7 Viewing the Monitoring.................................................................................................................................................. 533.7.8 Viewing Alarm Information........................................................................................................................................... 553.8 Expanding the Capacity of an EVS Disk........................................................................................................................ 563.9 Backing up Applications..................................................................................................................................................... 583.10 Restoring Applications...................................................................................................................................................... 593.11 Application Disaster Recovery........................................................................................................................................603.12 Viewing O&M Tasks...........................................................................................................................................................613.13 FAQs........................................................................................................................................................................................ 623.13.1 How Can I View All Enterprise Projects?.................................................................................................................623.13.2 Why Does a Member Account with the EPS Admin Policy Configured Through EPS Have NoPermissions to Add User Groups or Set Policies?..............................................................................................................623.13.3 How Do I Obtain the Enterprise Project ID?..........................................................................................................623.13.4 Why No Data Is Available After I Configured Application Monitoring Successfully on the SAP FullScreen Monitoring Page?.......................................................................................................................................................... 633.13.5 How Can I Add a Dedicated Account for the SAP Full Screen Monitoring?...............................................643.13.6 What Are the Metrics Displayed on the SAP Full Screen Monitoring?........................................................ 653.13.7 What Can I Do If SAP S/4HANA 1610 Fails to Obtain Monitoring Metrics?..............................................73

4 Best Practices of SAP Migration to HUAWEI CLOUD....................................................744.1 Overview.................................................................................................................................................................................. 744.1.1 Migration Scenarios.......................................................................................................................................................... 744.1.2 Migration Solutions.......................................................................................................................................................... 774.1.3 Related Cloud Services.....................................................................................................................................................814.2 Migration Procedure............................................................................................................................................................ 834.3 Migrating the SAP System from the x86 Platform to HUAWEI CLOUD............................................................ 844.3.1 Description........................................................................................................................................................................... 844.3.2 Solution Design.................................................................................................................................................................. 854.3.3 Preparing Resources......................................................................................................................................................... 91


Issue 02 (2019-07-12) Copyright © Huawei Technologies Co., Ltd. iii

4.3.4 Migrating Application Servers to HUAWEI CLOUD............................................................................................... 924.3.5 Migrating the Database to HUAWEI CLOUD...........................................................................................................944.3.6 Tests and Drills................................................................................................................................................................... 964.3.7 Switchover and Go-Live...................................................................................................................................................964.4 Migrating from a Third-Party Cloud to HUAWEI CLOUD....................................................................................... 974.4.1 Scenario Description......................................................................................................................................................... 974.4.2 Solution Design.................................................................................................................................................................. 984.4.3 Preparing Resources....................................................................................................................................................... 1004.4.4 Migrating Application Servers to HUAWEI CLOUD.............................................................................................1014.4.5 Migrating the Database to HUAWEI CLOUD........................................................................................................ 1014.4.6 Tests and Drills................................................................................................................................................................. 1014.4.7 Switchover and Go-Live................................................................................................................................................ 1014.5 Migrating from IBM or HP Midrange Computers to HUAWEI CLOUD............................................................1014.5.1 Scenario Description...................................................................................................................................................... 1014.5.2 Solution Design................................................................................................................................................................1024.5.3 Preparing Resources....................................................................................................................................................... 1054.5.4 Migrating Application Servers to HUAWEI CLOUD.............................................................................................1054.5.5 Migrating the Database to HUAWEI CLOUD........................................................................................................ 1054.5.6 Tests and Drills................................................................................................................................................................. 1074.5.7 Switchover and Go-Live................................................................................................................................................ 1074.6 Migrating SAP Applications Running on a Non-HANA Database to HUAWEI CLOUD SAP HANA.......1074.6.1 Scenario Description...................................................................................................................................................... 1074.6.2 Solution Design................................................................................................................................................................1084.6.3 Preparing Resources....................................................................................................................................................... 1094.6.4 Migrating Application Servers to HUAWEI CLOUD.............................................................................................1104.6.5 Migrating the Database to HUAWEI CLOUD........................................................................................................ 1104.6.6 Tests and Drills................................................................................................................................................................. 1104.6.7 Switchover and Go-Live................................................................................................................................................ 1104.7 Appendix................................................................................................................................................................................ 1104.7.1 Migration Solution Details........................................................................................................................................... 110

A Change History....................................................................................................................113


Issue 02 (2019-07-12) Copyright © Huawei Technologies Co., Ltd. iv

1 SAP Best Practices

This document summarizes operation practices in common SAP applicationscenarios. Each practice provides detailed solution description and operation guide,helping you easily use SAP services.

Table 1-1 SAP best practices

Best Practice Description

Best Practices forUploading SAP Backupsto the OBS Bucket

This section describes how to use scripts to callobsutil to back up local files to the OBS bucketand store copies locally within a certain period oftime.

Best Practices of SAPwith Enterprise ProjectManagement

This section describes how to create enterpriseprojects, manage templates, create applications,manage applications, manage and monitorapplications and resources using Enterprise ProjectManagement.

Best Practices of SAPMigration to HUAWEICLOUD

This section describes how to migrate the SAPsystem to HUAWEI CLOUD. HUAWEI CLOUDprovides an improved solution to help you migratewith higher efficiency and lower costs.

SAPBest Practices 1 SAP Best Practices

Issue 02 (2019-07-12) Copyright © Huawei Technologies Co., Ltd. 1

2 Best Practices for Uploading SAPBackups to the OBS Bucket

2.1 Overview

2.1.1 Object Storage ServiceObject Storage Service (OBS) is a cloud storage service that provides capabilitiesfor massive, secure, reliable, and cost-effective data storage. With OBS, you caneasily create, modify, and delete buckets, as well as upload, download, and deleteobjects.

OBS provides super large storage capacity that can store any type of files and issuitable for websites, enterprises, developers, and common subscribers. As a webservice, OBS provides service interfaces over Hypertext Transfer Protocol (HTTP)and Hypertext Transfer Protocol Secure (HTTPS). You can use OBS Console andOBS client to access and manage data stored on OBS from any computerconnected to the Internet anytime, anywhere. Besides, OBS supports REST APIs,facilitating data management and development of several types of upper-layerservice application. As a cloud service, OBS features flexible expansion and allowsthe infrastructure to be deployed in multiple regions, while maintaining highreliability. Therefore, you can access OBS in specific regions according to yourservice needs and experience rapid access speed at cost-effective prices.

For further details about OBS, see OBS Product Introduction.

2.1.2 ScriptThis script is developed using Python and applies to the Linux operating system.This script is used to upload local files to the OBS bucket and save copies locally.This script calls the obsutil to upload files to the OBS bucket.

obsutil is a command line tool for accessing OBS. You can use this tool to performcommon configurations in OBS, such as creating buckets, uploading anddownloading files/folders, and deleting files/folders. If you are familiar withcommand line interface (CLI), obsutil is recommended as an optimal tool forbatch processing and automated tasks.

For more information about obsutil, see Introduction to obsutil.

SAPBest Practices

2 Best Practices for Uploading SAP Backups to theOBS Bucket


https://support.huaweicloud.com/intl/en-us/productdesc-obs/en-us_topic_0045853681.html

https://support.huaweicloud.com/intl/en-us/utiltg-obs/obs_11_0001.html

2.1.3 DependencyThe script runs on the Linux operating system and is compatible with all Linuxversions. The script invokes obsutil. Table 2-1 shows the dependency between therunning environment of the obsutil and python.

Table 2-1 Dependency versions and description

Component/Module Requirement

Remarks HandlingMethod

Python The versionof Pythonmust bePython3.

Incompatibilityoccurs whenPython2 is used.

Upgrade thePython version.

2.2 Preparations Before the Upload

2.2.1 Preparing the EnvironmentBefore using obsutil, you need to register a cloud service account, use the OBSservice, create an IAM user, and obtain access keys (AKs and SKs). To ensureaccount and resource security, you are not advised to use the registered account toaccess OBS. Through the Identity and Access Management (IAM) service, you cancreate a user who has the permission to access OBS resources and performoperations on the OBS client.

Procedure

Step 1 Register an account and use OBS.

Step 2 Create an IAM user.

Step 3 Create Access Keys (AKs and SKs).

----End

2.2.2 Downloading SoftwareThis section describes how to download the obsutil_adapter.zip softwarepackage.

Procedure

Step 1 Log in to a server as user root using a key or password.

Step 2 On the CLI, download the obsutil_adapter.zip package and decompress it tothe /opt/huawei directory. The download address of software packages varies byregion. For details, see Table 2-2. The Hong Kong region is used as an examplehere.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/qs-obs/obs_qs_0000.html

https://support.huaweicloud.com/intl/en-us/clientogw-obs/obs_03_0035.html


wget https://obs-sap-ap-southeast-1.obs.myhwclouds.com/obsutil_adapter/obsutil_adapter.zip -P /opt/huawei

Table 2-2 Required software package

Name Description How to Obtain

obsutil_adapter.zip Softwarepackage

AP-Hong Kong: wget https://obs-sap-ap-southeast-1.obs.myhwclouds.com/obsutil_adapter/obsutil_adapter.zip -P /opt/huawei

AP-Bangkok: wget https://obs-sap-ap-southeast-2.obs.myhwclouds.com/obsutil_adapter/obsutil_adapter.zip -P /opt/huawei

SA-Johannesburg: wget https://obs-sap-af-south-1.obs.af-south-1.myhuaweicloud.com/obsutil_adapter/obsutil_adapter.zip -P /opt/huawei

cd /opt/huawei

unzip obsutil_adapter.zip -d obsutil_adapter/

NO TE

● obsutil_adapter.py: Script to be uploaded and executed. This script calls obsutil.● obsutil_adapter.cfg: Configuration file of this script● obsutil: the obsutil client● The log directory is /var/log/huawei/obsutil_adapter.

----End

2.2.3 Modifying the Configuration File

PrerequisitesYou have prepared the OBS bucket name.

Procedure


Step 2 Run the following command to modify the obsutil_adapter.cfg configuration fileand save it:

vi /opt/huawei/obsutil_adapter/obsutil_adapter.cfg

Step 3 Modify the configuration parameters by referring to Table 2-3 and save themodification.

SAPBest Practices



Table 2-3 Parameters

Parameter

Description ExampleValue

obs_path

Path of the OBS bucket to which the backups will beuploaded. You can enter the OBS bucket name andspecify a path after the bucket name. The format isbucket name/bucket path. Use the OBS bucket path youneed.

obs-sap/hana

retry_time

Number of retransmission attempts. For example, if itsvalue is set to 3, it indicates that if the upload fails, thesystem retries twice. If the upload still fails, the scriptexits.NOTE

The value of retry_time must be an integer.

3

modified_interval

Upload interval. The unit is minute. The files that aremodified within this period will not be uploaded. Forexample, if its value is set to 5, files that are modifiedwithin the last 5 minutes will not be uploaded.NOTE

The value of modified_interval must be an integer.

5

reserve_time

File reservation period. The unit is minute. For example,if its value is set to 2880, the files in thebackup_archive can be stored for 2880 minutes at mostlocally.NOTE

The value of reserve_time must be an integer.

2880

backup_path

Path that stores file backups. After the backup of a fileis complete, the file is moved to backup_archive.NOTE

Multiple paths are supported. Use commas (,) to separatepaths. For example: /hana/backup/data, /hana/backup/log

/hana/backup/data

backup_archive

Files that are successfully uploaded are archived in thisdirectory.When this script is executed, the files in thebackup_archive directory are queried first. If thedifference between the current time and the filecreation time exceeds the value of reserve_time, thefiles will be deleted. Otherwise, files will be backed upin the backup_path directory. After the backup of filesis complete, the files will be archived inbackup_archive.

/hana/backup/archive

SAPBest Practices



NO TE

● The backup_path and backup_archive directories must be independent from eachother. Each directory cannot be a subdirectory of another one. Ensure that the diskspace of the two directories is sufficient for storing backup files.

● To ensure the integrity of uploaded files, you cannot run the multiple scripts that havebeen uploaded at the same time. Otherwise, the script execution fails.

----End

2.2.4 Initializing obsutilBefore using obsutil, you need to configure the interconnection between obsutiland OBS, including the endpoint and access keys (AK and SK) of OBS. You can useobsutil to perform operations on OBS buckets and objects only after obtaining theOBS authentication.

Prerequisites● The obsutil has been downloaded. For details, see Downloading Software.● The access keys (AK and SK) have been obtained. For details, see Step 3 in

Preparing the Environment.

Procedure

Step 1 Run the following commands to initialize obsutil:

chmod +x obsutil

./obsutil config -i=ak -k=sk -e=endpoint

● ak: indicates the tenant access key, that is, the AK in Creating Access Keys(AK and SK).

● sk: indicates the tenant secret key, that is, the SK in Creating Access Keys(AK and SK).

● endpoint: The IP address of an endpoint varies from region to region. Table2-4 lists OBS endpoint IP addresses. For more information about OBSendpoints, see Regions and Endpoints.

Table 2-4 Endpoints

RegionName

EndpointRegion

Endpoint

AP-HongKong

ap-southeast-2

obs.ap-southeast-1.myhuaweicloud.com

AP-Bangkok ap-southeast-1

obs.ap-southeast-2.myhuaweicloud.com

AF-Johannesburg

af-south-1 obs.af-south-1.myhuaweicloud.com

SAPBest Practices







https://developer.huaweicloud.com/intl/en-us/endpoint

NO TE

– After running the preceding commands, a configuration file .obsutilconfig isautomatically generated in the same directory of the user who executes obsutilcommands (the ~ directory in Linux). .obsutilconfig contains all the configurationinformation of obsutil. For details about the parameters, see ParameterDescription.

– The .obsutilconfig file contains user AK and SK information. To prevent keyleakage, the obsutil file is hidden by default. You can run the ls -a command in thedirectory of the user who executes obsutil commands to view the file.

Step 2 After the configuration is complete, you can run the following command to checkthe connectivity:

./obsutil ls -s

Check the command output.

● If the command output contains Bucket number is:, the configuration iscorrect.

● If the command output contains Http status [403], the access keys areincorrectly configured.

● If the command output contains A connection attempt failed, the OBSservice cannot be connected. Check whether the network is normal.

----End

2.3 Uploading Backups to the OBS Bucket

2.3.1 Manually Running the Script

Prerequisites

Before running the script, ensure that the database backup is complete. This scriptcannot identify whether the backup file is complete.

Procedure

Step 1 After modifying the configuration file, run the following commands to start theupload:

cd /opt/huawei/obsutil_adapter

python3 obsutil_adapter.py

NO TE

After the script is executed, log in to OBS to view the uploaded file. The directory name onOBS is determined by time, and the structure is Bucket path/Year and month/Day/, forexample, obs-sap/hana/201808/22/.

----End

SAPBest Practices





2.3.2 Calling by Other ScriptsIf other scripts need to call this script, ensure that its software package has beendownloaded and decompressed. Before running the script, ensure that thedatabase backup is complete. This script cannot identify whether the backup file iscomplete.

Procedure

Step 1 Run the following command to call the script:

cd /opt/huawei/obsutil_adapter && python3 obsutil_adapter.py

NO TE

In the preceding command, /opt/huawei/obsutil_adapter indicates the path where thescript is decompressed. Change it based on the site requirements.

----End

2.3.3 Configuring Scheduled TasksIf a backup task needs to be executed periodically, configure scheduled tasks usingcrontab on Linux to call the script. Before running the script, ensure that thedatabase backup is complete. This script cannot identify whether the backup file iscomplete.

Procedure

Step 1 Edit the crontab file:

crontab -e

Set the scheduled task. Change the time according to the actual situation, savethe modification, and exit.

If the following information is displayed, the script will be called at 21:30 o'clockevery day:

30 21 * * * cd /opt/huawei/obsutil_adapter && python3 obsutil_adapter.py >/dev/null 2>&1

NO TE

The scheduled task execution time is defined by the customer. Ensure that the scheduledtask execution time is later than the backup time.

Step 2 View scheduled tasks. If you can find the scheduled tasks in Step 1 by running thefollowing command, it indicates that the setting is successful.

crontab -l

----End

2.4 FAQs

SAPBest Practices



2.4.1 How Do I Download a Backup File of a Day from theOBS Bucket?

This topic describes how to use obsutil to download a backup file of a day fromthe OBS bucket to the local host.

NO TICE

● Ensure that source objects in the OBS bucket do not change. Otherwise, thedownload may fail or data may be inconsistent.

● If the objects to be downloaded are in the OBS Archive storage class, you mustrestore the objects first. Otherwise, the download fails.

Procedure


Step 2 Run the following command to recursively download all files and folders(including the folder itself) in the bucket to a local path:

./obsutil cp obs://obs_path/Year/Month/Day/Local path -r -tempFileDir= aspecified path -f

In the preceding command:

● obs_path: OBS bucket path, for example: obs-sap/hana● Year/Month/Day: directory of a folder in the OBS bucket. For example:

201905/28.● Local path: path where the files are stored on the local host. For example:

src1.● tempFileDir= a specified path: Directory for storing temporary files during

multipart download. The default value is the value of defaultTempFileDir inthe configuration file. You can also specify a path.

NO TE

– Temporary files generated during multipart download are stored in this directory.Ensure that the user who runs obsutil commands has the write permission on thepath.

– The available space of the path must be greater than the size of the objects to bedownloaded.

For example, in the obs-sap bucket, download the backup files of May 28, 2019 tothe local path src1. The command is as follows:

./obsutil cp obs://obs-sap/hana/201905/28 /src1 -r -tempFileDir=/hana/backup-f

For more information about obsutil, see Introduction to obsutil.

----End

SAPBest Practices




2.4.2 How Can I Periodically Delete Backup Files from aBucket or Change the Storage Class of Backup Files?

This section applies to the following scenarios:

● Some files uploaded periodically need only to be retained for only one weekor one month. You need to delete the files after they expire.

● Files are seldom accessed after a certain period of time. These files need to betransitioned to Infrequent Access or Archive storage or be deleted.

You can create lifecycle rules for objects in the preceding scenarios.

NO TICE

● Use an independent bucket to store backup files to prevent important filesfrom being deleted by mistake during the periodical deletion.

● Apply the lifecycle rules to the entire bucket when configuring the lifecyclemanagement function to manage the lifecycle of all objects in the bucket.

Procedure

Step 1 For details, see Lifecycle Management Overview and Configuring a LifecycleRule.

----End

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-obs/en-us_topic_0045853659.html

https://support.huaweicloud.com/intl/en-us/usermanual-obs/obs_03_0335.html

https://support.huaweicloud.com/intl/en-us/usermanual-obs/obs_03_0335.html

3 Best Practices of SAP with EnterpriseProject Management

3.1 OverviewEnterprise Management helps enterprise users manage their cloud resources atthe project level or according to organization hierarchy. Enterprise Managementincludes Enterprise Project Management, Accounting Management, and PersonnelManagement. Enterprise Project Management centrally manages enterpriseprojects and resources in enterprise projects. This document describes how to usethe enterprise management function to create enterprise projects, provisionapplications using templates, and perform O&M and management.

Before using the enterprise project management function, you need to apply forthe Enterprise Management permission. For details about enterprise projectmanagement, see the Enterprise Project Management User Guide.

Figure 3-1 shows the operation process.

SAPBest Practices

3 Best Practices of SAP with Enterprise ProjectManagement


https://support.huaweicloud.com/intl/en-us/usermanual-em/en-us_topic_0131965280.html

Figure 3-1 Flowchart

3.2 Preparing Resources

3.2.1 Obtaining SoftwareTable 3-1 lists the required software.

SAPBest Practices



Table 3-1 Software installation package

Software Description How to Obtain

SAP HANA 1.0 orSAP HANA 2.0

SAP HANA installationpackage. Download therequired SAP HANAsoftware package based onthe version mappingrelationship between SAPHANA software versionand SUSE OS version onthe SAP official website.

https://support.sap.com/swdc

SAP S/4HANA SAP S/4HANA softwareinstallation packageDownload the required SAPS/4HANA softwarepackage based on versionmapping relationshipbetween SAP S/4HANAsoftware version and SUSEOS version on the SAPofficial website.NOTE

The version of SAP S4/HANAmust match that of theKernel. Otherwise, theinstallation will fail. Fordetails, visit https://support.sap.com/swdc.

3.2.2 Configuring an AgencyThe Data Provider and Enterprise Project Management need to be granted withthe permission to obtain information from the public cloud platform. Therefore,create an agency on the public cloud platform to obtain the platform information.

● Assign the agency to the ECS. Then, the Data Provider installed on the ECScan obtain the platform information through the agency.

● Assign the agency to OBS to ensure that software packages can be uploadedto OBS.

ProcedurePerform the following operations to create an agency.

Step 1 Log in to the management console.

Step 2 On the management console, click Service List and choose Management &Deployment > Identity and Access Management.

Step 3 Click Agencies in the left pane, and then click Create Agency in the upper rightcorner. The Create Agency page is displayed.

SAPBest Practices







Step 4 Set agency parameters.● Agency Name: DataProviderAccess. This name is only for reference.● Agency Type: Cloud service● Cloud Service: Elastic Cloud Server (ECS) and Bare Metal Server (BMS)● Validity Period: Retain the default setting.● Permissions: Perform the following operations.

a. Click Assign Permissions next to Permissions.b. In the displayed dialog box, enter Tenant Guest, OBS Buckets Viewer,

and ECS FullAccess respectively.c. Select Tenant Guest and OBS Buckets Viewer from the displayed results

and then All policies/roles in the drop-down list.d. Select ECS FullAccess and select the target region in the Project

[Region] column, for example, cn-east-4 [CN North-Beijing4].

Figure 3-2 Assigning permissions

e. Click OK.

Step 5 Click OK.

----End

Follow-up Operation

On the application provisioning page, set IAM Agency to DataProviderAccess sothat the agency can be used.

3.2.3 Uploading Software PackagesBefore provisioning an application, you need to download the OBS client andupload the required software installation packages to the OBS client.

Prerequisites

You have obtained the required software packages. For details about how toobtain the software packages, see Table 3-1.

Procedure

Step 1 Register an account and use OBS.

Step 2 Download and install the client by referring to Download OBS Client.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/qs-obs/obs_qs_0000.html

https://storage-intl.huaweicloud.com/obs/?agencyId=050bc3770f800f561fd4c01e5f898593®ion=ap-southeast-2&locale=en-us#/obs/manager/buckets

Step 3 Upload the required installation packages. For details, see OBS Tools.

NO TICE

The directory where the SAP S/4HANA bucket path resides must contain thefollowing folders, whose names are case sensitive:● BSK_ CD: contains SAP kernel patch.● CLNT_CD: contains the package corresponding to DB CLIENT.● EXP_CD: contains the package corresponding to EXP and must contain the file

whose name ends with part1.exe.● SWPM_CD: must contain the .exe file corresponding to SAPCAR and the .sar file

corresponding to SWPM. The file suffix must be .exe and .sar.

Upload the required software installation packages to the OBS directory asrequired.

WARNING

The folder names are case sensitive. Name the folders according to aboveexamples. Otherwise, the software installation packages may fail to be obtained.

● The example directories for provisioning SAP HANA in the OBS bucket are asfollows:obs-sap├readme.txt └hana └software └51053061 ├51053061_part1.exe ├51053061_part2.rar ├51053061_part3.rar └51053061_part4.rar

● The example directories for provisioning SAP S/4HANA in the OBS bucket areas follows:obs-sap├readme.txt └s4hana └s4hana1709 ├SWPM_CD │ ├SWPM10SP22_8-20009701.SAR │ └SAPCAR_721-20010450.EXE │ ├EXP_CD │ ├51052190_part5.rar │ ├51052190_part4.rar │ ├51052190_part3.rar │ ├51052190_part2.rar │ └51052190_part1.exe ├CLNT_CD │ └51052377.ZIP └BSK_CD ├igsexe_1-80003187.sar ├igshelper_4-10010245.sar ├SAPEXE_16-80002573.SAR ├SAPHOSTAGENT32_32-20009394.SAR └SAPEXEDB_16-80002572.SAR

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/tg-obs/obs_09_0001.html

● The example directories for provisioning SAP S/4HANA and SAP HANA in theOBS bucket are as follows:obs-sap├readme.txt └s4hana └s4hana1709 ├SWPM_CD │ ├SWPM10SP22_8-20009701.SAR │ └SAPCAR_721-20010450.EXE │ ├EXP_CD │ ├51052190_part5.rar │ ├51052190_part4.rar │ ├51052190_part3.rar │ ├51052190_part2.rar │ └51052190_part1.exe ├CLNT_CD │ └51052377.ZIP ├BSK_CD │ ├igsexe_1-80003187.sar │ ├igshelper_4-10010245.sar │ ├SAPEXE_16-80002573.SAR │ ├SAPHOSTAGENT32_32-20009394.SAR │ └SAPEXEDB_16-80002572.SAR └HANA ├51053061_part1.exe ├51053061_part2.rar ├51053061_part3.rar └51053061_part4.rar

● The example directories for provisioning SAP Business One in the OBS bucketare as follows:

WARNING

The name of the OBS directory folder is case sensitive. The directory mustcontain the following folders:– HANA– B1HANACreate the directory by referring to the following example. Otherwise, thesoftware installation package cannot be obtained.

obs-sap└sapb1-9.3 ├readme.txt ├HANA │ ├51050929_part1.exe │ └51050929_part2.rar └B1HANA ├51053060_part1.exe ├51053060_part2.rar └51053060_part3.rar

----End

3.3 Creating an Enterprise ProjectBefore provisioning applications to customers, you need to create enterpriseprojects for users to manage resources under the enterprise projects.

SAPBest Practices



Procedure

Step 1 On the HUAWEI CLOUD console, click Enterprise in the upper part of the pageand then Project Management.

Step 2 In the upper right corner, click Create Enterprise Project.

The Create Enterprise Project dialog box is displayed.

Figure 3-3 Create Enterprise Project

Step 3 Enter a project name and description. For details, see Table 3-2.

SAPBest Practices



Table 3-2 Configuration information

Parameter Description Example Value

Name Specifies the enterprise projectname.The name contains a maximum of64 characters. It can contain onlyletters, digits, underscores (_), andhyphens (-). The name cannot bethe word default in any forms ofuppercase, lowercase, orcombination of uppercase orlowercase, such as DeFault.

SAP

Description Add description information aboutan enterprise project.The description can contain amaximum of 512 characters.

-

Step 4 Click OK.

----End

3.4 Managing Templates

3.4.1 Example TemplatesAn example template is a default template for service resource provisioning andsoftware deployment. You can directly select an example template to createapplications or modify it as your own template.

Viewing an Example Template


Step 2 In the navigation pane, choose Application Management > TemplateManagement.

SAPBest Practices



The Example Templates tab page and the example template list are displayed bydefault.

Step 3 Click the name of the target example template. The example template detailspage is displayed.

You can view the details and content of the example template on this page. Youcan also click Create Application in the upper right corner to create anapplication, or click Download Template to save the template as your owntemplate.

For details about how to create an application, see Creating an Application.

----End

Creating an Application




Step 3 Click Create Application in the Operation column on the right of the exampletemplate list.

Create an application based on your requirements. For details, see Creating anApplication.

----End

Modifying as My Template


SAPBest Practices




Step 3 The Example Templates tab page and the example template list are displayed bydefault.

Step 4 Click Modify as My Template in the Operation column on the right of theexample template list.

Step 5 The Modify as My Template page is displayed. Set the parameters based onTable 3-3.

Table 3-3 Template parameter configuration

Parameter Description

Region Select a region to create the template.A maximum of 100 templates can be created in eachregion.

Template Name You can set a template name as required. The templatename cannot be empty and can contain only digits, letters,hyphens (-), and underscores (_), and must start with aletter.

Template Type ● SAP● Common

TemplateDescription

Optional. The description can contain a maximum of 256characters.

Template Content You can configure the template parameters based on yourrequirements in the gray area in the lower part of thepage.

Step 6 Click Create Now.

Step 7 After the template is created, you can view it in the template list on the MyTemplates tab page.

----End

SAPBest Practices



3.4.2 My TemplatesMy template is a custom resource template. You can view, create, copy, update,delete, and create applications on the My Templates tab page.

Viewing a Template




Step 3 Click the My Templates tab page.

Step 4 Select the region to be viewed.

The template list in the selected region is displayed in the lower part of the page.

Step 5 Search for a template.

Enter the template name in the upper right corner of the list to search for thetemplate to be viewed.

Step 6 Click the template name. The template details page is displayed.

You can view the template details and template content on the details page. Youcan also click Create Application in the upper right corner to create anapplication. For details about how to create an application, see Creating anApplication.

----End

Creating a Template


SAPBest Practices






Step 4 Click Create Template above the template list.

The Create Template page is displayed. Set the parameters based on Table 3-4.

Table 3-4 Template parameter configuration


Region Select a region to create the template. Amaximum of 100 templates can be created ineach region.

Template Name You can set a template name as required. Theapplication name cannot be empty and cancontain only digits, letters, hyphens (-), andunderscores (_), and must start with a letter.

Template Description Optional. The description can contain a maximumof 256 characters.

SourceType

Createdirectly

Template Type

Select SAP.Next, you can select Enter template code,Example Templates, or My Templates.

SelectTemplate

When Source Type is set to Example Templatesor My Templates, you need to select a template.

TemplateContent

You can view and edit the template content in thetext box.

SAPBest Practices




Createfrombackup

Template Data

1. Filter application backups based on thefollowing items:– Enterprise Project– Application– Application backup

2. Configure ECSs. For details, see section"Purchasing and Logging In to a Windows ECS"or "Purchasing and Logging In to a Linux ECS"in the Elastic Cloud Server User Guide.

3. If the selected application is attached to twoECSs, the ECSs can share configurations. Toshare configurations, select Sharedconfiguration for the applicable parameters onthe ECS Configuration tab page. Theseparameters of the two ECSs then will have thesame values in the created template.

(Optional) Set customized parameters.The configuration parameters include ParameterGroup, Parameter Name, Type, and Content.Select Text or Numeral for Type as required.A maximum of 10 parameter groups and 100parameters can be created. The parameter groupname and parameter name must be unique.

For customized parameters, you can add parameters to identify applications. Thefollowing is an example:

Parameter Groups: BasisInfo

Parameter Name: Database

Type: Text

Content: SAP HANA 2.0


After the template is created, you can view it in the template list on the MyTemplates tab page.

----End

Creating an Application


SAPBest Practices






Step 4 Click Create Application in the Operation column on the right of the templatelist.

Create an application based on your requirements. For details, see Creating anApplication.

----End

Copying a TemplateStep 1 On the HUAWEI CLOUD console, click Enterprise in the upper part of the page

and then Project Management.




Step 4 Locate the template to be copied, and click Replicate in the Operation column onthe right of the template.

The Replicate Template dialog box is displayed.

SAPBest Practices



Step 5 Enter the name and description.

NO TE

● The name must be unique and cannot be empty. It can contain only digits, letters,hyphens (-), and underscores (_), and must start with a letter.

● The description is optional. The description can contain a maximum of 256 characters.

----End

3.5 Creating an Application

3.5.1 Provisioning an SAP HANA DatabaseThis section uses an example template to describe how to quickly provision an SAPHANA database.

NO TE

The log directory for provisioning SAP HANA is /var/log/huawei/auto-install/hana-intall.log.

PrerequisitesThe SAP HANA software installation packages have been uploaded to the OBSbucket. For details about how to upload packages, see Uploading SoftwarePackages.

Provisioning an SAP HANA Database


Step 2 In the navigation pane, choose Application Management > Applications.

The application list is displayed in the lower part of the page.

Step 3 Click Create Application above the application list.

The Create Application page is displayed.

Step 4 Configure basic application information. Set the parameters based on Table 3-5.

SAPBest Practices





EnterpriseProject Name

Select an existing enterprise projectfrom the drop-down list box.

SAP

Region Select a region to create theapplication. A maximum of 100applications can be created in eachregion.

AP-Hong-Kong

ApplicationName

Specifies the name of theprovisioned application.

hana-1709

ApplicationDescription

Optional. The description cancontain a maximum of 256characters.

-

Source Type Select Example Templates or MyTemplates as required.

Example Templates

TemplateType

Set it to SAP or Common asrequired.

SAP

SelectTemplate

Select the template from the list. Ifthere are many templates, you canenter the template name in thesearch box to search for the targettemplate.

SAP-HANA-Single-Node

Step 5 Click Next.

Step 6 On the displayed page, configure parameters. For details, see Table 3-6.



Network Configuration

VPC Name Name of the VPC to which theHANA ECS belongs. If no VPC iscreated, click Create VPC.

vpc-sap-hana

Subnet Subnet used by the HANA ECS. Ifno subnet is created, click CreateSubnet.

subnet-fd25-sap-hana

Server and Storage Configuration

AZ Name of the AZ where the HANAECS is located

AZ1

ECSSpecification

Specifications of a HANA ECS. Setthis parameter as required.

e3.7xlarge.12 | 28vCPUs |348GB

SAPBest Practices




Image Image of a HANA ECS. Select Public image andthen SUSE Enterprise 12SP3 64bit for SAP.

SecurityGroup

Security group to which the HANAECS belongs. If no security groupis created, click Create SecurityGroup.

c28cef02-d150-4a62-8d98-ff5b2a663289

Key Pair Key pair for logging in to theHANA ECS. If no key pair iscreated, click Create Key Pair.

KeyPair-sap-hana

IAM Agency IAM agency name. After the IAMagency is configured, the ECS hasthe permission to access OBS andCloud Eye. For details about theagency name, see Configuring anAgency.

DataProviderAccess

System DiskType

Type of the system disk Ultra-high I/O

System Disk(GB)

System disk size 50

Usrsap DiskType

Type of the usrsap disk Ultra-high I/O

Usrsap Disk(GB)

Usrsap disk size 50

Swap DiskType

Type of the swap disk Ultra-high I/O

Swap Disk(GB)

Swap disk size 10

Shared DiskType

Type of the shared disk Ultra-high I/O

Shared Disk(GB)

Shared disk size 418

Log Disk Type Type of the log disk Ultra-high I/O

Log Disk (GB) Log disk size 200

Data DiskType

Type of the data disk Ultra-high I/O

SAPBest Practices




Single DataDisk (GB)

Size of an EVS disk● If the LVM is not configured,

the value is the size of a singleEVS disk.

● If the LVM is configured, thevalue is the size of the EVSdisks that from the logicalvolume.

250

Data DiskQuantity

Number of data disks.● If the LVM is not configured,

the data disk is an EVS disk.Choose 1 from the drop-downlist box.

● If the LVM is configured, thedata disk uses an LVM logicalvolume formed by multiple EVSdisks. Choose the number ofthe EVS disks from the drop-down list.

1

Backup SFSAZ

Name of the AZ where the SFSECS is located

AZ1

Backup SFSSize (GB)

SFS size. SFS is used for HANAdatabase backup.

1044

SAP HANA Database Configuration

HANAHostname

HANA hostname. The name mustbe 1 to 13 characters long andmust contain only letters, digits,periods (.), hyphens (-), andunderscores (_).

hana-1709

HANA SystemID

HANA system ID. The ID iscomposed of one uppercase letterand two digits.

S00

HANAInstanceNumber

HANA instance number 00

HANAPassword

Password of the HANA database.Confirm the password. Thepassword must comply with theSAP password setting rules.

-

SAPBest Practices




OBS BackupDirectory

Directory of the HANA installationpackage on OBS. For details, seeUploading Software Packages.NOTE

The OBS bucket directory is in theformat of obs://Bucket name/Directory.

obs://obs-sap/hana/software/51053061

Extended Configuration

OS Version OS version SUSE 12

HANA Version HANA database version HANA 2.0

Install SAPSoftware

Decide whether to install SAPsoftware based on the siterequirements.

Yes

Step 7 Click Next.

On the Confirm Specifications page, confirm the basic information and templateparameters.

Step 8 Click Submit.

After the application is created, you can view it in the application managementlist.

----End

Follow-up Operations

Install Data Provider on all cloud servers so that SAP technical support personnelcan use this software to collect information of the platform where the cloudservers run, facilitating fault identification and analysis if the SAP system is faultyor the system performance deteriorates.

NO TE

On the server where SAP NetWeaver is deployed, you must specify the DataproviderAccessagency for the ECSs created on the server. In addition, install Data Provider on the server.

Procedure

Step 1 Log in to all cloud servers.

Step 2 Run the following command to check whether Data Provider has been installed:

systemctl status hwdataproviderp3

The command output is similar to the following. If the value of Active is active(running), Data Provider has been successfully installed. Otherwise, follow theoperations described in the Data Provider for SAP User Guide to install it.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/dpug-sap/sap_01_0001.html

----End

3.5.2 Provisioning an SAP S/4HANA Application SystemYou can use an example template to quickly provision SAP S/4HANA. For details,see the SAP S/4HANA Quick Deployment User Guide.

3.5.3 Provisioning SAP Business OneYou can use an example template to quickly provision SAP Business One. Fordetails, see the SAP Business One Quick Deployment Guide.

3.6 (Optional) Managing ApplicationsIf you want to use applications to manage resources that are not created inapplications, you can use the management function to manage them, includingapplication monitoring and backup and restoration.

Only ECSs in the running or stopped state can be managed currently. Applicationscreated using templates cannot be managed.

Procedure




Step 3 Click Manage Resource in the upper part of the application list.

The Application Management page is displayed.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/ugqd-s4hana/s4hana_01_0002.html

https://support.huaweicloud.com/intl/en-us/ugqd-sapb1/sapb1_01_0002.html

Step 4 Select an ECS as prompted. For details, see Table 3-7.

Table 3-7 Selecting an ECS


Enterprise Project Name Click the drop-downarrow and select theenterprise project towhich the resource to bemanaged belongs.

SAP

Region Click the drop-downarrow and select theregion to which theresource to be managedbelongs.

AP-Hong-Kong

Select ECS 1. Select the resource tobe managed in theECS list.

2. Click tosynchronize theresource to theSelected ECSs Listarea.

app_example

Step 5 Click Next.

1. Select an application.Click the drop-down arrow and select an application from the drop-down listbox. Click Create Application and fill in information such as the name tocreate an application.

2. (Optional) Configure parameters. For details, see Table 3-8.For customized parameters, you can add parameters to identify applications.The configuration parameters include Parameter Group, Parameter Name,Type, and Content. Select Text or Numeral for Type as required.

NO TE

– This parameter is optional.– A maximum of 10 parameter groups and 100 parameters can be created.– The parameter group name and parameter name must be unique.

SAPBest Practices



Table 3-8 Parameter configuration


Parameter Group Name of a parametergroup. You can click

to add or to deletea parameter group.

BasisInfo

Parameter Name Name of a customparameter. You canclick Add on the rightto add a parameter.

Database

Type Set Type to Text orNumeral as required.

Text

Content Parameter content SAP HANA 2.0

3. Click Next.

Step 6 Confirm the specifications of the resource to be managed and click Submit.

The application has been managed. You can view the application status in theapplication list.

----End

3.7 SAP Full Screen Monitoring

3.7.1 OverviewThe SAP full screen monitoring provides functions such as SAP system monitoring,alarm statistics, application overview, CPU usage, memory usage, disk I/O, andnetwork traffic overview. The SAP full screen monitoring helps you betterunderstand the application resource usage, alarms, and SAP system running statusin real time.

Table 3-9 lists the OSs and product versions supported by SAP full screenmonitoring.

Table 3-9 OSs and product versions

Type Version

OS ● SUSE Linux Enterprise Server (SLES) 12 SP3 for SAP● SUSE Linux Enterprise Server (SLES) 12 SP4 for SAP● SUSE Linux Enterprise Server (SLES) 12 SP5 for SAP● SUSE Linux Enterprise Server (SLES) 15 for SAP● SUSE Linux Enterprise Server (SLES) 15 SP1 for SAP● Windows Server 2012

SAPBest Practices



Type Version

SAP HANA SAP HANA 1.0 SP12 or later and SAP HANA 2.0

SAP S/4HANA SAP S/4HANA 1511, SAP S/4HANA 1610, SAP S/4HANA1709, SAP S/4HANA 1809, and SAP S/4HANA 1909

SAP BusinessOne

SAP Business One 9.0, SAP Business One 9.1, SAP BusinessOne 9.2, SAP Business One 9.3, and SAP Business One 10.0

SAP NetWeaver SAP NetWeaver 7.5

SAP ECC EHP7 FOR SAP ERP 6.0

NO TE

Currently, only SAP HANA databases (single-node deployment without HA required), SAP S/4HANA application systems (single-node deployment without HA required), and SAPBusiness One can be provisioned by the templates on Enterprise Project Management.If the SAP full screen monitoring is required in SAP HANA (single-node deployment with HArequired), SAP S/4HANA (single-node deployment with HA required), distributed SAP S/4HANA (single-node deployment with HA required), and distributed SAP S/4HANA (single-node deployment without HA required) scenarios, the following requirements must be met:● All ECSs are provisioned on the Enterprise Project Management console and are

manually deployed in HA or distributed mode.● ECSs are provisioned on the management console and managed by applications of

Enterprise Project Management.

3.7.2 Installing SAP Monitoring Plug-ins

3.7.2.1 SAP HANA (Single-Node Deployment Without HA Required)To view the SAP full screen monitoring, SAP monitoring plug-ins must be installed.In the SAP HANA (single-node deployment without HA required) scenario, SAPmonitoring plug-ins must be installed on the HANA nodes.

PrerequisitesThe Agent has been installed and basic monitoring data can be viewed on theCloud Eye console. If the Agent is not installed, install it by referring to theInstalling and Configuring the Agent.

ProcedureInstalling and Configuring the Plug-ins

Step 1 Run the following commands to obtain the installation script to install the plug-ins.

The download paths of the script vary depending on regions. The followingcommands show the download path in AP-Bangkok.

cd /tmp

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-ces/ces_01_0027.html

curl https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/install.sh | sh

Table 3-10 Method of obtaining the script

Item Description

How to Obtain

install.sh

Installationscript

AP-Bangkok: https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/install.shAF-Johannesburg: https://obs-sap-af-south-1.obs.af-south-1.myhuaweicloud.com/sapmon/install.sh

Step 2 Modify the configuration.

1. Run the following command to encrypt the password:/usr/local/telescope/plugins/sapmon/bin/ktool encrypt

2. Enter the password.3. Run the following command to modify the configuration file:

vim /usr/local/telescope/plugins/sapmon/config/sapmon.iniTable 3-11 lists the parameters. Set the parameters based on the actualsituation. Change the password to the encrypted password obtained in Step2-1.

Table 3-11 Configuration parameters

Type Parameter Description Example Value

DEFAULT log_level Log level INFO

log_file Log file name. The log filepath is /var/log/huawei/sapmon/.

sap_metrics.log

hostname OS hostname hana-1709

database.hana

enable Whether to obtain databasemetrics. The value can betrue or false.NOTE

In the SAP HANA (single-nodedeployment with HA required)scenario, the value of the activenode is true and the value ofthe standby node is false.

true

ha_mode Whether the database isdeployed in HA mode. If yes,set this parameter to true. Ifno, set it to false.

false

sid Database SID S00

SAPBest Practices



https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/install.sh


https://obs-sap-af-south-1.obs.af-south-1.myhuaweicloud.com/sapmon/install.sh



instance_number

Database instance number 00

tenant_database_name

Name of the tenantdatabase. This parameter isused in the multi-tenantscenario.– If the HANA database is

for single tenant, you donot need to set thisparameter.

– If the HANA database isfor multiple tenants,enter the name of thetenant database.

-

username SAP HANA usernameNOTE

You need to use the followingSQL statements to grantrequired permissions to thisuser:CREATE USER <username>PASSWORD <password> NOFORCE_FIRST_PASSWORD_CHANGE;GRANT CATALOG READ to<username>;GRANT SELECT on SCHEMA_SYS_STATISTICS to<username>

-

password SAP HANA user password -

NO TE

If you need to monitor multiple tenant databases, copy and paste parameters underdatabase.hana, and change database.hana to database.hana.tenantdb_name.Replace tenantdb_name with the tenant database name, and change values ofusername, password, and other required parameters.

4. Run the following command to restart the Cloud Eye Agent:/usr/local/telescope/telescoped restart

----End

(Optional) Uninstalling the Plug-ins

Step 1 Run the following command to uninstall the plug-ins:

rpm -e sapmon

----End

SAPBest Practices



3.7.2.2 SAP HANA (Single-Node Deployment With HA Required)

In the SAP HANA (single-node deployment with HA required) scenario, you needto deploy the SAP monitoring plug-ins on both the active and standby nodes.

Prerequisites

The Agent has been installed on the active and standby nodes and basicmonitoring data can be viewed on the Cloud Eye console. If the Agent is notinstalled, install it by referring to the Installing and Configuring the Agent.

Procedure

Step 1 Deploy the plug-ins on the active and standby nodes. For details, see SAP HANA(Single-Node Deployment Without HA Required).

NO TE

● Set hostname to the names of hosts of active and standby nodes. On the active node,set the value of enable of database.hana to true to enable the monitoring function.

● After the HA switchover, set the value of enable of database.hana on the originalactive node to false to stop the monitoring of the original active node. On the standbynode, set the value of enable of database.hana to true to enable the new active node.

● After the HA switchover, you need to change the original active node information to thenew active node information in the Overview Status area on the SAP Full ScreenMonitoring. For details, see operations for modifying the monitoring the panel inFollow-up Operation.

----End

3.7.2.3 SAP S/4HANA (Single-Node Deployment Without HA Required)

In the SAP S/4HANA (single-node deployment without HA required) scenario, theASCS and PAS instances are deployed on the same node. You need to deploy theSAP monitoring plug-ins on this node.

Prerequisites

The Agent has been installed and basic monitoring data can be viewed on theCloud Eye console. If the Agent is not installed, install it by referring to theInstalling and Configuring the Agent.

Procedure

Preparations

Step 1 Obtain SAP NW RFC SDK.

NO TE

To obtain SAP NW RFC SDK, log in at https://support.sap.com/en/my-support/software-downloads.html, access downloads of Support Packages & Patches, search for SAP NWRFC SDK 7.50, and download it.

Step 2 Log in to the ECS as user root.

SAPBest Practices





https://support.sap.com/en/my-support/software-downloads.html


Step 3 Upload the obtained SAP NW RFC SDK to the /usr/sap directory.

Step 4 Run the following commands to decompress the SAP software SAP NW RFC SDKto the /usr/sap directory:

unzip nwrfc750P_2-70002755.zip

mv nwrfcsdk /usr/sap/

----End

Installing the Monitoring Plug-ins

Step 1 Run the following commands to obtain the installation script to install the plug-ins.

The download paths of the script vary depending on regions. The followingcommands show the download path in AP-Bangkok:

cd /tmp

wget https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/install.sh&& sh install.sh --nwrfcsdk-path /usr/sap/nwrfcsdk

/usr/sap/nwrfcsdk is the decompression path in Step 4.

Table 3-12 Method of obtaining the script

Item Description

How to Obtain

install.sh

Installationscript

AP-Bangkok: https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/install.shAF-Johannesburg: https://obs-sap-af-south-1.obs.af-south-1.myhuaweicloud.com/sapmon/install.sh


1. Run the following command to encrypt the password:/usr/local/telescope/plugins/sapmon/bin/ktool encrypt

2. Enter the password.3. Run the following command to enter the edit mode of the configuration file.

Modify the file according to Table 3-13, save the file, and exit.vim /usr/local/telescope/plugins/sapmon/config/sapmon.iniModify the parameters based on the actual situation. Change the password tothe return code obtained in Step 2-1.




SAPBest Practices









sap_metrics.log

hostname OS hostname s4hana-1709

application.netweaver

enable Whether to obtain theapplication metrics. Thevalue can be true or false.NOTE

In the SAP S/4HANA (single-node deployment with HArequired) scenario, the valueof the active node is true andthe value of the standby nodeis false.

true

sid Application SID S4H

instance_number

PAS instance ID 10

client SAP system ID 000

username Application username ddic

password Application password. Enterthe encrypted password.

-

4. Run the following command to restart the Cloud Eye Agent:

/usr/local/telescope/telescoped restart

----End



rpm -e sapmon

Step 2 Run the following command to uninstall the third-party Perl software that the SAPmonitoring plug-ins depend on:

rpm -e sapmon-thirdparty

NO TE

● The SAP monitoring plug-ins of 1.0.x depend on the third-party Perl software that needsto be uninstalled before uninstalling the monitoring plug-ins.

● SPA monitoring plug-ins of versions later than 1.2.0 do not have dependencies.

----End

SAPBest Practices



3.7.2.4 SAP S/4HANA (Single-Node Deployment With HA Required)In the SAP S/4HANA (with HA required) scenario, the ASCS instance is deployedon the active node and the ERS instance is deployed on the standby node. Youneed to deploy the SAP monitoring plug-ins on both the active and standby nodes.

PrerequisitesThe Agent has been installed on the active and standby nodes and basicmonitoring data can be viewed on the Cloud Eye console. If the Agent is notinstalled, install it by referring to the Installing and Configuring the Agent.

Procedure

Step 1 Deploy the plug-ins on the active and standby nodes. For details, see SAP S/4HANA (Single-Node Deployment Without HA Required).

NO TE

● Set hostname to the names of hosts of active and standby nodes. On the active andstandby nodes, set the value of instance_number to the PAS or AAS instance number.On the active node, set the value of application.netweaver to true to enable themonitoring function.

● The AAS and PAS instances must be installed on both the active and standby nodes, andtheir processes must be started.

● After the HA switchover, set the value of enable of application.netwearver on theoriginal active node to false to stop the monitoring of the original active node. On thestandby node, set the value of enable of application.netweaver to true to enable thenew active node.

● After the HA switchover, you need to change the original active node information to thenew active node information in the Overview Status area on the SAP Full ScreenMonitoring. For details, see operations for modifying the monitoring the panel inFollow-up Operation.

----End

3.7.2.5 SAP S/4HANA (Distributed Deployment with HA Required)In the SAP S/4HANA (distributed deployment with HA required) scenario, youneed to deploy the SAP monitoring plug-ins on node 1 and node 2 shown inFigure 3-4.

PrerequisitesThe Agent has been installed on the two nodes and basic monitoring data can beviewed on the Cloud Eye console. If the Agent is not installed, install it by referringto the Installing and Configuring the Agent.

Procedure

Step 1 Deploy the plug-ins on node 1 and node 2. For details, see SAP S/4HANA (Single-Node Deployment With HA Required).

Figure 3-4 shows the application deployment in the SAP S/4HANA (distributeddeployment with HA required) scenario.

SAPBest Practices





Figure 3-4 Deployment scheme

----End

3.7.2.6 SAP S/4HANA (Distributed Deployment Without HA Required)

In the SAP S/4HANA (distributed deployment without HA required) scenario, youneed to deploy the SAP monitoring plug-ins on the ASCS node (node 1 shown inFigure 3-5).

Prerequisites

The Agent has been installed on the two nodes and basic monitoring data can beviewed on the Cloud Eye console. If the Agent is not installed, install it by referringto the Installing and Configuring the Agent.

Procedure

Step 1 Deploy the plug-ins on the ASCS node (node 1 in the figure). For details, see SAPS/4HANA (Single-Node Deployment Without HA Required).

Figure 3-5 shows the application deployment scheme in the SAP S/4HANA(distributed deployment without HA required) scenario.

Figure 3-5 Deployment scheme

----End

SAPBest Practices




3.7.2.7 SAP Business OneDeploy monitoring plug-ins for SAP Business One and the HANA database.

PrerequisitesThe Agent has been installed and basic monitoring data can be viewed on theCloud Eye console. If the Agent is not installed, install it by referring to theInstalling and Configuring the Agent.

ProcedureInstalling and Configuring the Plug-ins

Step 1 Install the monitoring plug-ins. For details, see Step 1.


1. Run the following command to modify the configuration file:vim /usr/local/telescope/plugins/sapmon/config/sapmon.iniTable 3-14 lists the parameters. Set the parameters based on the siterequirements.





sap_metrics.log

hostname OS hostname b1

application.b1hana

enable Whether to obtain SAPBusiness One metrics. Thevalue can be true or false.

true

sid The SAP Business One doesnot provide a system ID. Thissystem ID is provided to youfor identifying the system.

B00

The following is a configuration example:[application.b1hana]enable = ture# System ID of the SAP B1 HANAsid = B00

2. Run the following command to restart the Cloud Eye Agent:/usr/local/telescope/telescoped restart

----End

SAPBest Practices






rpm -e sapmon

----End

3.7.2.8 SAP ECC

To monitor SAP ERP 6.0 metrics, you need to deploy and configure monitoringplug-ins following the operations descried in Scenario 1: SAP ECC (Linux) orScenario 2: SAP ECC (Windows).

Scenario 1: SAP ECC (Linux)

For details about how to deploy the monitoring plug-ins for SAP ECC (Linux), seeSAP S/4HANA (Single-Node Deployment Without HA Required).

Scenario 2: SAP ECC (Windows)

In the SAP ECC (Windows) scenario where SAP ERP 6.0 metrics need to bemonitored, you need to install and configure the monitoring plug-ins.

Prerequisites

The Agent has been installed and basic monitoring data can be viewed on theCloud Eye console. If the Agent is not installed, install it by referring to theInstalling and Configuring the Agent.

Procedure

Preparations

Step 1 Obtain the SAP NW RFC SDK and decompress it to C:\nwrfcsdk.

NO TE

To obtain SAP NW RFC SDK, log in at https://support.sap.com/en/my-support/software-downloads.html, access downloads of Support Packages & Patches, search for SAP NWRFC SDK 7.50, and download it.

----End

Installing and Configuring the Plug-ins

Step 1 Use a browser to download the monitoring plug-in installation packages.

Access the URL for your region. The following command uses the URL for HongKong (China) as an example:

https://obs-sap-ap-southeast-1.obs.ap-southeast-1.myhuaweicloud.com/sapmon/sapmon_setup_1.2.2.0_x64.exe

SAPBest Practices






Table 3-15 Required software package

Name Description

How to Obtain

sapmon_setup_x64.exe

Softwareinstallation package

AP-Hong Kong: https: https://obs-sap-ap-southeast-1.obs.ap-southeast-1.myhuaweicloud.com/sapmon/sapmon_setup_1.2.2.0_x64.exe

AP-Bangkok: https://obs-sap-ap-southeast-2.obs.ap-southeast-2.myhuaweicloud.com/sapmon/sapmon_setup_1.2.2.0_x64.exe

SA-Johannesburg: https://obs-sap-af-south-1.obs.af-south-1.myhuaweicloud.com/sapmon/sapmon_setup_1.2.2.0_x64.exe

Step 2 Install SAP monitoring plug-ins.

1. Click sapmon_setup_x64.exe. The installation window is displayed.2. Click Next. On the displayed Choose Folder page, select Set the folder path

and the decompressed folder.3. Click Next. Select an installation directory. The default installation directory is

C:\Program Files\Huawei\sapmon.4. Click Install. After the installation is complete, click Close.

Step 3 Modify the configurations.

After the installation is complete, go to the installation directory and modify theconfigurations. The default installation directory is C:\Program Files\Huawei\sapmon.

1. Run ktool.bat as the administrator to encrypt the password used for loggingin to the application system.

2. Enter the password as required. The encrypted password is automaticallysaved to clipboard.

3. Open the configuration file config/sapmon.ini in the installation directoryand modify the configurations.Table 3-16 lists the parameters. Set the parameters based on the siterequirements. Change the password to the one obtained in Step 3.1.


Type Parameter

Description Example Value


log_file Log file name. The log filepath is C:\ProgramData\Huawei\sapmon\.

sap_metrics.log

hostname OS hostname erp01

SAPBest Practices



Type Parameter

Description Example Value

application.netweaver

enable Whether to obtain theapplication metrics. Thevalue can be true or false.NOTE

In the SAP ERP 6.0 (single-node deployment with HArequired) scenario, the valuefor the active node is trueand the value for the standbynode is false.

true

sid Application SID ERP

instance_number

PAS instance ID 01

client SAP system ID 000

username Application username ddic

password Application password.Enter the encryptedpassword.

N/A

4. Restart the CES Agent service.

a. On the Windows desktop, choose Start > Run. Enter services.msc in thedisplayed dialog box.

b. In the displayed dialog box, locate huawei-telescoped, right-click it, andclick Restart.

----End


Step 1 Go to the installation directory of the monitoring plug-ins. The default installationdirectory is C:\Program Files\Huawei\sapmon.

Step 2 Double-click uninst.exe and uninstall the monitoring plug-ins as prompted.

----End

3.7.3 (Optional) Upgrading Monitoring Plug-insAfter the monitoring metric update or plug-in optimization, you need to upgradethe monitoring plug-ins for better monitoring of SAP metrics.

Upgrading the Monitoring Plug-ins (Linux)

Step 1 Log in to the node where the SAP monitoring plug-ins are installed.

Step 2 Run the following command to upgrade the plug-ins:

/usr/local/telescope/plugins/sapmon/upgrade.sh

SAPBest Practices



NO TE

To upgrade monitoring plug-ins of 1.0.x to 1.2.x or later, you need to upgrade SAP NW RFCSDK to 7.5.0 and run the following command to specify the directory for storingdecompressed SAP NW RFC SDK:

/usr/local/telescope/plugins/sapmon/upgrade.sh --nwrfcsdk-path /usr/sap/nwrfcsdk/

If information similar to that shown in Figure 3-6 is displayed, the upgrade issuccessful.

Figure 3-6 Successful upgrade

----End

Upgrading the Monitoring Plug-ins (Windows)

Step 1 Go to the installation directory. The default installation directory is C:\ProgramFiles\Huawei\sapmon.

Step 2 Double-click upgrade.bat.

----End

3.7.4 Adding a Monitoring PanelYou can add the SAP monitoring metrics to the SAP Full Screen Monitoring.

SAPBest Practices



Procedure




Step 3 Click SAP Full Screen Monitoring above the application list.

The Monitoring Management page is displayed.

Step 4 Click in the SAP Full Screen Monitoring area.

Step 5 Add monitoring metrics as prompted.● In the Add Application Monitoring box, select Application and Database,

and enter Application SID and Database SID.

NO TE

– A maximum of 18 application monitoring data records can be added currently.– The Application SID cannot be left blank. The value must be a string of 3

characters consisting of uppercase letters and digits, and must start with a letter.

● In the Add Monitoring Graph box, select Monitoring Graph.

Step 6 Click OK.

----End

Follow-up OperationYou can also modify and delete the monitoring panel.

Modifying a Monitoring Panel


SAPBest Practices




Step 3 The application list is displayed in the lower part of the page.


Step 5 The Monitoring Management page is displayed.

Step 6 In the Overview Status panel of the SAP Full Screen Monitoring area, click to modify the target application monitoring data.

Step 7 Modify monitoring metrics as required.● In the Modify Application Monitoring box, modify Application, Database,

Application SID, and Database SID.● In the Modify Monitoring Graph box, select Monitoring Graph.

Step 8 Click OK.

----End

Deleting a Monitoring Panel






SAPBest Practices



Step 4 In the SAP Full Screen Monitoring area, click in the upper right corner of themonitoring panel to be deleted.

Step 5 In the displayed dialog box, click OK.

----End

3.7.5 Viewing the SAP Full Screen Monitoring PageThe SAP full screen monitoring helps you better understand the applicationresource usage, alarms, and SAP system running status in real time.

The system will be disconnected automatically if no operation is performed within30 minutes as an administrator account. You are advised to use the dedicatedaccount for full screen monitoring. For details about how to add a dedicatedaccount, see How Can I Add a Dedicated Account for the SAP Full ScreenMonitoring?

Figure 3-7 SAP full screen monitoring

The SAP full screen monitoring mainly monitors application metrics and IaaS layermetrics. Application metrics include SAP HANA metrics and SAP applicationmetrics.

Table 3-17 describes the SAP monitoring metrics.

SAPBest Practices



Table 3-17 Metrics

Item Description Metric Metric Description

AlarmStatistics

Displays the number ofalarms of different severitylevels, including CriticalAlarms, Major Alarms,Minor Alarms, andInformational Alarms.Cloud Eye collects thealarm information. Afteryou install and configurethe plug-ins required bythe SAP full-screenmonitoring, the systemreports the collectedmonitoring data on theCustom Monitoring pageof the Cloud Eye console.You only need to createalarm rules in Cloud Eyeto view alarm statistics onthe SAP Full ScreenMonitoring page.For details about custommonitoring and creatingalarm rules, see the CloudEye User Guide.NOTE

The Alarm Statisticsfunction takes effect only onthe applications that meetthe following conditions:● The application has been

added to the applicationmonitoring. For details,see Adding a MonitoringPanel.

● Alarm rules have beencreated for theapplication.

● CriticalAlarms

● MajorAlarms

● MinorAlarms

● InformationalAlarms

N/A

ABAPDumps

Displays the top threeapplications with thelargest number of dumptasks in the last hour. You

can click to view theapplications with dumptasks in the last hour.

N/A N/A

Background Jobs

Displays the top threeapplication SIDs with thelargest number of

finished_jobs Number of completedjobs

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-ces/en-us_topic_0094279601.html



background jobs in the

last hour. You can click to view the applicationSIDs with background jobsin the last hour.

canceled_jobs

Number of deleted jobs

LockEntriesUsage

Displays the top threeapplications with thelargest number of lockentries usage. You can

click to view the lockentries usage of allapplications.

lock_entries_usage

Lock entries usage

Overview Status

Displays customapplication monitoringdata. You can add, modify,and delete applicationsbased on the siterequirements. indicates the normal

running status. indicates the abnormal

running status.

Logged InUsers

Number of users thathave logged in to theSAP application

Version Version information

Hosts Active Status of SAPapplication ECSs. Forexample, 1/2 HostsActive indicates thatthere are two ECSs intotal and one ECS isrunning.

Instances Number of availableinstances in the totalnumber of SAPapplication instances.For example, 3/4Instance indicates thatthree of the fourinstances are available.

HA Active HA status of SAPapplications

Hosts Active Status of databaseECSs. For example, 1/2Hosts Active indicatesthat there are two ECSsin total and one ECS isrunning.

SAPBest Practices




Services Number of availableservices in thedatabase. For example,9/10 Services indicatesthat nine of the tenservices are available.

HA Active Database HA status

SR Active Database systemreplication status

CPUUsage

Displays the top threeresource hosts with thelargest CPU usage in thelast three minutes. You can

click to view the CPUusage of all resource hostsin the last three minutes.

CPU usage Host CPU usage

MemoryUsage

Displays the top threeresource hosts with thelargest memory usage andtheir available memory inthe last 3 minutes. You can

click to view thememory usage and theiravailable memory of allresource hosts.

AGT.memoryusage

Memory usage

AGT.availablememory

Available memory

Disk I/O Displays the top threeresource hosts with thelargest read and write rate(KB/s) in the latest three

minutes. You can click to view the read and writerate (KB/s) of all resourcehosts.

AGT. diskread rate

Disk I/O (read)

AGT. diskwrite rate

Disk I/O (Write)

Network Displays the top threeresource hosts with thelargest inbound andoutbound (Kbit/s) in thelatest three minutes. You

can click to view theinbound and outbound(Kbit/s) of all resourcehosts.

AGT.inboundbandwidth

Inbound traffic

AGT.outboundbandwidth

Outbound traffic

SAPBest Practices




FileSystemUsage

Displays the top threeresource hosts with thelargest used file systemusage (%) and theirremaining space (GB) inthe last three minutes. You

can click to view thefile system usage (%) andremaining space (GB) ofall resource hosts.

AGT. diskusage

File system usage

AGT.availabledisk space

Remaining file systemcapacity

For more SAP monitoring metrics, see What Are the Metrics Displayed on theSAP Full Screen Monitoring?

Prerequisites● The plug-ins have been installed. Otherwise, install them by referring to

Installing SAP Monitoring Plug-ins.● The monitoring panel has been added. Otherwise, add it by referring to

Adding a Monitoring Panel.

Procedure






Step 4 In the upper right corner of the page, click Full Screen Monitoring.

The SAP Full Screen Monitoring page is displayed.

----End

SAPBest Practices



3.7.6 Viewing the Server Monitoring PageAfter provisioning an application, you can view OS monitoring metrics, basicmonitoring metrics, and process monitoring metrics.

PrerequisitesThe plug-ins have been installed. Otherwise, install them by referring to InstallingSAP Monitoring Plug-ins.

Procedure




Step 3 Click an application name to go to the application details page.

Step 4 On the Resources tab page, click Server Monitoring in the Operation column.

----End

3.7.7 Viewing the MonitoringAfter provisioning an application, you can create a monitoring panel to monitorand view the metrics of the resources you care about.

NO TICE

● Currently, each panel supports a maximum of 24 graphs.● You can add a maximum of 20 metrics to one graph. Monitoring comparison

between different services, dimensions, and metrics is supported.

PrerequisitesThe plug-ins have been installed. Otherwise, install them by referring to InstallingSAP Monitoring Plug-ins.

SAPBest Practices



ProcedureStep 1 On the HUAWEI CLOUD console, click Enterprise in the upper part of the page

and then Project Management.



Step 3 Click Create Monitoring Panel in the Operation column on the right of theapplication list.

The Create Monitoring Panel dialog box is displayed.

Step 4 Enter the name of the monitoring panel.

NO TE

The monitoring panel name cannot be empty. It can contain only digits, letters, hyphens (-),and underscores (_), and must start with a letter.

Step 5 Click OK.

After a monitoring panel is created, Create Monitoring Panel in the Operationcolumn switches to View Monitoring.

Step 6 Click View Monitoring.

The Monitoring Panels page of the Cloud Eye console is displayed. The systemautomatically displays the created monitoring panel.

Step 7 Click Add Graph.

The Add Graph dialog box is displayed.

Figure 3-8 Adding a graph

SAPBest Practices



Step 8 In the Add Graph dialog box, set the parameters listed in Table 3-18 to monitorand view the metrics of the resources you care about.

NO TE

When adding a graph, you must specify Resource Type, Dimension, Monitored Object,and Metric one by one from left to right.



Title Specifies the title of the graph to beadded. Only letters, digits, underscores(_), and hyphens (-) are allowed.

SAP

ResourceType

Specifies the type of the resource to bemonitored.

ECS.SAP

Dimension Specifies the metric dimension.● For application, choose

application_sid,eps_application_id.● For SAP HANA, choose

database_sid,eps_application_id.

application_sid,eps_application_id

MonitoredObject

Specifies the object to be monitored.You can select multiple monitoringobjects at a time.

A01,32383274-4a14-4204-a443-d3291543ce0c

Metric Specifies the metric name. For detailsabout the metric, see What Are theMetrics Displayed on the SAP FullScreen Monitoring?

a01_active_instance_quantity

Step 9 Click OK.

On a selected panel, you can view the trends in the new graph. If you hover the

pointer on the graph and click , you can view detailed metric data comparison.

----End

3.7.8 Viewing Alarm InformationAfter provisioning an application, you need to create an alarm rule in the CloudEye console for the application, so that you can view the alarm information on theSAP full screen monitoring page or Cloud Eye.

Prerequisites

The plug-ins have been installed. Otherwise, install them by referring to InstallingSAP Monitoring Plug-ins.

SAPBest Practices



Procedure

Step 1 Log in to the management console.

Step 2 In the navigation pane on the top of the page, choose Service List. UnderManagement & Deployment, click Cloud Eye.

Step 3 In the navigation pane on the left, click Custom Monitoring.

Step 4 Click Create Alarm Rule in the Operation column. For details about how to viewcustom monitoring and create alarm rules, see Custom Monitoring.

Figure 3-9 Creating an alarm rule

NO TE

● After the alarm notification is configured, the system automatically sends an SMSmessage or email to notify the user if an alarm is triggered.

● You can click View Metric in the Operation column to view monitoring metrics. For thedescription about each metric, see What Are the Metrics Displayed on the SAP FullScreen Monitoring?

● Except for customized monitoring metrics, you can select only metrics with (Agent)when creating alarm rules. Otherwise, the alarm information will not be displayed onthe SAP full screen monitoring page. For example: (Agent) CPU usage.

Step 5 View alarm information.

You can view alarm information in either of the following ways:

● In the navigation tree on the left, choose Alarm Management > AlarmHistory.

● Go to the SAP full screen monitoring page. For details, see Viewing the SAPFull Screen Monitoring Page

----End

3.8 Expanding the Capacity of an EVS DiskIf the SAP system is too large, you can expand the capacity of EVS disks of theenterprise project application resources.

Procedure


SAPBest Practices




Step 2 In the navigation pane, choose Application Management > O&M Management.

The Tasks tab page and task list are displayed by default.

Step 3 Click Create Task above the task list.

The Create Task page is displayed. For details, see Table 3-19.



Task Name Custom name of the task. Thename cannot be empty. It cancontain only letters, digits,hyphens (-), and underscores (_).

EVS_disk_expansion-S4HANA-1709

Task Type Choose EVS disk expansion. EVS disk expansion

Select Disk You need to select disks based onthe following information:● Enterprise Project● Application● Server● Disk Name

Enterprise Project: SAPApplication:S4HANA-1709Server: s4hana-1709Disk Name: st-s4hana-1709-data_volume

New Capacity(GB)

Configure the disk capacity (GB)to be added.

10

SAPBest Practices



NO TE

● Capacity expansion is risky. Be caution to perform this operation.

● To prevent data loss, the disk capacity can only be expanded.

● If the expanded disk has been attached to a server, the capacity expansion takes effectafter you restart the server. Some OSs do not need a restart. For details, see the OS list.

● When the MBR partition style is used, the maximum disk capacity supported is 2048 GB,and the rest exceeding 2048 GB cannot be allocated or used. If the disk has alreadybeen put to use, ensure that the disk partition style is checked before expanding itscapacity.

● After the disk has been expanded, you need to log in to the server and manually modifythe file system configuration to use the additional capacity. For details, see ExpansionScenarios.


The task is created.

----End

3.9 Backing up ApplicationsBefore routine backup or major service adjustment, you can back up applicationsso that you can quickly restore data when exceptions occur.

NO TE

Currently, only EVS data can be backed up using Enterprise Project Management. For SFSdata, you need to back it up on your own.

Procedure





The Create Task page is displayed. Configure task information based on Table3-20.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-evs/evs_01_0007.html





Task Name Custom name of the task. Thisfield cannot be left blank. It cancontain only letters, digits,underscores (_), and hyphens (-).

Backup_S4HANA-1709

Task Type Choose Application backup. Application backup

SelectApplication

Select an application based on theenterprise project.

S4HANA-1709


The Create Backup page is displayed.

Step 5 Set the backup.

This function calls Cloud Server Backup Service (CSBS). For details about backupsettings, see the Creating a CSBS Backup.

----End

3.10 Restoring ApplicationsDuring routine management, if an exception occurs, you can restore theapplication using its backups to ensure data reliability.

Procedure





The Create Task page is displayed. Configure task information based on Table3-21.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/qs-csbs/en-us_topic_0072046354.html



Task Name Custom name of the task. Thisfield cannot be left blank. Itcan contain only letters, digits,underscores (_), and hyphens(-).

Restore_S4HANA-1709

Task Type Choose Application recovery. Application recovery

Select CSBSBackup

Filter the backup to berestored by selecting theenterprise project, application,server, or entering the backupname.

-


The Restore Server page is displayed.

Step 5 Click OK.

The application is restored.

----End

3.11 Application Disaster RecoveryYou can create application disaster recovery tasks for ECSs in an application. Whenthe production site is faulty, you can use simple configurations to quickly recoverservices at the DR site.

Creating Application Disaster Recovery




SAPBest Practices




The Create Task page is displayed. Table 3-22 describes the information requiredto configure the task.



Task Name Custom name of the task. Thisfield cannot be left blank. It cancontain only letters, digits,underscores (_), and hyphens (-).

Disaster_S4HANA-1709

Task Type Choose Application disasterrecovery.

Application DisasterRecovery

Select ECS Select the ECS based on enterpriseproject and application.

-

Select ProtectionGroup

Select a protection group from thedrop-down list or click CreateProtection Group.For details about how to setparameters for creating aprotection group, see Create aProtection Group.

-

Step 4 Click Create.

The Create Protected Instance page is displayed. For details, see Create aProtection Instance.

Go back to the task list on the O&M Management page. If the target task statusis Succeeded, the disaster recovery for the application is successful.

----End

3.12 Viewing O&M TasksBy viewing O&M tasks, you can learn about the status, type, enterprise project,and creator of O&M tasks.

Procedure


SAPBest Practices



https://support.huaweicloud.com/intl/en-us/qs-sdrs/en-us_topic_0108180805.html






Step 3 Filter tasks.

You can select the enterprise project that tasks belong to, task type, start and endtime of the task in the upper right corner of the list. You can also enter the taskname to filter tasks.

----End

3.13 FAQs

3.13.1 How Can I View All Enterprise Projects?● When using the master account to log in to the management console, you

can view information about all enterprise projects.● When using a member account to log in to the management console, you can

also view information about all enterprise projects if this member account hasthe global authorization granted by the master account.

3.13.2 Why Does a Member Account with the EPS AdminPolicy Configured Through EPS Have No Permissions to AddUser Groups or Set Policies?

Operations related to user groups depend on the IAM service. IAM is a globalservice and takes effect only after global policies are configured. The policies seton the User Groups tab page on the Enterprise Project Management page takeeffect only for the current enterprise projects.

3.13.3 How Do I Obtain the Enterprise Project ID?● By calling APIs.

Cloud services can be authorized by IAM to call the API that is used to querya list of enterprise projects. The returned project list contains the ID of eachenterprise project. For details about the APIs, see the API Reference ofEnterprise Management service.

SAPBest Practices



● From the enterprise project details page. The specific procedure is as follows:

a. On the HUAWEI CLOUD console, click Enterprise in the upper part of thepage and then Project Management.

b. Click the name of the enterprise project whose ID will be obtained. Theenterprise project ID is displayed on the enterprise project details page.

3.13.4 Why No Data Is Available After I ConfiguredApplication Monitoring Successfully on the SAP Full ScreenMonitoring Page?

Rectify the fault based on the causes listed in Table 3-23.

Table 3-23 Troubleshooting

Possible Cause Troubleshooting

The SAP full screenconfiguration is incorrect orthe configured applicationhas been deleted.

Enter the edit mode and check whether theapplication, application SID, database, anddatabase SID are configured as required. If theyare incorrect, correct them and update theconfiguration.

The Agent and SAP plug-ins are not installed on thecloud server in theapplication.

Install the Agent and SAP plug-ins, and wait forseveral minutes.

The Agent data is stillwithin the reporting cycle.

The reporting cycle from Cloud Eye to EPS is onceevery three minutes. Wait for three minutes andthen refresh the Agent data.

The cloud server metainformation is incorrectlymodified.

Enter the edit mode, update the monitoringconfiguration, and wait for several minutes.

The parameters in themetrics.ini configurationfile are incorrect.

Check whether the configuration file is consistentwith the actual application parameters.

The Agent and daemonprocesses are abnormal.

Check whether the Agent and Telecope processesare normal.

The Agent has notobtained data.

Run the ./sapmon -v command in /usr/local/telescope/plugins/sapmon to check whether anerror is reported when obtaining metrics.

SAPBest Practices



3.13.5 How Can I Add a Dedicated Account for the SAP FullScreen Monitoring?

The system will be disconnected automatically if no operation is performed within30 minutes as an administrator account. You are advised to use the dedicatedaccount for full screen monitoring.

To add a dedicated display account for the SAP full screen monitoring, perform thefollowing steps.

Step 1 Hover the mouse over the username in the upper right corner of the page andclick Identity and Access Management from the drop-down list.

The IAM page is displayed.

Step 2 Create a user group.

1. In the navigation pane on the left, click User Groups.2. Click Create User Group on the upper right of the page.3. Set the user group name and the description information.4. Click OK.

Step 3 Create a dedicated display account for the SAP full screen monitoring.

1. In the navigation pane on the left, click Users.2. Click Create User on the upper right of the page.3. Set user information on the Create User page.

Set User Groups to the user group created in Step 2. For details, see Creatinga User and Adding It to a User Group.

4. Click OK.

Step 4 Configure permission policies for the user group.

1. In the navigation pane on the left, click User Groups.2. In the user group list, choose More > Configure Permission in the Operation

column on the right of the user group to which the created user belongs.3. Configure policies for the global-level project.

a. Click Configure Policy on the right of the global project.b. Select Tenant Guest from the Available Policies list.c. Click OK.

4. Configure policies for all region-level projects supported by the applicationmanagement.

a. Click Configure Policy on the right of the region-level project.b. Select Tenant Guest from the Available Policies list.c. Click OK.

NO TE

The enterprise project is a global-level service, but the SAP full screen monitoring calls theregion-level Cloud Eye service. Therefore, you need to configure policies for the currentsupported regions.

----End

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/qs-iam/iam_01_0031.html

https://support.huaweicloud.com/intl/en-us/qs-iam/iam_01_0031.html

3.13.6 What Are the Metrics Displayed on the SAP Full ScreenMonitoring?

SAP monitoring metrics are classified into SAP HANA metrics, SAP NetWeaverABAP and SAP NetWeaver Java application metrics, and SAP Business One metrics,as shown in Table 3-24, Table 3-25, Table 3-26, and Table 3-27.

NO TE

● Collection period: The unit is minute, and the range is 1 to 60 minutes.● The collection periods of metrics in the same group are managed uniformly.

Table 3-24 SAP HANA metrics

MetricGroup

Metric Description DefaultCollectionPeriod(Minute)

database_version

database_version Database version 1

service_quantity

<hostname>_<sid>_<nr>_service_quantity

Total number ofservices on an ECSwhere SAP HANA isdeployed.

1

active_service_quantity

<hostname>_<sid>_<nr>_active_service_quantity

Number of availableservices on an ECSwhere SAP HANA isdeployed.

1

database_ha_active

database_ha_active Database HA status 1

sr_active sr_active Database systemreplication status

1

threads all_threads Total number ofthreads

1

active_threads Number of activethreads

blocked_threads Number of blockedthreads

sqlexecutor_threads Number of SQLexecution threads

sqlexecutor_threads_active Number of active SQLexecution threads

SAPBest Practices



MetricGroup


jobworker_threads Number of jobthreads

jobworker_threads_active Number of active jobthreads

session total_sessions Total number ofsessions

1

database_users_sessions Number of databaseuser sessions

applications_sessions Number ofapplication sessions

application_users_sessions Number ofapplication usersessions

idle_sessions Number of idlesessions

running_sessions Number of runningsessions

blocking_sessions Number of blockingsessions

blocked_sessions Number of blockedsessions

totalmemory_used_by_services

mem_used Total memory usedby the service

1

resident_mem_used

memory_used_by_services

<hostname>_<sid>_<nr>_<service>_mem_used

Memory used by theservice

1

memory_used_by_tables

table_mem_used Memory used bydatabase tables

1

resource_used

<hostname>_<sid>_<nr>_mem_available_percent

Percentage ofavailable memory

1

<hostname>_<sid>_<nr>_mem_total

Total memory

<hostname>_<sid>_<nr>_mem_available

Available memory

SAPBest Practices



MetricGroup


<hostname>_<sid>_<nr>_mem_used

Used memory

<hostname>_<sid>_<nr>_swap_available

Available swapvolume

<hostname>_<sid>_<nr>_swap_used

Used swap volume

<hostname>_<sid>_<nr>_instance_mem_used

Memory used byinstances

<hostname>_<sid>_<nr>_peak_instance_mem_used

Peak memory usageof instances

memory_used_by_componments

<hostname>_<sid>_<nr>_system_mem_used

Used system memory 1

<hostname>_<sid>_<nr>_monitoring_statistical_data_mem_used

Memory used bymonitoring statistics

<hostname>_<sid>_<nr>_statement_execution_mem_used

Memory fortemporary statementexecution result

<hostname>_<sid>_<nr>_caches_mem_used

Cache memory

<hostname>_<sid>_<nr>_column_store_tables_mem_used

Memory used bycolumn storagetables

<hostname>_<sid>_<nr>_row_store_tables_mem_used

Memory used by rowstorage tables

<hostname>_<sid>_<nr>_code_size_mem_used

Memory used by codesegments

<hostname>_<sid>_<nr>_stack_size_mem_used

Memory used bystacks

recent_data_backup

age_of_recent_data_backup[_tenant_db_name]

Number of hourssince the lastsuccessful full databackup If the backupfails, the value is -1.

1

SAPBest Practices



MetricGroup


recent_savepoint

age_of_recent_savepoint[_tenant_db_name]

Number of minutessince last SAVEPOINTIf the SAVEPOINTdoes not exist, thevalue is -1.

1

recent_savepoint_duration[_tenant_db_name]

Duration (in seconds)of the lastSAVEPOINT If theSAVEPOINT does notexist, the value is -1.

1

largest_table_record_count

largest_table_record_count[_tenant_db_name]

Maximum number ofrecords in a databasetable

1

largest_table_size

largest_table_size[_tenant_db_name]

Maximum size of adatabase table

1

Table 3-25 SAP NetWeaver ABAP application metrics

Metric Group Metric Description DefaultCollectionPeriod(Minute)

logged_in_users logged_in_users Number of users whohave logged in to theSAP application

1

application_version

application_version SAP application version 1

instance_quantity

<sid>_instance_quantity

Total number ofinstances on an ECSwhere the application isdeployed

1

active_instance_quantity

<sid>_active_instance_quantity

Number of availableinstances on an ECSwhere the application isdeployed

1

SAPBest Practices




application_ha_active

application_ha_active Application HA statusNOTE

Only HAE in HA mode issupported.

1

abap_short_dumps

abap_short_dumps Number of ABAP ShortDumps in the last onehour

1

jobs finished_jobs Number of FinishedJobs

1

canceled_jobs Number of CanceledJobs

1

running_jobs running_jobs Number of RunningJobs

1

lock_entries_usage

lock_entries_usage Lock entries usage 1

extended_memory_utilization

<hostname>_<sid>_<nr>_extended_memory_utilization

Extended memoryusage

1

heap_memory_utilization

<hostname>_<sid>_<nr>_heap_memory_utilization

Heap memory usage 1

work_processes <hostname>_<sid>_<nr>_dialog_work_processes_utilization

Dialog work processusage

1

<hostname>_<sid>_<nr>_background_work_processes_utilization

Background workprocess usage

1

<hostname>_<sid>_<nr>_spool_work_processes_utilization

Spool work processusage

1

<hostname>_<sid>_<nr>_update_1_work_processes_utilization

Update 1 work processusage

1

<hostname>_<sid>_<nr>_update_2_work_processes_utilization

Update 2 work processusage

1

SAPBest Practices




<hostname>_<sid>_<nr>_number_of_total_dialog_work_processes

Total number of dialogwork processes

1

<hostname>_<sid>_<nr>_number_of_total_background_work_processes

Total number ofbackground workprocesses

1

<hostname>_<sid>_<nr>_number_of_total_spool_work_processes

Total number of spoolwork processes

1

<hostname>_<sid>_<nr>_number_of_total_update_1_work_processes

Total number of update1 work processes

1

<hostname>_<sid>_<nr>_number_of_total_update_2_work_processes

Total number of update2 work processes

1

<hostname>_<sid>_<nr>_number_of_free_dialog_work_processes

Total number of idledialog work processes

1

<hostname>_<sid>_<nr>_number_of_free_background_work_processes

Total number of idlebackground workprocesses

1

<hostname>_<sid>_<nr>_number_of_free_spool_work_processes

Total number of idlespool work processes

1

<hostname>_<sid>_<nr>_number_of_free_update_1_work_processes

Total number of idleupdate 1 workprocesses

1

<hostname>_<sid>_<nr>_number_of_free_update_2_work_processes

Total number of idleupdate 2 workprocesses

1

logged_in_users <hostname>_<sid>_<nr>_logged_in_users

Number of logged usersto an instance

1

SAPBest Practices




abap_short_dumps_5m

abap_short_dumps_5m Number of ABAP ShortDumps (Five Minutes)Number of ABAP ShortDumps in the last fiveminutes

5

update_records update_records Number of updaterecords in the last oneminute

1

failed_updates failed_updates Number of failedupdates in the last oneminute

1

rfc_ping <hostname>_<sid>_<nr>_rfc_ping

rfc_pingRFC ping latency fromthe Agent node to theAAS node

1

dialog_response_time

<hostname>_<sid>_<nr>_dialog_response_time

Dialog response time 1

dialog_db_request_time

<hostname>_<sid>_<nr>_dialog_db_request_time

Dialog databaserequest time

1

failed_idocs failed_idocs Number of IDocs in thewarning and errorstatuses

1

Table 3-26 SAP NetWeaver Java application metrics


instance_quantity

<sid>_instance_quantity

Total number ofinstances on an ECSwhere the application isdeployed

1

SAPBest Practices






Number of availableinstances on an ECSwhere the application isdeployed

1

j2ee_running_process_count

j2ee_running_process_count

Number of runningJava processes

1

j2ee_thread_count

j2ee_thread_count Number of Java threads 1

j2ee_session_count

j2ee_session_count Number of Javasessions

1

j2ee_websession_count

j2ee_websession_count Number of Java websessions

1

j2ee_ejbsession_count

j2ee_ejbsession_count Number of Java EJBsessions

1

j2ee_vm_heap_size

j2eevmheap_<processname>_<type>_size

Size of the local classesor local objects heap inthe Java process

1

j2eevmheap_<processname>_<type>_commitSize

Commit size of thelocal classes or localobjects heap in theJava process

j2eevmheap_<processname>_<type>_maxUsedSize

Maximum used size ofthe local classes orlocal objects heap inthe Java process

j2eevmheap_<processname>_<type>_initialSize

Initial size of the localclasses or local objectsheap in the Javaprocess

j2eevmheap_<processname>_<type>_maxSize

Maximum size of thelocal classes or localobjects heap in theJava process

SAPBest Practices



Table 3-27 SAP Business One metrics

Metric Group Metric Description DefaultCollection Period(Minute)

instance_quantity <sid>_instance_quantity

Total number ofinstances on an ECSwhere the applicationis deployed

1



Number of availableinstances on an ECSwhere the applicationis deployed

1

b1_version application_version SAP Business Oneversion

1

application_b1servertools_active

application_sld_active

Status information ofSAP Business OneServer Tools

1

application_b1s_active

application_b1s_active

Status information ofSAP Service Layer

1

application_sldagent_active

application_sldagent_active

Status information ofSAP SLD Agent

1

3.13.7 What Can I Do If SAP S/4HANA 1610 Fails to ObtainMonitoring Metrics?

If the SAP S/4HANA 1610 cannot obtain the monitoring metrics, perform thefollowing operations:

Step 1 Activate the background dispatching.

1. Log in to SAP GUI.2. On the SAP menu, choose CCMS > Configuration > Alert Monitor.3. On the displayed page, choose Technical Infrastructure > Local Method

Execution > Activate Background Dispatching.

Step 2 Activate the central system dispatching.

1. Log in to SAP GUI.2. On the SAP menu, choose CCMS > Configuration > Alert Monitor.3. On the displayed page, choose Technical Infrastructure > Method Execution

> Activate Central System Dispatching.

Step 3 View monitoring metrics.

----End

SAPBest Practices



4 Best Practices of SAP Migration toHUAWEI CLOUD

4.1 Overview

4.1.1 Migration ScenariosIf your SAP system uses old version software whose performance is poor, or thesystem is deployed on cloud servers of small specifications with an inflexiblearchitecture, you are suffering from slow system running and high O&M costs,especially when the businesses running on the system are growing. An increasingnumber of customers are choosing to migrate SAP systems to HUAWEI CLOUD toreduce costs and improve efficiency. HUAWEI CLOUD SAP on Cloud solutionprovides comprehensive cloud deployment schemes, improving the efficiency andreducing costs.

SAP migration projects are much more complex than traditional IT migrationprojects. An SAP migration project involves hardware migration, software upgrade,service and interface testing, project management, and risk control. In addition, aSAP migration project involves personnel and organizations from multiple parties,including customer's IT team, service team, migration implementor, andinfrastructure provider. A successful migration project requires close collaborationamong all the parties. During the migration, HUAWEI CLOUD providesinfrastructure and assistants the migration. In addition, HUAWEI CLOUD platformwill facilitate the project implementation.

This document is not a replacement of SAP's or database vendor's officialdocuments. This document is intended for SAP migration consultants and SAPpractitioners. The restrictions and specifications of SAP software and databases inthis document are subject to the official documents.

This document assumes that you are familiar with SAP system deployment andoperations on HUAWEI CLOUD. If you are new to HUAWEI CLOUD SAP on Cloudsolution, read the following documents:

● SAP Deployment Guide● SAP S/4HANA Quick Deployment Guide● SAP HANA User Guide (Single Node)

SAPBest Practices

4 Best Practices of SAP Migration to HUAWEICLOUD


https://support.huaweicloud.com/intl/en-us/dg-sap/sap_05_0002.html


https://support.huaweicloud.com/intl/en-us/ugs-saphana/saphana_02_0002.html

● SAP NetWeaver User Guide

This document describes how to migrate SAP systems from on-premises or othercloud platforms to HUAWEI CLOUD in four typical migration scenarios, asdescribed in Table 4-1. You can select a suitable migration solution based on theactual requirements.

Table 4-1 Migration scenarios

Scenario Description Solution

MigratingSAPsystemsfrom x86platform toHUAWEICLOUD

In this scenario, youmigrate an SAP system thatis deployed on an x86physical machine in youron-premises data center ora VMWare virtual machine(VM). The supportedoperating systems (OSs) ofservers are listed in OSsSupported by DifferentTypes of ECSs. There is norestriction on the database.After the migration toHUAWEI CLOUD, thedatabase and OSs remainunchanged.

Use the following services and toolsto migrate the system:● Use HUAWEI CLOUD Server

Migration Service (SMS) tomigrate SAP applicationservers without serviceinterruption, replicating off-cloud servers to HUAWEICLOUD.

● If there is no requirement ondatabase downtime, use theSMS to migrate the databaseof a non-production system.

● To reduce the service downtime,use the native databasemigration tool to move theproduction system database tothe cloud. For example, useSystemReplication, OralceDataGuard, or SQL LoggingShipping migrate HANA.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-sapnw/sapnetweaver_01_0001.html

https://support.huaweicloud.com/intl/en-us/productdesc-ims/ims_01_0007.html




MigratingSAPsystemsform athird-partycloud toHUAWEICLOUD

In this scenario, youmigrate an SAP system thatis deployed on a third-partycloud. The supported serverOSs are listed in OSsSupported by DifferentTypes of ECSs. There is norestriction on the database.In addition, other cloudservices, such as objectstorage service, can beinvolved in. After themigration to HUAWEICLOUD, the database, OSs,and system architectureremain unchanged. Theinvolved cloud services ofother cloud vendors will bechanged to those ofHUAWEI CLOUD.

The solution is similar to that ofthe previous scenario. However,there are some differences:● You can easily adjust the

network bandwidth between thethird-party cloud platform andHUAWEI CLOUD. The maximumbandwidth can be hundreds ofMbit/s.

● Generally, the systemarchitecture does not needadjustment. If the on-premisessystem architecture is complex,you need to replan thedeployment architecture of thesystem on the cloud.

● Generally, an on-premisessystem contains only physicalservers or VMs. A system on athird-party cloud may containcloud service resources.

MigratingSAPsystemsfrom IBMor HPmidrangecomputersto HUAWEICLOUD

In this scenario, youmigrate an SAP systemdeployed on IBM or HPmidrange computers. TheOSs are not supported byHUAWEI CLOUD. There isno restriction on thedatabase. After themigration, the OSs arechanged to thosesupported by HUAWEICLOUD, and the databaseremains unchanged.

You need to deployed applicationservers and the database server ofthe system on HUAWEI CLOUD.The target system is redeployed onHUAWEI CLOUD ECSs or BMSs.Solutions for database migrationare as follows:● Use the SAP R3load Export/

Import function to migrate thedatabase.

● Or use some native databasetools, such as OracleGoldenGate or Oracle XTTS.

SAPBest Practices







MigratingSAPapplications runningon a non-HANAdatabaseto HUAWEICLOUD SAPHANA

In this scenario, youmigrate an SAP systemdeployed in the local datacenter. The database is anon-HANA database (suchas Sybase, Oracle, andDB2). The target end isHUAWEI CLOUD SAPHANA system. The serverOSs may change.

The project includes systemmigration, software upgrade, anddatabase and OS change.● Use the database migration

option (DMO) of SAP SUM toupgrade and migrate the SAPsystem to HUAWEI CLOUD SAPHANA system.

● Use the Classical Migration toSAP HANA solution. Use SUMto upgrade the system to asupported version, and then usethe System Copy function ofSWPM to migrate the systemonto the HANA database.

Due to the complexity of a migration project, this section will not include thedetailed migration processes, but only focuses on the part related to HUAWEICLOUD. There are two types of migration:

● Homogeneous migration: The databases and OSs of the source anddestination servers remain unchanged, and the software can be upgraded inthe homogeneous migration.

● Heterogeneous migration: Either of databases and OSs are changed.

You can view the following examples:

● Homogeneous migration:– Migrating the SAP System from the x86 Platform to HUAWEI CLOUD– Migrating from a Third-Party Cloud to HUAWEI CLOUD

● Heterogeneous migration:– Migrating from IBM or HP Midrange Computers to HUAWEI CLOUD– Migrating SAP Applications Running on a Non-HANA Database to

HUAWEI CLOUD SAP HANA

4.1.2 Migration SolutionsTable Migration services and tools describes the services and tools recommendedby HUAWEI CLOUD to migrate an SAP system. The table compares the applicationscopes, downtime, and migration complexity of the solutions. You can select asolution that meets your requirements. For details about migration operations ofeach solution, see Migration Solution Details.

SAPBest Practices



https://blogs.sap.com/2013/11/29/database-migration-option-dmo-of-sum-introduction/


https://blogs.sap.com/2013/12/03/classical-migration-to-sap-hana/


Table 4-2 Migration services and tools

Service/Tool

Advantages andDisadvantages

Application Scope

DatabaseInterruptionDuration(Bandwidth:100 Mbit/s)

TechnicalSupport

Scenarios

500GBdatabase

2 TBdatabase

ServerMigrationService orServerMigrationTool (P2Vand V2Vmigrationtools)

Advantages: Themigrationof SAPapplicationservers anddatabaseservers iseasy.Disadvantages: Thedowntimeis long.Only theX86platform issupported.

Applies tohomogeneous x86platformmigration.Theserviceand toolcanmigrateSAPapplications anddatabases.Interruptthedatabaseservicewhen youmigratethedatabaseusingSMS.

About18hours

About65hours

HUAWEICLOUDServerMigrationService

Migratingan SAPsystem fromthe X86platform toHUAWEICLOUDMigratingan SAPsystem froma third-partycloud toHUAWEICLOUD

Databasebackup andrestorationfunction

Advantages: ShortdowntimeDisadvantages: Onlyhomogeneousmigrationissupported.

Applies tothemigrationbetweendatabasesof thesametype.

Fullmigration:About20hoursIncrementmigration:About2hours

Fullmigration:About70hoursIncrementmigration:About 2hours

Databaseprovider

Migratingan SAPsystem fromthe X86platform toHUAWEICLOUDMigratingan SAPsystem froma third-partycloud toHUAWEICLOUD

SAPBest Practices



Service/Tool


Application Scope


TechnicalSupport

Scenarios

Databasereplication(includingHANA SRand OracleDataGuard)

Advantages: Thedowntimeisshortenedto minutes.Disadvantages: Theoperationsarecomplexand requireexpertise.

Applies tothemigrationbetweendatabasesof thesametype.

Within1 hour

Within1 hour

Databaseprovider

Migratingan SAPsystem fromthe X86platform toHUAWEICLOUDMigratingan SAPsystem froma third-partycloud toHUAWEICLOUDMigratingan SAPsystem fromIBMmidrangecomputersto HUAWEICLOUD(withdatabaserestrictions)

SAPBest Practices



Service/Tool


Application Scope


TechnicalSupport

Scenarios

DMO ofSAP SUM

Advantages: You canupgradethe SAPsystemwhilemigratingthedatabase.Disadvantages: Theoperationsarecomplexand requireexpertise.

Applies tohomogeneous andheterogeneousmigrationandsupportsSAPupgradeduring thedatabasemigration.Migratesdata fromotherdatabasesto theHANAdatabase.

About10hours

About45hours

SAP Migratingan SAPsystem fromthe x86platform toHUAWEICLOUDMigratingan SAPsystem froma third-partycloud toHUAWEICLOUDMigratingan SAPsystem fromIBMmidrangecomputersto HUAWEICLOUDMigratingan SAPsystemrunning ona non-HANAdatabase toHUAWEICLOUD SAPHANAdatabase

SAPBest Practices



Service/Tool


Application Scope


TechnicalSupport

Scenarios

R3load(parallelimport andexportfunction)

Advantages: astandardSAP toolthat is easyto useDisadvantages: Thedowntimeis long,whichdepends onthedatabasesize.

Supportshomogeneous andheterogeneousmigration.

About24hours

About48hours

SAP Migratingan SAPsystem fromthe x86platform toHUAWEICLOUDMigratingan SAPsystem froma third-partycloud toHUAWEICLOUDMigratingan SAPsystem fromIBMmidrangecomputersto HUAWEICLOUDMigratingan SAPsystemrunning ona non-HANAdatabase toHUAWEICLOUD SAPHANAdatabase

4.1.3 Related Cloud ServicesPublic cloud refers to a cloud based on the standard cloud computing model, inwhich service providers make resources available to the general public over theInternet. The core attribute of a public cloud is its shared resources. HUAWEICLOUD is a public cloud and provides the following cloud services to implementSAP system migration. You can use HUAWEI CLOUD services independently ortogether to meet your migration requirements. Table 4-3 lists the cloud servicesthat can be used during the migration.

SAPBest Practices



Table 4-3 HUAWEI CLOUD services

Service Features

SMS Server Migration Service provides P2V and V2V migration services tohelp you migrate applications and data from on-premises X86physical servers or VMs on private or public clouds to HUAWEICLOUD Elastic Cloud Servers (ECSs).SMS migrates SAP application servers while the applications arerunning, and migrates database servers after the database service isstopped. You can use SMS to migrate incremental data.For more information about SMS, see What is Server MigrationService.

IMS If your SAP application servers can be converted into image files,and the types and OSs of the image files are listed inFormats and OSs Supported for External Image Files, you cancreate the SAP application server image files as private images onHUAWEI CLOUD, and use the images to quickly deploy newapplication servers.For details, see Creating a Linux System Disk Image from anExternal Image File and Creating a Windows System Disk Imagefrom an External Image File.

OMS Object Storage Migration Service is an online data migration service.If the source SAP system has object storage data (such as databasebackup files and software installation media) stored on a third-partycloud, the OMS can smoothly migrate the data from the third-partycloud to the HUAWEI CLOUD.Note: This service applies only to migrate objects storage from athird-party cloud.For details about how to use the OMS, see Object StorageMigration Service Introduction.

DES Data Express Service is a massive data transmission solution. Itallows transmitting a large amount of data using Teleport devices ordisks (with external USB interfaces, SATA interfaces, or SASinterfaces) to HUAWEI CLOUD. DES helps to address issues facingmassive data transmission such as high network costs and longtransmission time.If the source SAP system has storage devices with a large amount ofdata, for example, the storage device where the database backupdirectory resides, you can use DES for migration. Whether to use DESdepends on the amount of data and the network bandwidth. Fordetails, see DES Application Scenarios.For more information about DES, see the DES Product Overview.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/productdesc-sms/sms_01_0002.html


https://support.huaweicloud.com/intl/en-us/productdesc-ims/en-us_topic_0030713143.html

https://support.huaweicloud.com/intl/en-us/usermanual-ims/en-us_topic_0030713191.html




https://support.huaweicloud.com/intl/en-us/productdesc-oms/en-us_topic_0045916963.html

https://support.huaweicloud.com/intl/en-us/productdesc-oms/en-us_topic_0045916963.html

https://support.huaweicloud.com/intl/en-us/productdesc-des/des_01_0036.html

https://support.huaweicloud.com/intl/en-us/productdesc-des/zh-cn_topic_0047663842.html

4.2 Migration ProcedureFigure 4-1 shows the implementation procedure of a typical SAP migrationproject.

Figure 4-1 Migration procedure

The implementation phases are as follows:

1. Project PreparationBased on specific requirements and application system information, assess therisks and feasibility of the cloud migration. Collect information andassessment results to plan the project and design the solution. Manage theproject, for example, establish a project team and formulate teammanagement regulations.HUAWEI CLOUD provides a system deployment solution and offers migrationsuggestions. The solution includes computing, network, and security resourceson the cloud, and account systems.

2. Tests and DrillsSet up the migration environment to ensure that the system will meet therequirements after the migration to HUAWEI CLOUD. Ensure that no problemremains unsolved in each phase of the migration project.HUAWEI CLOUD provides a series of user and deployment guides to help youmigrate the system:

SAPBest Practices



– SAP HANA User Guide (Single Node)

– SAP NetWeaver User Guide

– SAP Business One User Guide

– SAP S/4HANA Quick Deployment Guide

– SAP Business One Quick Deployment Guide

– SAP Deployment Guide

3. Preparations for Bringing the System Online

Optimize the migration solution based on the drill and test results anddetermine the final solution. List known issues and transmission items. TestHA, switchover, and shutdown solutions, and decide the switchover andshutdown plan. Design and verify the rollback solution.

This task is performed by the migration implementor and supported byHUAWEI CLOUD.

4. System Switchover

Migrate the workload according to the final switchover plan and solutiondetermined based on the system tests.


5. Bringing the System Online

Continuously monitor the system after it is brought online and optimize thecloud architecture if necessary.


4.3 Migrating the SAP System from the x86 Platform toHUAWEI CLOUD

4.3.1 DescriptionIn this scenario, you migrate an SAP system that is deployed on an X86 physicalmachine in your on-premises data center or VMWare VM. The supported OSs ofservers are listed in OSs Supported by Different Types of ECSs. There is norestriction on the database. After the migration to HUAWEI CLOUD, the databaseand OS remain unchanged.

Use HUAWEI CLOUD Server Migration Service to migrate SAP application serverswithout service interruption, replicating off-cloud servers to HUAWEI CLOUD. Fordatabase migration:

● Non-production system database: If there is no requirement on databasedowntime, use Server Migration Service to migrate the database offline.

● Production system database: To reduce the service downtime, use the nativedatabase migration tool to migrate the database.

Figure 4-2 shows the migration plan.

SAPBest Practices





https://support.huaweicloud.com/intl/en-us/usermanual-sapb1/sapbo_01_0002.html


https://support.huaweicloud.com/intl/en-us/ugqd-sapb1/sapb1_01_0002.html



Figure 4-2 Migrating the SAP system from the x86 platform to HUAWEI CLOUD

4.3.2 Solution Design

Deployment PlanUse HUAWEI CLOUD services for the deployment. Specifically, use ECS or BMS forserver computing resources, and EVS and SFS for storage.

Table 4-4 Deployment plan

Migrate Object Source Target

Application server Physical server ECS

Database server Physical server ECS or BMS

Storage Physical hard disk EVS

Figure 4-3 shows a typical SAP system deployment architecture on HUAWEICLOUD. The architecture of a new deployment or that used in a migration toHUAWEI CLOUD is similar to this one.

SAPBest Practices



Figure 4-3 SAP deployment architecture

For more features and details, see SAP Deployment Guide.

You can also visit the SAP official website to learn more about the SAP productsrelated to HUAWEI CLOUD. Table 4-5 lists the SAP notes.

Table 4-5 HUAWEI CLOUD-related SAP notes

SAPNote #

Title

2582296

SAP Applications on Huawei Cloud: Supported Products and HuaweiCloud VM types

2582305

SAP on Huawei Cloud: Support prerequisites

2570214

Linux on Huawei Cloud: Adaption of your SAP License

2570198

SAP on Linux with Huawei Cloud: Enhanced Monitoring

2644322

SAP Adaptive Server Enterprise (ASE) 16.0 Certification Report forHuawei Cloud

Determine the number and specifications of servers deployed on HUAWEI CLOUDbased on the source system status, service requirements, and the precedinginformation. Then, design the HUAWEI CLOUD deployment plan. The deploymentplan needs to contain the detailed information about cloud product selection andnetworking plan to guide subsequent resource provisioning.

SAPBest Practices




http://service.sap.com/sap/support/notes/2582296

http://service.sap.com/sap/support/notes/2582296

https://launchpad.support.sap.com/#/notes/2582305






http://launchpad.support.sap.com/#/notes/2644322

http://launchpad.support.sap.com/#/notes/2644322

Networking PlanAfter the migration, a VPC is used on the cloud. For details about subnet planning,see the VPC User Guide. HUAWEI CLOUD is connected with the on-premises IDCusing EIP, VPN, or Direct Connect.

HUAWEI CLOUD VPC is an isolated and private virtual network environment thatusers apply for on the HUAWEI CLOUD. You can configure IP address segments,subnets, and security groups, assign EIPs, and allocate bandwidths in a VPC.Figure 4-4 shows the network architecture.

Figure 4-4 Network architecture

VPC provides multiple connections between the local system of a user and the SAPsystem running on HUAWEI CLOUD. You can select a connection type as required.

● Direct Internet ConnectionYou can configure a public EIP address on the cloud server to connect it to thepublic network through the EIP service. The SAP technical support personnelcan access the system deployed on HUAWEI CLOUD using the public IPaddress.

● Direct ConnectDirect Connect helps you establish a dedicated network that connects yourlocal data center to the public cloud. Direct Connect sets up dedicatedconnections between the Direct Connect gateway and a VPC on the publiccloud. With Direct Connect, you can establish network circuits between thecloud and your data center, office, or collocation environment. Direct Connectcan effectively reduce network latency and improve network experience.

● VPNVPN establishes a secure, encrypted communication tunnel between the VPNgateway of the VPC on HUAWEI CLOUD and the VPN gateway of your localdata center, allowing you to directly use resources in the VPC through theVPN.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-vpc/vpc_0001.html

By default, cloud servers in a VPC cannot communicate with your data centeror private network. To enable communication between them, you can createa VPN.

Security DesignEnterprises store core data in the SAP system. HUAWEI CLOUD ensures thesecurity of the SAP system based on the cloud platform security and networkconfigurations.

You are recommended to divide the cloud-based system (production environmentand development and test environment) into zones of different security levels,including the management, application, SAP DB, and demilitarized zones (DMZ).The zones are isolated from each other using VPCs or subnets.

Figure 4-5 Production environment security solution

Figure 4-6 Development and test environment security solution

For details, see SAP Security White Paper.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/swp-sap/sap_03_0002.html

Service Account System DesignAfter the system is deployed on the cloud, HUAWEI CLOUD provides enterprisemanagement services for enterprise group uses to manage the employees,finance, and materials in multi-level organizations and multi-project mode and tostandardize enterprise operation requirements on HUAWEI CLOUD. Figure 4-7shows the HUAWEI CLOUD enterprise accounts. For details, see EnterpriseManagement.

Figure 4-7 Enterprise accounts

Migration SolutionTable 4-6 lists the recommended migration solution. For details about themigration methods, see Migration Solution Details.

Table 4-6 Migration Solution

Migrate Object Migration Plan Description

Applicationserver

SMS or SMTNOTE

If the source server cannotaccess SMS, use SMT.

SMS supports online andincremental migration. You arerecommended to migrate SAPapplication servers online inincremental mode for multipletimes.Data transmission time =Actual data volume/Actualnetwork bandwidthTable 4-7 lists the estimatedtime for transmitting 1 TBdata. Estimate the timerequired for transmitting databased on the actual datavolume. If the data cannot betransmitted within theestimated time, increase thenetwork bandwidth.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-em/em_am_0006.html

https://support.huaweicloud.com/intl/en-us/usermanual-em/em_am_0006.html

Migrate Object Migration Plan Description

Database server ● The non-productionsystem database can bemigrated offline usingSMS.

● The production systemdatabase is migratedusing the nativedatabase tool, such asthe database backupand restore tool.

If you use SMS to migrate thedatabase, SMS performs onlineclone of the OS. All the dataon the OS, such as theapplication software andsystem configurations, isreplicated to the target system.Generally, the applicationsoftware can be started at thetarget system. However, if thedatabase is migrated when it isrunning, the database may failto start after the migration.Therefore, you need to migratethe database offline when youuse SMS.

Table 4-7 Theoretical time for transmitting 1 TB data

Network Bandwidth 2Mbit/s

10Mbit/s

50Mbit/s

100Mbit/s

Theoretical time (80% networkutilization rate)NOTE

Transmission time (days) = [Total capacity(KB)]/[Bandwidth (Mbit/s) x 125 xNetwork utilization rate x 60 (seconds) x60 (minutes) x 24 (hours)]

106days

13 days 60 hours 30hours

Service Switchover PlanThe owner of the service switchover plan is the migration implementor. Thissection provides an example of the service switchover plan.

SAPBest Practices



Table 4-8 Switchover plan example

MigrationPlan

Switchover Plan Impact

Use SMS tomigrateapplicationservers online,and use SMTto migratedatabaseservers offline.

1. After using SMS tomigrate the applicationservers to HUAWEICLOUD, use incrementalreplication tosynchronize the sourceend server changes toHUAWEI CLOUD online.

2. After stopping thedatabase, use SMS tomigrate the databaseservers to HUAWEICLOUD.

The database servers aremigrated offline, so theinterruption will be long. Thisplan applies to the non-production system.Interruption duration = Datatransmission time for thedatabase server +Commissioning time after themigration

Deployapplicationservers on thecloud, and usethe backupand restoreplan fordatabaseservers.

1. Commission theapplication servers afterthe deployment.

2. Restore the databaseservers using fullbackup.

3. Stop the database at thesource end. Upload theincremental data andnecessary log files to thedatabase on the cloud.Restore the databaseusing the incrementaldata.

Stop the servers at the sourceend before the incrementalbackup of the last time.Compared with the offlinemigration plan, this plan causesshorter interruption, so it appliesto the production system.Interruption duration = Time forincremental backup + Time fortransmitting incremental data+ Time for restoring theincremental data

4.3.3 Preparing ResourcesTo ensure smooth migration, you need to perform the following operations:

1. Prepare the network environment.

a. Follow the descriptions in Networking Plan to interconnect the sourceserver with HUAWEI CLOUD, establish network connectivity using CloudConnect, and configure VPN. For details, see SAP Deployment Guide.

b. Set up the HUAWEI CLOUD network environment, including creatingVPCs, subnets, and security groups. For details, see the related section inthe SAP Deployment Guide.

2. Prepare software tools required for the migration, such as SAP migrationsoftware and specific database migration tool.

3. Prepare resources at the source end.

SAPBest Practices





a. Back up the data at the source end, including important files andsoftware installation packages. You are advised to back up the data toHUAWEI CLOUD OBS.

b. Check the source server settings. Check whether the source server OSmeets migration requirements by referring to OSs Supported byDifferent Types of ECSs, and check the data volume on the sourceserver.

4. Prepare resources at the target end.

a. Provision HUAWEI CLOUD server resources based on Deployment Plan.b. Set the security parameters based on Security Design.c. Purchase OBS, SFS, OMS, and DES on HUAWEI CLOUD as required.

4.3.4 Migrating Application Servers to HUAWEI CLOUDYou can migrate SAP application servers to HUAWEI CLOUD using either of thefollowing methods:

● Method 1: Using SMS● Method 2: Importing Images

Method 1: Using SMS is recommended. If VMs are at the source end, you can useMethod 2: Importing Images.

Method 1: Using SMSIf you use SMS for migration, the systems at the source end and target end arebasically the same. For details about the changes, see What Are the DifferencesBetween Target ECSs and Source Servers After the Migration?.

The following uses an SAP HANA database server as an example to describe themigration procedure.

Step 1 Back up the source end data and software.

Step 2 Obtain the AK/SK of the account to which the target server belongs.● If you need to use an account to migrate servers, see How Do I Obtain the

AK and SK of an Account?.● If you have created an IAM user under this account, grant the permission to

the IAM user and use the IAM user to create the AK/SK. For details, see HowDo I Obtain the AK and SK of an IAM User?.

Step 3 Install the migration Agent on the source server. For details, see How Can I Installthe Migration Agent on Source Servers?. Enter the AK/SK obtained in Step 2when they are required by SMS-Agent.

Step 4 After the migration Agent is started successfully, it automatically collectsinformation about the source server and sends collected information to SMS. SMSautomatically checks whether the source server information is valid and whetherthe source server can be migrated. After the migration Agent uploads sourceserver information to SMS, you can log in to the HUAWEI CLOUD managementconsole at any time to view information about the source server using theHUAWEI CLOUD account of the target server. For details, see Viewing CheckResults.

SAPBest Practices





https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0008.html








https://support.huaweicloud.com/intl/en-us/qs-sms/sms_02_0005.html


Step 5 Start the migration task. For details, see Creating and Starting a Migration Task.

NO TE

● Ensure that source servers are on during the migration.● When you migrate the database, stop the database before the last time synchronization

and then migrate it offline.

Step 6 After the migration task is complete, log in to the target server using the sourceserver login mode. Check whether the basic functions are normal, including thenetwork and storage.

Step 7 Modify the basic OS settings of the target server to adapt to HUAWEI CLOUD.

1. Modify the DNS and NTP configurations. For details, see How Can IConfigure the NTP and DNS Servers for an ECS?.

2. (Optional) Install and configure Cloud-Init. For details, see Installing Cloud-Init and Configuring Cloud-Init.For more about Cloud-Init, see Cloud-init.

3. (Optional) Install the HUAWEI CLOUD one-click password reset plug-in. Fordetails, see (Optional) Installing the One-Click Password Reset Plu.

4. Modify the host name and the hosts file as required. For details, seeChanging Host Name.

5. Install Data Provider.Data Provider is the SAP metric collector on HUAWEI CLOUD. For detailsabout how to install and configure Data Provider, see Data Provider for SAPUser Guide.

6. Restart the server and check whether other OS errors occur.

Step 8 Check whether the SAP HANA database can start properly.

1. Switch to user {$SID}ADM and run the HDB start command to start thedatabase.

2. Run the sapcontrol -nr 00 -function GetProcessList command to query thestatus of all SAP HANA processes. The command output shows that all SAPHANA processes are in the GREEN state.

3. Use SAP HANA Studio to connect to the SAP HANA database and checkwhether the connection is successful and whether all processes are in thenormal state.

SAPBest Practices




https://support.huaweicloud.com/intl/en-us/ecs_faq/en-us_topic_0074825901.html


https://support.huaweicloud.com/intl/en-us/bestpractice-ims/ims_bp_0023.html



https://support.huaweicloud.com/intl/en-us/productdesc-ecs/ecs_01_0055.html





Step 9 (Optional) After a migration task is complete, you can use SMS to synchronize theincremental data from the source servers to the target servers as needed. Fordetails about how to perform the incremental synchronization, see SynchronizingData After a Migration Task Is Complete.

NO TE

After the incremental synchronization, the status of the target server becomes consistentwith the source server. Perform Step 6 to Step 8 after the synchronization is complete.

Step 10 Connect the application with the database to test whether the system isfunctional.

----End

Method 2: Importing ImagesIf your source servers can be converted into image files, and the type and OS ofthe image files are listed in Formats and OSs Supported for External ImageFiles, you can create the source server image files as private images on HUAWEICLOUD, and use the images to quickly deploy new servers on HUAWEI CLOUD.

Step 1 Export the source server as images of formats supported by HUAWEI CLOUD,You can use the recommended tool to convert the image format. For details, seeConverting the Image Format Using qemu-img.

Step 2 Upload the external image file to the OBS bucket. For details, see Uploading anExternal Image File.

Step 3 Select the uploaded image file on the management console and register theimage file as a private image. For details, see Creating a Linux System DiskImage from an External Image File and Creating a Windows System DiskImage from an External Image File.

Step 4 Use the created image to provision new servers in the planned environment basedon the design.

----End

4.3.5 Migrating the Database to HUAWEI CLOUDYou can use either of the following methods to migrate the database:

● You can use SMS to migrate the database, but the migration must beperformed offline. For details, see Method 1: Using SMS.

● If you have high database downtime requirements, you can use the databasebackup and restoration function or database synchronization technology tomigrate the database.

SAPBest Practices



https://support.huaweicloud.com/intl/en-us/usermanual-sms/sms_03_0011.html

https://support.huaweicloud.com/intl/en-us/usermanual-sms/sms_03_0011.html



https://support.huaweicloud.com/intl/en-us/ims_faq/ims_faq_0016.html


https://support.huaweicloud.com/intl/en-us/usermanual-ims/ims_01_0210.html

https://support.huaweicloud.com/intl/en-us/usermanual-ims/ims_01_0210.html





This document uses the SAP HANA database as an example to describe howto reduce migration RTO. For details, see Method 2: Using the DatabaseBackup and Restore Function and Method 3: Using the DatabaseSynchronization Technology.

Method 1: Using SMS

To ensure data consistency between the target system and the source system, youneed to stop services at the source end before the last time incrementalsynchronization. Then, repeat procedures in Method 1: Using SMS.

Method 2: Using the Database Backup and Restore Function

The database backup and restoration function uses the backup of the sourcesystem data and restore it in the target system.

The following uses the SAP HANA database as an example to describe how to usemethod to migrate the database to HUAWEI CLOUD.

Step 1 Migrate the source database to HUAWEI CLOUD by performing steps provided inMigrating Application Servers to HUAWEI CLOUD. Alternatively, deploy SAPHANA servers on HUAWEI CLOUD. For details, see SAP HANA User Guide.

Step 2 Stop the database service at the source end and perform a full backup for thedatabase. Ensure that the necessary logs are retained. Transfer the backup file tothe target server on HUAWEI CLOUD.

You can also use OBS to transfer files. OBS provides multiple tools to acceleratethe file upload. For details, see OBS Tools.

Step 3 Log in to the target server and use HANA Studio or run the hdbsql command torestore the backup data to the database. For details, see SAP HANAAdministration Guide.

NO TE

● If the size of a full backup file is large, data transmission and restoration will take a longtime. To reduce the downtime, you can restore the data on the target system using afull backup without stopping services on the source system. After you stop the servicesat the source end, perform a differential or incremental backup and then restore thedifferential or incremental backup to the target system.

● Alternatively, you can use SMS to migrate source servers to HUAWEI CLOUD so that youdo not need to deploy the system again, and part of the backup data can be migratedto the target server. You only need to perform a differential or incremental backup andthen restore it to the target system.

Step 4 Start the SAP HANA database on the cloud and verify that the database isfunctional and the data is intact.

Step 5 Connect the application with the database to test whether the system isfunctional.

----End

SAPBest Practices




https://support.huaweicloud.com/intl/en-us/tg-obs/obs_09_0001.html

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/c4663eabbb571014923a90c70cec566c.html

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/c4663eabbb571014923a90c70cec566c.html

Method 3: Using the Database Synchronization Technology

Databases have their native tools to support synchronous data replication, such asHANA System Replication, Oracle Data Guard, On Availability Groups (SQLServer), and Q Replication of DB2.

The following uses the SAP HANA database as an example to describe how to useHANA System Replication to migrate the database to HUAWEI CLOUD.

Step 1 Migrate the source database to HUAWEI CLOUD by performing steps provided inMigrating Application Servers to HUAWEI CLOUD. Alternatively, you can deploySAP HANA servers at HUAWEI CLOUD. For details, see SAP HANA User Guide.

Step 2 Configure asynchronous system replication from the source SAP HANA databaseto the target SAP HANA database. For details, see SAP HANA AdministrationGuide.

Step 3 Before the system switchover, check HANA System Replication to ensure that thedata replication status is normal, and then stop the source SAP application system.

Step 4 Run the SAP HANA takeover command on the target database to check thedatabase running status. For details, see SAP HANA Administration Guide.

Step 5 Start the target SAP application system on the cloud and ensure that theconnection between the application system and HANA database is normal.

Step 6 Check the system availability and service data integrity on the service side.

----End

4.3.6 Tests and DrillsAfter setting up the environment required for the migration, you can perform testson target system service functions and service migration drills.

Migration Drills

Use the designed service switchover plan to perform a drill to ensure that the planmeets the requirements. For details about the service switchover plan, see ServiceSwitchover Plan.

Service Tests

Check the target system on the cloud and perform complete verification on keyservice processes. Ensure that the system after the migration can meet servicerequirements.

4.3.7 Switchover and Go-LivePerform the official system migration according to the plan specified in themigration drill. You can switch over services of the development and test systemfirst, verify that the development and test system is running properly, and then cutover services of the production system.

SAPBest Practices



https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/676844172c2442f0bf6c8b080db05ae7.html

https://www.oracle.com/database/technologies/high-availability/dataguard.html

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-2017


https://www.ibm.com/support/knowledgecenter/en/SSTRGZ_11.4.0/com.ibm.swg.im.iis.db.repl.intro.doc/topics/iiyrqinfroadmap.html


https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/099caa1959ce4b3fa1144562fa09e163.html

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/099caa1959ce4b3fa1144562fa09e163.html

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/123f2c8579fd452da2e7debf7cc2bd93.html

4.4 Migrating from a Third-Party Cloud to HUAWEICLOUD

4.4.1 Scenario DescriptionIn this scenario, you migrate the SAP system that is deployed on a third-partycloud. The supported server OSs are listed in OSs Supported by Different Typesof ECSs. There is no restriction on the database. In addition, other cloud services,such as object storage service, can be involved in. After the migration to HUAWEICLOUD, the database, OS, and system architecture remain unchanged. Theinvolved cloud services of other cloud vendors will be changed to those ofHUAWEI CLOUD.

This scenario is similar to the previous one. However, there are some differences:

● You can easily adjust the network bandwidth between the third-party cloudplatform and HUAWEI CLOUD. The maximum bandwidth can be hundreds ofMbit/s.

● Generally, the system architecture does not need adjustment. If the on-premises system architecture is complex, you need to replan the deploymentarchitecture of the system on the cloud.

● Generally, an on-premises system contains only physical servers or VMs. Asystem on a third-party cloud may contain cloud service resources.

Figure 4-8 shows an example. You can use the same system architecture as thethird-party cloud to reduce migration complexity.

SAPBest Practices





Figure 4-8 Migrating from a third-party cloud


Deployment PlanTo deploy the system on HUAWEI CLOUD, keep the application architectureunchanged and replace third-party cloud services with HUAWEI CLOUD services.

For details about the deployment solution design, refer to section DeploymentPlan.

Networking PlanThe system networking on HUAWEI CLOUD is the same as that of the source end.The system connects to a third-party cloud through EIP and VPN or DirectConnect.

For details, see Networking Plan.

Security Design● For details, see Security Design. Find more information in the SAP Security

White Paper.● For details about permission management, see Service Account System

Design.

Migration PlanTable 4-9 lists the recommended migration solutions.

SAPBest Practices





Table 4-9 Migration solutions

Object Solution Description

Applicationservers

Server Migration ServiceNOTE

The source server must accessHUAWEI CLOUD SMS. Bind a publicIP address to the source server.

SMS supports online andincremental migration. Youcan migrate SAP applicationservers while the applicationsare running, and synchronizeincremental data severaltimes.Data transmission time =Actual data volume/Actualnetwork bandwidthTable 4-10 lists the estimatedtime for transmitting 1 TBdata. Estimate the timerequired for transmitting databased on the actual datavolume. If the data cannot betransmitted within theestimated time, increase thenetwork bandwidth.

Database ● You can migrate a non-production system databaseafter stop the databaseservice using SMS.

● You can use the databasebackup and restorationfunction or other nativedatabase tools to migrationthe production systemdatabase.

When using SMS, you need tostop the database servciebefore the migration toensure data consistency.The service interruptionduration of using nativedatabase tool is shorter thanthat of using the SMS. Fordetails about the estimatedinterruption duration, seesection Table 4-2.

Table 4-10 Theoretical time for transmitting 1 TB data

Network Bandwidth 2Mbit/s

10Mbit/s

50Mbit/s

100Mbit/s

Theoretical time (80% networkutilization rate)NOTE

Transmission time (days) = [Total capacity(KB)]/[Bandwidth (Mbit/s) x 125 xNetwork utilization rate x 60 (seconds) x60 (minutes) x 24 (hours)]

106days

13 days 60 hours 30hours

SAPBest Practices



Service Switchover PlanThe owner of the service switchover plan is the migration implementor. Thissection provides an example of the service switchover plan.


MigrationSolution


The applicationservers areredeployed onor migrated toHUAWEICLOUD byimportingimages. Thedatabase isrestored usingbackup data.

1. Redeploy andcommission theapplication servers onHUAWEI CLOUD.

2. Back up the entiresource database serverand upload full backupsto the target system torestore data to thetarget database.

3. Stop the sourcedatabase, upload theincremental ordifferential data andrequired log files toHUAWEI CLOUD, andrestore the backup datato the target database.

The service interruption duration= the incremental backupduration + the incrementalbackup transmission duration+ the incremental datarestoration duration

Use SMS tomigrate theapplicationservers, andthe databasereplicationfunction tosynchronizedatabase.

1. After the applicationservers are migrated toHUAWEI CLOUD usingSMS, use incrementalreplication tosynchronize the servers.

2. Configure synchronousreplication from the on-premises database tothe cloud database. Stopthe services on thesource end and performthe service takeover onthe cloud database.

Stop source end services onlyafter the last incrementalsynchronization is performedusing SMS.After the cloud database takesover the services, the serviceswitchover is complete.The service interruption durationis the database switchoverduration.

4.4.3 Preparing ResourcesFor details, see Preparing Resources.

SAPBest Practices



4.4.4 Migrating Application Servers to HUAWEI CLOUDPerform operations provided in Method 1: Using SMS to migrate the applicationservers. You can also use the method described in Method 2: Importing Images.

The procedure is the same as that described in Migrating Application Servers toHUAWEI CLOUD.

4.4.5 Migrating the Database to HUAWEI CLOUDThe migration method is the same as that of scenario 1. For details, see Migratingthe Database to HUAWEI CLOUD.

4.4.6 Tests and DrillsFor details, see Tests and Drills.

4.4.7 Switchover and Go-LiveFor details, see Switchover and Go-Live.

4.5 Migrating from IBM or HP Midrange Computers toHUAWEI CLOUD

4.5.1 Scenario DescriptionIn this scenario, you migrate the SAP system deployed on IBM or HP midrangecomputers. The OSs are not supported by HUAWEI CLOUD. After the migration,the OSs are changed to those supported by HUAWEI CLOUD, and the databaseremains unchanged.

You need to deployed application servers and the database servers of the systemon HUAWEI CLOUD. The target system is redeployed on HUAWEI CLOUD ECSs orBMSs. Use the export and import functions of R3load to migrate database data.You can also use some native database tools, such as Oracle GoldenGate.

Figure 4-9 shows an example. For details, see section Migrating from IBM or HPMidrange Computers to HUAWEI CLOUD.

SAPBest Practices



Figure 4-9 Migration from IBM midrange computers to HUAWEI CLOUD



For the deployment solution design, refer to section Deployment Plan.

Networking PlanA VPC is used on HUAWEI CLOUD, and subnets are created according to thenetworking best practices on HUAWEI CLOUD. On-premises IDC connects toHUAWEI CLOUD through EIP and VPN or Direct Connect.


Security DesignFor details, see Security Design. Find more information in the SAP SecurityWhite Paper.

For details about permission management, see Service Account System Design.

Migration SolutionTable 4-12 shows the recommended solutions.

SAPBest Practices






Object Migration Solution Description

Application servers Redeployment If the application serversrunning OSs that are notsupported by HUAWEICLOUD, you need to deploythe source system on theHUAWEI CLOUD.

Database ● System Copy option ofSWPM (R3load importand export functions)

● Heterogeneousdatabase migrationprovided by a nativedatabase tool, such asOracle GoldenGate andOracle XTTS offlinedatabase data Export/Import function

The R3load export andimport function is used in astandard SAP migrationsolution. If any problemoccurs during the migration,you can visit SAP officialwebsite to seek for SAPtechnical support. Whenusing R3load, you need toshut down the servers beforeexporting the data, and theservice interruption durationis long.If you requires shorterservice interruption period,use heterogeneousmigration provided by thedatabase. For example,Oracle GoldeGate supportsto reduce the downtime toalmost zero. For moreinformation, see OracleGoldeGate technicaldetails.

Service Switchover PlanTable 4-13 shows an example.

SAPBest Practices



https://www.oracle.com/middleware/technologies/goldengate.html




MigrationSolution


The applicationservers anddatabaseserver areredeployed onHUAWEICLOUD. Thedatabase ismigrated usingthe SWPMimport andexport function(R3load).

1. After the system isdeployed on HUAWEICLOUD, stop serviceson the source end anduse the SWPM toexport the sourcesystem.

2. Upload the exportedfiles to the destinationsystem through aprivate line, and thenimport the files to thedestination systemusing SWPM.

The downtime is long, and thesystem needs to be shut downfrom the beginning.The service interruption duration= Data exporting duration + Filetransferring duration+ Dataimporting duration

The applicationservers anddatabaseserver areredeployed onHUAWEICLOUD. TheOracledatabase ismigrated usingthe OracleGoldeGate.

1. After the system isdeployed on HUAWEICLOUD, use the OracleGoldeGate toconfigure datasynchronization fromthe source to thedestination.

2. Stop the services onthe source end andperform the servicetakeover on the clouddatabase.

After the cloud database takesover the services, the serviceswitchover is complete.The service interruption durationis the database switchoverduration.

SAPBest Practices



MigrationSolution


The applicationservers anddatabaseserver areredeployed onHUAWEICLOUD. TheOracledatabase ismigrated usingOracle XTTS.

1. After the system issuccessfully deployedon HUAWEI CLOUD,cross-platformtransportabletablespaces (XTTS)and multipleincremental backupsare used tosynchronize data withthe cloud.

2. After services on thesource end arestopped, perform thedata synchronization,and then the databaseon the cloud takesover the services. Thisgreatly shortens thedowntime.

After the cloud database takesover the services, the serviceswitchover is complete.The service interruption durationis the time of the last incrementalsynchronization of the database.


4.5.4 Migrating Application Servers to HUAWEI CLOUDYou need to redeploy the system on HUAWEI CLOUD because the OSs running onIBM Power midrange computers are not supported by HUAWEI CLOUD.

Redeploying the SystemDeploy the servers on HUAWEI CLOUD. Redeploy the system on HUAWEI CLOUD.For details, see SAP Deployment Guide, SAP HANA User Guide, and SAPNetWeaver User Guide.

4.5.5 Migrating the Database to HUAWEI CLOUDHeterogeneous migration may involve replication operations, such as data tablesplitting and ABAP code modification. These operations require SAP system anddatabase management experience. You may spend more time adjusting thesystem and planning the migration. Do not change the database type. Thefollowing solutions are available:

● Method 1: Use SAP System Copy that is a standard migration solutionprovided by SAP. If you have any questions during the migration, contact SAPtechnical support. For details, see Method 1: Using SAP System Copy(R3load).

SAPBest Practices







● Method 2: Use a database native tool. Different databases have their ownheterogeneous migration solutions, for example, offline data Export/Import.

Method 1: Using SAP System Copy (R3load)SAP System Copy is a standard migration solution supported by SAP's technicalpersonnel. It can migrate data from your database to the HANA database (SystemCopy - Target Database SAP HANA) and other databases (System Copy - TargetDatabases Other than SAP HANA).

When using System Copy, stop the services before you start the export. The serviceinterruption duration depends on the database size. Importing and exporting ofover 1 TB data takes a long time, which has a great impact on services. Figure4-10 shows the procedure.

Figure 4-10 System migration

The procedure is described as follows:

Step 1 On HUAWEI CLOUD, create the a subnet, configure security group policies, andbuild the target system, including the database and application servers.

Step 2 Stop the source system services. Run the SWPM tool on the source server and useSystem Copy to export data. For details, see SAP System Copy.

Step 3 Upload the exported data to the file system of the target system.

Step 4 Run the SWPM tool in the target system and use System Copy to import data.

Step 5 Verify the system availability and data integrity.

----End

Method 2: Using the native migration function of your database.Databases have their own heterogeneous migration solutions. For example, theOracle database has Oracle GoldenGate, and the DB2 has Q Replication, and theoffline data Export/Import function. However, heterogeneous migration requiresmore careful planning and design. Consultants who are familiar with databasemigration tools are needed for implementing the migration.

SAPBest Practices



https://help.sap.com/viewer/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-US/baf86558573d43faa20068ec39751efb.html

https://help.sap.com/viewer/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-US/baf86558573d43faa20068ec39751efb.html

https://help.sap.com/viewer/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-US/bf15a049b0044c79b19109023291fa67.html

https://help.sap.com/viewer/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-US/bf15a049b0044c79b19109023291fa67.html

https://help.sap.com/doc/saphelp_nwpi711/7.1.1/en-US/47/fe9dc92d204aa7e10000000a421937/content.htm?no_cache=true


https://www.ibm.com/support/knowledgecenter/zh/SSTRGZ_10.2.1/com.ibm.swg.im.iis.db.repl.intro.doc/topics/iiyrcintrsqr0.html



4.6 Migrating SAP Applications Running on a Non-HANA Database to HUAWEI CLOUD SAP HANA

4.6.1 Scenario DescriptionIn this scenario, you migrate the source SAP system deployed in the local datacenter. The database is a non-HANA database (such as Sybase, Oracle, and DB2).The target end is HUAWEI CLOUD SAP HANA system. The server OSs may change.

The project includes system migration, software upgrade, database migration, andOS change. Use the DMO of SAP SUM to upgrade and migrate the SAP system toHUAWEI CLOUD SAP HANA system. Alternatively, use the Classical Migration toSAP HANA solution. Use SUM to upgrade the system to a supported version, andthen use System Copy of SWPM to migrate the system onto the HANA database.

Figure 4-11 DMO Migration

SAPBest Practices







For the deployment solution design, refer to section Deployment Plan.

Networking PlanA VPC is used on HUAWEI CLOUD, and subnets are created according to thenetworking best practices on HUAWEI CLOUD. On-premises IDC connects toHUAWEI CLOUD through EIP and VPN or Direct Connect.


Security DesignFor details, see Security Design. Find more information in the SAP SecurityWhite Paper.

For details about permission management, see Service Account System Design.

Migration SolutionRedeploy the application servers and database server on HUAWEI CLOUD. Fordatabase migration, use the SAP solutions. Table 4-14 describes therecommended solutions.



Application servers ● Redeployment Redeployment onHUAWEI CLOUD

SAPBest Practices






Database ● DMO in SUM● Classic migration of SAP

HANA (only applicable toJava systems)

● SAP provides theDMO in SUM toupgrade and migratethe SAP system toHUAWEI CLOUD SAPHANA. For details, seeDatabase MigrationOption (DMO) ofSUM.

● Alternatively, use theClassical Migration toSAP HANA solution.Use SUM to upgradethe system to asupported version,and then use SystemCopy of SWPM tomigrate the systemonto the HANAdatabase. For details,see ClassicalMigration to SAPHANA.

Generally, data is transmitted over the network. The optimal network bandwidth ishigher than 50 Mbit/s.

Service Switchover Plan

The migration implementor is responsible for the service switchover plan. Table4-15 shows an example plan.


Migration Solution Switchover Plan Impact

Application serversare newly deployed,and databaseservers aremigrated usingDMO.

1. Deploy and commissionthe new system.

2. Stop source databaseservices and use DMO tomigrate data to the targetsystem.

The downtime relates tothe service data volumeand network bandwidth.The service interruptiontime of this plan is long.


SAPBest Practices









4.6.4 Migrating Application Servers to HUAWEI CLOUDYou need to redeploy SAP application servers on HUAWEI CLOUD.

Redeploying the SystemRedeploy the system on HUAWEI CLOUD. For details, see SAP Deployment Guide,SAP HANA User Guide, and SAP NetWeaver User Guide.

4.6.5 Migrating the Database to HUAWEI CLOUDSAP provides the DMO in SUM and typical SAP migration methods to help youmigrate data from non-HANA databases to the HANA database. If you are anexperienced SAP migration consultants, use these methods to migrate your SAPsystem to HUAWEI CLOUD.

For details, see the official SAP documents Classical Migration to SAP HANA andDatabase Migration Option (DMO) of SUM.



4.7 Appendix

4.7.1 Migration Solution DetailsTable 4-16 describes common SAP system migration methods.

SAPBest Practices








Table 4-16 Migration tools and methods

Tool/Method Description

Server MigrationService

SMS provides P2V and V2V migration services to help youmigrate applications and data from on-premises X86 physicalservers or VMs on private or public clouds to ECSs onHUAWEI CLOUD.For details about how to use SMS, see the Server MigrationService Quick GuideNOTE

HUAWEI CLOUD also provides the Server Migration Tool (SMT). TheServer Migration Service is the SMT provided as a service, but theSMT has more powerful functions. If the SMS cannot meet yourrequirements, contact HUAWEI CLOUD technical support.The differences between the SMS and SMT are as follows:● Supported OSs: SMT supports more types and versions. For those

supported by SMS, see Supported Source Server OSs.● Connections: For SMS, source servers need to access HUAWEI

CLOUD SMS server through the Internet. If a source server and atarget ECS are connected through Direct Connect or VPN, ensurethat the source server to be migrated can access the SMS.

Image Export/Import

If your servers can be converted into image files, and thetype and OS of the image files are listed in Formats and OSsSupported for External Image Files, you can create serverimage files as private images on HUAWEI CLOUD, and usethe images to quickly deploy new servers.For details, see Creating a Linux System Disk Image froman External Image File and Creating a Windows SystemDisk Image from an External Image File.

DatabaseBackup andRestoration

This method uses the database backup function to exportdata from the source system, transfer the backup files to thedestination system, and then use the database restorationfunction to restore the data.Proper use of the database backup and restoration featurereduces the migration downtime.

DatabaseSynchronizationand Replication

Database replication functions include HANA SystemReplication, Oracle Data Guard, Always On AvailabilityGroups (SQL Server), and DB2 Q Replication. They all havesimilar features that allow you to copy a database from onenode to another. If you require shorter downtime, usedatabase replication as the data migration tool.

SAP SystemCopy (R3load)

The System Copy in SAP Software Provisioning Manager(SWPM) can replicate the SAP system to a new systemthrough the Export/Import function. This document does notdescribe this tool in detail. However, this is a solution tomigrate the SAP system to HUAWEI CLOUD.You can visit SASP official website to find details aboutSystem Copy and System Copy and Migration.

SAPBest Practices














https://www.oracle.com/database/technologies/high-availability/dataguard.html



https://www.ibm.com/support/knowledgecenter/en/SSTRGZ_11.4.0/com.ibm.swg.im.iis.db.repl.intro.doc/topics/iiyrqinfroadmap.html

https://help.sap.com/saphelp_nwpi711/helpdata/en/47/fe9dc92d204aa7e10000000a421937/content.htm?no_cache=true

https://wiki.scn.sap.com/wiki/display/SL/System+Copy+and+Migration

Tool/Method Description

DMO Data Migration Option (DMO) is integrated in SAP SoftwareUpdate Manager (SUM), which upgrades SAP systems andmigrate SAP databases. This document does not describe thistool in detail. However, this is a solution to migrate an SAPsystem to HUAWEI CLOUD.For details, see Database Migration Option for SUM andDatabase Migration Option of SUM

Classicmigration toSAP HANA

This solution uses a series of processes and tools includingheterogeneous System Copy to migrate data from a databaseto the HANA database. This document does not describe thissolution in detail. However, you can use this solution tomigrate the SAP system to HUAWEI CLOUD.For details about the solution, see Classical Migration toSAP HANA.

Object StorageMigrationService

OMS is an online data migration service that helps userseasily and smoothly migrate object storage data from otherpublic clouds to HUAWEI CLOUD.For details about how to use OMS, see the Object StorageMigration Service Quick Start.

Data ExpressService

DES is a massive data transmission solution. It allowstransmitting a large amount of data using Teleport devices ordisks (with external USB interfaces, SATA interfaces, or SASinterfaces) to HUAWEI CLOUD. DES helps to address issuesfacing massive data transmission such as high network costsand long transmission time.For details about how to use DES, see Data Express ServiceQuick Start.

SAPBest Practices



https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=395285937




https://support.huaweicloud.com/intl/en-us/qs-oms/oms_01_0010.html

https://support.huaweicloud.com/intl/en-us/qs-oms/oms_01_0010.html

https://support.huaweicloud.com/intl/en-us/qs-des/des_01_0080.html

https://support.huaweicloud.com/intl/en-us/qs-des/des_01_0080.html

A Change History

Description Released On

This issue is the third official release, which incorporates thefollowing change:Added the best practices of migrating the SAP system toHUAWEI CLOUD.

2020-07-06

This issue is the second official release, which incorporates thefollowing change:Added the best practices of uploading SAP backups data to theOBS bucket.

2019-07-12

This issue is the first official release. 2019-05-24

SAPBest Practices A Change History
