![]() ![]() The RTO/RPO are typically higher than with other DR option in which data is replicated directly from the database (like using HANA System Replication or CloudEndure). ![]() The RTO depends on the database size and change rate. The RPO in this solution depends on source system log backup frequency, change rate and amount of time taken to copy the backed up objects to the DR region. In this blog, we will describe the scenario using AWS Backint agent. The data and log backup for SAP HANA database in AWS can be performed using native database tools and the AWS Backint Agent, or 3rd party tools. To bring in the latest data into the databases, backups can be restored with point-in-time recovery. In the DR region, for testing or real DR events, SAP systems can be built on-demand using the AMIs copied from the primary region. File system data (like transport directory and sap mount directory) is created and replicated using AWS Backup.AMIs ( Amazon Machine image) of application servers and databases are created and replicated to DR AWS region using AWS Backup.The Production system backups (data and log) are replicated to the DR region using Amazon S3 CRR.Use AWS Backint agent for SAP HANA or other database native tools, to take the DB backup and store it in Amazon S3.The following approach is used to backup and copy the production system to the selected AWS region for DR: Data is not replicated directly from databases. Setup is simplified using AWS services and features including AWS Backup, AWS CloudFormation and Amazon S3 CRR.įor this option, there are no Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Block Storage (EBS) volumes provisioned in the DR AWS region during normal operations. In this solution, the disaster recovery setup uses the backups of the primary SAP systems to build the DR environment. Solution Overview: Passive DR for SAP Applications in AWS This solution is suitable for customers who wish to lower the cost of their DR solution and are able to accept higher RTO and RPO SLAs, when compared to data replication based solutions. In this blog, we are going to show how to build a low-cost DR solution using a passive DR approach for SAP HANA based applications. With AWS, the on-demand capabilities of Amazon Elastic Compute Cloud (EC2) provides customers with more options for their DR solution compared with a traditional on-premises setup. The document High Availability and Disaster Recovery Options for SAP HANA on AWS describes all options for DR setup for SAP HANA databases on AWS, such as HANA System Replication (HSR) with data preload on or off, and backup and restore with Amazon Simple Storage Service (S3) Cross-Region Replication (CRR).Ĭustomers can also use CloudEndure Disaster Recovery the block-level replication tool from AWS,, for the DR setup. ![]() This guide provides a set of architecture guidelines, strategies, and decisions for SAP customers and partners who have a requirement for deploying SAP NetWeaver-based systems with a highly available and reliable configuration on AWS To make it easy for you, SAP Specialist Solutions Architects have come up with Architecture Guidance for Availability and Reliability of SAP on AWS. For customers running their SAP workloads on AWS, some of the key considerations for the design of the DR solution are single or multiple AWS Region or Availability Zones, Service Level Agreements such as Recovery Point Objective (RPO) and Recovery Time Objective (RTO), and cost. A Disaster Recovery (DR) solution is an important aspect of SAP system design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |