SAP Disaster Recovery


What is Disaster Recovery?

Disaster recovery is an organization’s method of regaining access to and functionality for its IT infrastructure following disruptive events, such as major equipment failure, natural disaster, cyberattack, or pandemic. It relies on the backup of data and computer processing capabilities at a remote location not affected by the disaster. In a disaster, the organization can restore data and computing functions to continue operations.

Disaster recovery focuses on IT systems supporting critical business functions instead of business continuity, which involves keeping all essential aspects of a business functioning despite significant disruptive events. Priorities and recovery time objectives should be developed during the business impact analysis. Technology recovery strategies should be designed to restore hardware, applications, and data in time to meet the business recovery needs.

What is Disaster Recovery?

Disaster recovery is an organization’s method of regaining access to and functionality for its IT infrastructure following disruptive events, such as major equipment failure, natural disaster, cyberattack, or pandemic. It relies on the backup of data and computer processing capabilities at a remote location not affected by the disaster. In a disaster, the organization can restore data and computing functions to continue operations.

Disaster recovery focuses on IT systems supporting critical business functions instead of business continuity, which involves keeping all essential aspects of a business functioning despite significant disruptive events. Priorities and recovery time objectives should be developed during the business impact analysis. Technology recovery strategies should be designed to restore hardware, applications, and data in time to meet the business recovery needs.

What is SAP Disaster Recovery?

SAP offers standard and enhanced disaster recovery service for SAP Business Technology Platform (SAP BTP), Neo environment. Data backups are stored at a disaster recovery site and contain all data stored in the SAP BTP’s data management and document services. According to SAP, any data not stored in these services cannot be recovered.

The SAP BTP Enhanced Disaster Recovery service provides asynchronous data replication to a remote disaster recovery region to improve the time for recovery. The service requires hardware setup and covers production applications running on SAP BTP in disaster recovery-enabled subaccounts. The setup requires configuration steps that the organization and the dedicated SAP team must perform in advance.

Further Resources for SAPinsiders:

High Availability & Disaster Recovery Protection for SAP and SAP S/4HANA in Azure. Check out this webinar and hear from Microsoft and SIOS experts about the four fundamental options for protecting SAP S/4HANA in the cloud and best practices for disaster recovery of SAP HANA systems.

Considerations for Disaster Recovery and Automated Failover Clusters for SAP HANA Infrastructures. In this SAPinsider Q&A, SUSE’s Peter Schinagl, Technical Architect, and Markus Gürtler, Technical Alliance Manager, answer questions regarding disaster recovery scenarios for SAP HANA infrastructure, automation solutions for failover, and system replication.

A Step-by-Step Configuration Guide for Disaster Recovery. In this article, Muhammad Abdul Jamil, SAP Basis Administrator at the Orient Group of Companies, provides a detailed step-by-step guide on setting up a standby database of the SAP production server for disaster recovery.

Other vendors offering SAP disaster recovery services: AWS, Commvault, Google Cloud, NetApp, and Syntax.

6425 results

  1. Extending and Modifying SAP Standard with Business Add-Ins and the New Modification Assistant

    Up until now, Customer Exits and Modifications were the only development techniques available for extending and modifying standard SAP applications. Release 4 introduces two new techniques – Business Add-Ins and the Modification Assistant. Business Add-Ins are predefined exit points in a source that allow developers to either insert their own logic during implementation or simply…...…
  2. Real-Time, Outbound Interfaces to Non-R/3 Systems Made Simple with Change Pointers, Message Control, and Workflow

    Developers often struggle with custom ABAP/4 code or database logging to devise ways to track changes to data and then to trigger output of that changed data across outbound interfaces to non-R/3 systems. The onus of creating a way to track changes as they occur rests squarely on the shoulders of these developers, but it…...…
  3. Size Does Matter – Strategies for Successful SAP R/3 Capacity Planning

    Capacity planning is not a trivial task. Choose your hardware vendor and equipment carefully, and upgrades will pose few problems. Choose the wrong vendor-model combination, and you will be forced to make extensive changes to your hardware and operating system that will entail extensive planning and testing, and could ultimately require all new equipment. So…...…
  4. An Introduction to SAP’s New and Improved Frontend Printing

    Dr. Stefan Fuchs describes a new spool access method that allows the transfer of print data from the application server to the current location of the SAPGUI. From there the data is sent to the local spooler on the user’s particular frontend. That new spool access method — method “F” — is what SAP calls…...…
  5. Achieving a More Manageable and Reliable R/3 Spool Server Landscape Using Release 4 Output Classifications, Logical Servers, and Alternate Servers

    Three new output features give rise to a more manageable, more reliable R/3 spool server environment — classifications, logical servers, and alternate servers. With Release 4, classifications of output devices and spool servers (along the lines of production, high-volume, desktop, and test printing) are now made possible within R/3 itself. This helps you ensure that…...…
  6. ABAP Programming – An Integrated Overview

    With Release 4.0 and the debut of ABAP Objects, SAP is replacing the classical distinction between reporting and transaction programming with an integrated view, recognizing the simple fact that all application logic is programmed in ABAP and that the application can communicate with the user via screens and with the database via a common interface…....…
  7. A Beginner’s Guide to Accessing BAPIs with the SAP DCOM Connector

    This article will introduce you to the basic design principles behind SAP DCOM Connector (SDC), show you how to build BAPI-enabled applications with SDC in Visual Basic, and discuss some advanced concepts for SDC-based applications. In order to keep things simple, we will assume that our applications are built without MTS. So I will not…...…
  8. Extending SAP Business Workflow with Web Forms

    Web forms are the means by which developers can create applications that enable users to start workflows and execute work items from the comfort of a Web browser. A Web form is a simple, intuitive interface, which is made up of a relatively short list of fields and a “Submit” button. This interface obviates the…...…
  9. Lessons in Logon Load Balancing

    In large SAP R/3 environments that require multiple application instances, you can achieve intelligent, automated distribution of workload across multiple application instances, with minimal impact to end users, through logon groups. This article explains how logon groups work and how to use them to establish a logon load balancing strategy that can improve system performance,…...…
  10. Leveraging the R/3 Warehouse Management Structure with the MM-MOB and WM-LSR Interfaces

    /Project ManagementIntegrating the R/3 Warehouse Management (WM) module with mobile data entry devices and external warehouse management systems is made possible by two interfaces — Mobile Data Entry (MM-MOB), which enables mobile entry and transfer of data to and from SAP, and Warehouse Control Unit (WM-LSR), which enables the sending and receiving of information between…...…