HA and DR Guide - HUAWEI CLOUD...HA and DR Scenarios 4.1 Concepts Related to HA and Disaster...

SAP HANA

HA and DR Guide

Issue 01

Date 2018-05-23

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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 and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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, guarantees orrepresentations 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.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2018-05-23) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document.................................................................................................................. 1

2 Advantages of Cloud-Based HA.................................................................................................2

3 Introduction to Public Cloud Services...................................................................................... 3

4 HA and DR Scenarios................................................................................................................... 54.1 Concepts Related to HA and Disaster Recovery............................................................................................................ 54.2 Automatic Recovery of SAP HANA ECSs....................................................................................................................64.3 SAP HANA Cluster HA (Host Auto-Failover).............................................................................................................. 74.4 SAP HANA Single-Node HA (System Replication + Preload on + SUSE HAE).........................................................84.5 SAP HANA DR (System Replication).........................................................................................................................124.6 SAP HANA HA and DR.............................................................................................................................................. 154.7 SAP HANA HA and DR Scenario Comparison...........................................................................................................17

5 SAP HANA HA Planning (Distance and RTT)..................................................................... 20

6 Related Documents..................................................................................................................... 21

A Change History........................................................................................................................... 22

SAP HANAHA and DR Guide Contents


ii

1 About This Document

This document describes how to configure the SAP system on the public cloud to protectapplications from a single point of failure (SPOF). It also explores how to migrate localfeatures to the public cloud platform and improve SAP installation technologies to maximizethe reliability of SAP deployment.

Note that this document cannot replace standard SAP installation documents. For moreinformation about SAP deployment on the public cloud and public cloud technicalcomponents, see the operation guides of SAP and Huawei.

This document describes how to set up and configure the system replication for SAP HANAdatabases, but does not guide how to configure the high availability (HA) for databases indetails, for example, using SQL Server Mirroring or Oracle Data Guard. For details, see HAinstallation and configuration guides of the corresponding database.

This document does not cover all service reasons and criteria for ensuring HA on the publiccloud.

We assume that you have the following knowledge or skills:

l Knowledge about SAP system administratorsl Knowledge about operating systemsl HA principles of different databasesl Knowledge about SAP HANA database administratorsl HA principles of the public cloud.

SAP HANAHA and DR Guide 1 About This Document


1

2 Advantages of Cloud-Based HA

Compared with traditional HA, cloud-based HA has the following advantages:

l Agility: HA systems can be deployed on the cloud quickly and effectively. However, torealize traditional HA, you need to purchase servers and hardware, complete hardwareplanning, and require skilled engineers for construction.

l Flexible expansion: Cloud-based HA systems can be dynamically expanded as requiredto meet system performance requirements. However, the traditional HA architecture isfixed and not easy to be dynamically expanded.

l O&M: Tenants do not need to maintain the cloud-based HA. It is maintained by thecloud service providers. Traditional HA requires a local O&M team.

l Reliability: Cloud-HA can be deployed in different regions based on the tenant'srequirements to achieve cross-region HA and ensure system security.

l Cost: Compared with traditional HA, cloud-based HA is cost-effective.

SAP HANAHA and DR Guide 2 Advantages of Cloud-Based HA


2

3 Introduction to Public Cloud Services

Table 3-1 Public cloud services

Service Description

VirtualPrivateCloud(VPC)

VPC enables you to create private, isolated virtual networks. You canconfigure IP address segments, subnets, and security groups, assign EIPs, andallocate bandwidth in a VPC.NOTE

The same SAP HANA system is deployed in the same VPC.

ImageManagementService(IMS)

IMS provides comprehensive image management capabilities. You can createa private image or use an existing public image to create ECSs in batches.NOTE

Currently, the public cloud platform supports the following SAP public images:

l SUSE Linux Enterprise Server 11 SP4 for SAP



ElasticCloudServer(ECS)

ECS provides scalable, on-demand cloud servers for secure, flexible, andefficient application environments, ensuring reliable, uninterrupted services.NOTE

Huawei public cloud provides HANA ECSs for running SAP HANA. For moreinformation, see the SAP HANA User Guide.

ElasticVolumeService(EVS)

EVS provides persistent block storage for services such as ECS and BareMetal Server (BMS). With advanced data redundancy and cache accelerationcapabilities, EVS offers high availability and durability with an extremely lowlatency. You need to perform operations such as initializing an EVS disk andcreating a file system.NOTE

For details about the EVS specifications in the SAP HANA scenario, see the SAP HANAUser Guide.

SAP HANAHA and DR Guide 3 Introduction to Public Cloud Services


3

Service Description

(Optional)ScalableFileService(SFS)

SFS provides completely hosted sharable file storage for ECSs. Compatiblewith the Network File System protocol, SFS is expandable to petabytes,features high performance, and seamlessly handles data-intensive andbandwidth-intensive applications.NOTE

The shared and backup volumes can be provided by SFS. For details, see the SAP HANAUser Guide.

VolumeBackupService(VBS)

Volume Backup Service (VBS) provides online backup for EVS disks andallows data restoration from backups, offering protection against virus attacksand software and hardware faults.

ObjectStorageService(OBS)

OBS is a stable, secure, efficient, and easy-to-use cloud storage service. WithRepresentational State Transfer Application Programming Interfaces (RESTAPIs), OBS is able to store unstructured data of any amount and form at99.999999999% reliability (11 nines).

SAP HANAHA and DR Guide 3 Introduction to Public Cloud Services


4

4 HA and DR Scenarios

4.1 Concepts Related to HA and Disaster Recovery

4.2 Automatic Recovery of SAP HANA ECSs

4.3 SAP HANA Cluster HA (Host Auto-Failover)

4.4 SAP HANA Single-Node HA (System Replication + Preload on + SUSE HAE)

4.5 SAP HANA DR (System Replication)

4.6 SAP HANA HA and DR

4.7 SAP HANA HA and DR Scenario Comparison

4.1 Concepts Related to HA and Disaster Recoveryl Availability

Availability is used to measure the running continuity of the system. It is expressed inpercentage and is inversely proportional to the downtime. For example, if the availability of asystem is 99.9%, its annual downtime must be less than 0.1% or 9 hours.

l Downtime

Downtime is the result of service interruption, which may be caused by system upgrade oraccident faults. A fault may be a device, software, or network fault, or a major disaster, suchas a fire. A power failure or construction accident may cause the failure of the entire datacenter.

l HA

HA is ensured by a set of business technologies, engineering practices, and design principles.System continuity can be achieved by eliminating a single point of failure. HA minimizes theservice loss by restoring the system immediately after it is interrupted.

l DR

Disaster recovery is performed after a data center is interrupted or onsite faults are beingrectified. Data backups prepared in event of disasters are more complex and expensive.

l Data synchronization mode

SAP HANAHA and DR Guide 4 HA and DR Scenarios


5

The SAP HANA System Replication supports synchronization (full synchronization,memory synchronization, and synchronization) and asynchronization modes. In the HAautomatic switchover scenario, the synchronization mode is recommended to ensure thatno data is lost during the data switchover (RPO = 0).– Full synchronization: After the secondary system receives the synchronization

data and stores it in disks, the secondary system sends confirmation information tothe primary system and then the primary system submits logs of this operation. Ifthe secondary system fails to receive the synchronization data due to a fault, theprimary system waits until the secondary system recovers.

– Synchronization: After the secondary system receives the synchronization data andstores it in disks, the secondary system sends confirmation information to theprimary system and then the primary system submits logs of this operation. If thesecondary system fails to receive synchronization data due to a fault and theprimary system fails to synchronize data to the secondary system, the primarysystem continues its service.

– Memory synchronization: After the secondary system receives the logs (memory)and sends a confirmation message to the primary system, the primary systemsubmits logs of this operation. If the secondary system fails to receivesynchronization data due to a fault and the primary system fails to synchronize datato the secondary system, the primary system continues its service.

– Asynchronization: The primary system sends the synchronization data to thesecondary system and submits logs without waiting for the response from thesecondary system. The fault of the secondary system does not affect the primarysystem running services.

l Data preload mode– The preload option is ON.

Data is stored in the memory.The switchover is fast (RTO).

– The preload option is OFF.The memory usage is low and the memory is used by other systems, such as non-production systems.The switchover duration is long.Before the switchover, activate the preload mode.

4.2 Automatic Recovery of SAP HANA ECSs

Scenarios

The public cloud provides automatic recovery by default to restart ECSs through coldmigration, ensuring high availability and dynamic ECS migration.

l You can enable automatic recovery during or after ECS creation.l An ECS can be automatically recovered only if the host on which it is deployed becomes

faulty. This function does not take effect if the fault is caused by the ECS itself.l An ECS can be automatically recovered only once within 12 hours if the host on which it

is deployed becomes faulty.l ECS automatic recovery may fail in the following scenarios:



6

– Many hosts in the system are faulty.

– The host to which the ECS services are migrated does not have sufficient temporarycapacity.

Advantages

The public cloud provides the automatic recovery capability for ECSs with easy configurationand no extra cost.

NOTICEIt is recommended to use the automatic recovery capability of ECSs in the SAP non-production environment.

Deployment Plan

Figure 4-1 shows the deployment plan.

Figure 4-1 Automatic recovery of SAP HANA ECSs

4.3 SAP HANA Cluster HA (Host Auto-Failover)

Scenarios

The public cloud supports the SAP HANA cluster mode, which has the HA capability ensuredby the configured standby nodes and the automatic switchover function (Host Auto-Failover).

l Standby nodes are configured for the SAP HANA cluster to implement automaticswitchover. When any node in the cluster fails, the SAP HANA automatically triggers aswitchover. The switchover does not cause data loss (RPO = 0).



7

l A single standby node can only recover the fault of a single node at one time. It isrecommended to configure multiple standby nodes for a SPA HANA cluster with overeight nodes.

l The public cloud supports anti-affinity deployment of the SAP HANA cluster. ECSs inthe same SAP HANA cluster are deployed on different physical servers to ensure HA.

l Currently, the public cloud supports a maximum of eight nodes (7 worker nodes and 1standby node) in an SAP HANA cluster.

Advantages

The SAP HANA cluster HA is easy to be deployed and cost-effective based on its HAmechanism and Public cloud capabilities.

NOTICEBefore enabling the HA automatic switchover function of an SAP HANA cluster, disable theautomatic recovery function of the ECSs in the cluster.

Deployment Plan


Figure 4-2 SAP HANA cluster HA (Host Auto-Failover)

4.4 SAP HANA Single-Node HA (System Replication +Preload on + SUSE HAE)

SAP HANA HA within an AZ

Scenarios



8

The public cloud supports SAP HANA HA. In this scenario, deploy the primary andsecondary SAP HANA systems in the same AZ and configure the System Replicationfunction of SAP HANA and the SUSE High-Availability Extension (HAE) function to enableautomatic switchover and realize HA. This applies to the scenario where a single SAP HANAnode is deployed.

l The System Replication function of SAP HANA provides data replication.l Enabling the Preload function of System Replication can preload data to the memory of

the secondary system to reduce the switchover time and lower Recovery Time Objective(RTO).

l Configuring SUSE HAE allows automatic system switchover. The public cloud providesscripts for automatic HAE configuration. For details, see the SAP HANA User Guide(Single Node Deployment).

l The HA mechanism automatically monitors the health status of the primary SAP HANAsystem (SAP HANA process, OS, and data replication). When the primary system fails,failover and virtual IP address floating are automatically triggered to achieve HA of theHANA system.

Advantages

Based on the public cloud capabilities, SAP HANA System Replication, and SUSE HAE,SAP HANA provides reliable assurance for your core services.

NOTICEIn the production environment, you are advised to use the SAP HANA HA automaticswitchover solution to reduce the RTO. Before using this solution, you need to disable theautomatic recovery function of ECSs.

Deployment Plan




9

Figure 4-3 SAP HANA HA within an AZ

Cross-AZ SAP HANA HAScenarios

Deploy secondary SAP HANA systems in different AZs.

l The System Replication function of SAP HANA provides data replication.l Enabling the Preload function of System Replication can preload data to the memory of

the secondary system to reduce the switchover time and lower Recovery Time Objective(RTO).

l Configuring SUSE HAE allows automatic system switchover. The public cloud providesscripts for automatic HAE configuration. For details, see the SAP HANA User Guide(Single Node Deployment).

l The HA mechanism automatically monitors the health status of the AZ where theprimary system (SAP HANA process, OS, and data replication) is located. When the AZwhere the primary system is located fails, failover and virtual IP address floating areautomatically triggered to achieve HA of the HANA system.

Advantages

Based on the public cloud capabilities, SAP HANA System Replication, and SUSE HAE,cross-AZ SAP HANA deployment provides reliable assurance for your core services.

Deployment Plan




10

Figure 4-4 Cross-AZ SAP HANA HA

Scenario 1: SAP HANA HA (System Replication + Preload off + DEV/QAS)Scenarios

When the preload function is disabled, the secondary SAP HANA system can be used todeploy non-production systems.

l After the preload function of System Replication is disabled, only a few resources (10%)need to be reserved for the secondary system for receiving synchronization data from theprimary system. In addition, non-production systems can be deployed on the secondarysystem.

l According to the SAP best practice, non-production systems on the secondary systemhave to use additional storage resources to avoid the impact on the production systemafter the switchover of the secondary system.

l Before the switchover, disable non-production systems on the secondary system toensure sufficient resources on the secondary system and then manually trigger theswitchover.

Advantages

The secondary SAP HANA system can be fully utilized to reduce the overall cost based onpublic cloud capabilities and SAP HANA HA mechanism.

NOTICEIn the production environment, you are advised to use the SAP HANA single-node HAautomatic switchover solution to reduce the RTO. Before using this solution, you need todisable the HA configuration function of ECSs.

Deployment Plan




11

Figure 4-5 SAP HANA HA within an AZ (System Replication + Preload off + DEV/QAS)

4.5 SAP HANA DR (System Replication)

ScenariosThe public cloud supports SAP HANA DR. Cross-AZ SAP HANA DR can be achieved bydeploying primary and secondary SAP HANA systems in different AZs and using the SystemReplication function of SAP HANA to implement data replication.

l Based on the network status between AZs, you can select the synchronization orasynchronization mode to meet different RPO requirements.

l When the preload function is disabled, the secondary system can be used to deploy non-production systems. For details, see Scenario 1.

AdvantagesA VPC can be deployed across AZs and allows the primary and secondary SAP HANAsystems to be deployed in the same subnet. No extra network configuration is required.

Deployment PlanFigure 4-6 shows the deployment plan.



12

Figure 4-6 SAP HANA DR (System Replication)

Scenario 1: SAP HANA DR (System Replication + Preload off + DEV/QAS)The public cloud supports SAP HANA DR. Cross-AZ SAP HANA DR can be achieved bydeploying primary and secondary SAP HANA systems in different AZs and using SystemReplication to implement data replication. The secondary system can be used to deploy non-production systems when the preload function is disabled.

l After the preload function of System Replication is disabled, only a few resources (10%)need to be reserved for the secondary system for receiving synchronization data from theprimary system. In addition, non-production systems can be deployed on the secondarysystem.

l According to the SAP best practice, non-production systems on the secondary systemhave to use additional storage resources to avoid the impact on the production systemafter the switchover of the secondary system.

l Before the switchover, disable non-production systems on the secondary system toensure sufficient resources on the secondary system and then manually trigger theswitchover.

Advantages

A VPC can be deployed across AZs and allows the primary and secondary SAP HANAsystems to be deployed in the same subnet. No extra network configuration is required. Thesecondary system can be fully utilized to reduce the overall cost.

Deployment Plan




13

Figure 4-7 SAP HANA DR (System Replication + Preload off + DEV/QAS)

Scenario 2: Cloud DR System DeploymentThe public cloud supports deploying the SAP HANA DR system on the cloud to synchronizedata with the system of the customer's local data center.

l Use the VPN service to connect customer data centers to public cloud resources. Deploythe SAP HANA DR system on the cloud.

l Synchronize data between on-cloud and on-premises SAP HANA systems using SystemReplication in the asynchronization mode.

l Manually switch to the on-cloud SAP HANA system when a fault occurs in the customerdata center system.

Advantages

Public cloud resources allow the complete DR between on-cloud and on-premises systems.

Deployment Plan




14

Figure 4-8 DR system deployment on cloud

4.6 SAP HANA HA and DR

Scenario 1: Single-AZ SAP HANA HA (System Replication in theSynchronization Mode + Preload on + SUSE HAE) and Cross-AZ SAP HANADR (System Replication in the Asynchronization Mode + Preload on)

Scenarios

Deploy the primary and secondary SAP HANA systems in the same AZ and configure theSystem Replication function of SAP HANA and the SUSE HAE function to enable automaticswitchover and realize HA. In the other AZ, deploy a secondary SAP HANA system andconfigure Multitier System Replication function to implement cross-AZ DR. This applies tothe scenario where a single SAP HANA node is deployed.

Deployment Plan

Figure 4-9 shows the deployment plan of SAP HANA HA within an AZ and SAP HANA DRacross AZs.



15

Figure 4-9 Single-AZ SAP HANA HA and cross-AZ SAP HANA DR

Scenario 2: Single-AZ SAP HANA HA (System Replication in theSynchronization Mode + Preload on + SUSE HAE) and Cross-Region SAPHANA DR (System Replication in the Asynchronization Mode + Preload on)

Scenarios

Deploy the primary and secondary SAP HANA systems in the same AZ and configure theSystem Replication function of SAP HANA and the SUSE HAE function to enable automaticswitchover and realize HA. In the other region, deploy a secondary SAP HANA system andconfigure Multitier System Replication function to implement cross-region DR. This appliesto the scenario where a single SAP HANA node is deployed.

Deployment Plan

Figure 4-10 shows the deployment plan of SAP HANA HA within an AZ and SAP HANADR across regions.

Figure 4-10 Single-AZ SAP HANA HA and cross-region SAP HANA DR



16

Scenario 3: Cross-AZ SAP HANA HA (System Replication in theSynchronization Mode + Preload on + SUSE HAE) and Cross-Region SAPHANA DR (System Replication in the Asynchronization Mode + Preload on)

Scenarios

Deploy the primary and secondary SAP HANA systems in different AZs of the same regionand configure the System Replication function of SAP HANA and the SUSE HAE function toenable automatic switchover and realize HA across AZs. In the other region, deploy asecondary SAP HANA system and configure Multitier System Replication function toimplement cross-region DR. This applies to the scenario where a single SAP HANA node isdeployed.

Deployment Plan

Figure 4-11 shows the deployment plan of SAP HANA HA across AZs and SAP HANA DRacross regions.

Figure 4-11 Cross-AZ SAP HANA HA and cross-region SAP HANA DR

4.7 SAP HANA HA and DR Scenario Comparison

Scenario Comparison

Table 4-1 Scenario summary and comparison

Scenario Deployment ApplicationScope

Applicable SAP Scenario

Automatic Recovery ofSAP HANA ECSs

Localdeploymentand HA

Singlenode/cluster

Non-production scenario(development, test, training, andsandbox)

SAP HANA Cluster HA(Host Auto-Failover)


Cluster Production scenario



17

Scenario Deployment ApplicationScope

Applicable SAP Scenario

SAP HANA HA(System Replication +Preload on+ SUSEHAE)


Singlenode/cluster

Production scenario

SAP HANA HA(System Replication +Preload off)


Singlenode/cluster

Production and non-productionscenarios

SAP HANA DR(System Replication)

Cross-AZdeploymentand DR

Singlenode/cluster

Production and non-productionscenarios

On-Cloud and On-Premises SAP HANADR(System Replication)

Cross-regiondeploymentand DR

Singlenode/cluster

Production scenario

Comparison Between Cost and Reliability

Table 4-2 Comparison between cost and reliability

Scenario AdditionalCost

RPO

RTO

Remarks

Automatic Recovery ofSAP HANA ECSs

None N/A

High RPO is uncertain.RTO is high. Restart the ECSusing cold migration.

SAP HANA Cluster HA(Host Auto-Failover)

LowN workernodes and 1standby node

0 Low RPO = 0RTO is in the minute level. Theswitchover between worker andstandby nodes is automatic.

SAP HANA HA(System Replication +Preload on+ SUSE HAE)

MediumN + N

0 Low RPO = 0. The synchronizationmode is used for data replication.RTO is in the minute level. Theswitchover between primary andsecondary systems is automatic.



18

Scenario AdditionalCost

RPO

RTO

Remarks

SAP HANA HA(System Replication +Preload off)

MediumN + N

≈ 0 Medium

RPO varies depending on thedata replication mode andnetwork status.RTO is high. (Decide theswitchover policy. Manuallyperform the switchover andpreload the data to the memory.)

SAP HANA DR(System Replication)

Medium tohighN + 2N

≈ 0 Medium

RPO varies depending on thedata replication mode andnetwork status.RTO is high. (Decide theswitchover policy. Manuallyperform the switchover andpreload the data to the memory.)

On-Cloud and On-Premises SAP HANADR(System Replication)

MediumN + N

> 0 Medium

RPO > zero. Generally, theasynchronization mode is used.RTO is high. (Decide theswitchover policy. Manuallyperform the switchover andpreload the data to the memory.)



19

5 SAP HANA HA Planning (Distance and

RTT)

Typical round-trip time (RTT):

l The recommended network bandwidth between data centers is 10 Gbit/s (shared).l The RTT (ms) between data centers is determined based on the feasibility and rationality.

In addition, there may be a deviation.

Table 5-1 RTT

Item Assumed Distance (km) Target RTT

Host Auto Failover (localdisk)

0 < 0.1 ms

Synchronous SystemReplication

10-50 0.5 ms-1 ms

Asynchronous SystemReplication

> 100 10+ ms

Synchronous StorageReplication

1050

0.5 ms1 ms

Asynchronous StorageReplication

> 100 10+ ms

SAP HANAHA and DR Guide 5 SAP HANA HA Planning (Distance and RTT)


20

6 Related Documents

To ensure that the SAP system installed on the public cloud platform in compliance with theSAP support requirements, you are advised to refer to the standard SAP documents and notesin Table 6-1 and Table 6-2.

Table 6-1 SAP documents

Name Link

SAP HANA Administrator Guide SAP HANA Administration Guide

Setting Up SAP HANA System Replication Setting Up SAP HANA SystemReplication

Configuring SAP HANA SystemReplication

Configuring SAP HANA SystemReplication

Monitoring SAP HANA System Replication Monitoring SAP HANA SystemReplication

SAP HANA Multitier System Replication SAP HANA Multitier System Replication

How to Perform System Replication forSAP HANA

How to Perform System Replication forSAP HANA

SAP HANA System Replication Details SAP HANA System Replication Details

Table 6-2 SAP notes

Description Note Link

FAQ 1999880 FAQ: SAP HANA System Replication

Configurationdescription

2369981 Required configuration steps for authenticationwith HANA System Replication

Network configurationdescription

1876398 Network configuration for System Replication inSAP HANA

SAP HANAHA and DR Guide 6 Related Documents


21

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

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/c7ecfd46d4124d42b868bad468175c30.html

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/c7ecfd46d4124d42b868bad468175c30.html

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

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

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

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

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/ca6f4c62c45b4c85a109c7faf62881fc.html

https://archive.sap.com/documents/docs/DOC-47702

https://archive.sap.com/documents/docs/DOC-47702

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

https://launchpad.support.sap.com/#/solutions/r/?type=note&route=notes&pos=0&p=%7B%22note%22%3A%221999880%22%7D





A Change History

Description Date

This issue is the third official release, which incorporates the followingchanges:Added the cross-region DR scenario.Added the cross-AZ HA scenario.

2018-05-23

This issue is the second official release, which incorporates the followingchange:Deleted the content of the Volume Backup Service (VBS).

2018-02-25

This issue is the first official release. 2018-02-01

SAP HANAHA and DR Guide A Change History


22

Date post:	26-Apr-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times