Subscribe Us

Header Ads

Disaster recovery for SAP systems on Google Cloud

Current market conditions create an even greater need for SAP customers to take advantage of cloud agility and innovation. To help SAP customers simplify their cloud journeys, Google Cloud offers the first cloud initiative, the Cloud Acceleration Program (CAP), empowering customers with solutions, guidance, and offers from our cloud partner. Clients gain access to expert skills for migration, implementation optimization, and more profound skills in the areas of analytics and machine learning. 


Google Cloud offers CAP participants transparent financial incentives for customers to avoid infrastructure costs for SAP Cloud migrations and to ensure that no duplicate costs are incurred during migration. Disaster recovery (DR) is all too often an afterthought in business continuity strategies.An effective DR plan focuses on the technology systems supporting critical business functions; it involves a set of policies and procedures for recovering and/or continuing vital technology infrastructure and systems following any kind of disaster. Essentially, in an effective DR plan, technology systems will transition from the primary site to the DR site.One of the biggest challenges companies face when creating DR plans is deciding between self-managed, on-prem hardware or cloud solutions.


What matters to your disaster recovery strategy


There is no one-size-fits-all approach to disaster recovery. Strategies differ from application to application according to structure, function, and objective. The most successful DR plans consider the entire technology network and the company’s end-goals.

A good disaster recovery strategy always begins with a business impact analysis that defines two key metrics:

  • Recovery Time Objective (RTO): How long you can afford to have your business offline.

  • Recovery Point Objective (RPO): How much data loss you can sustain before you run into compliance issues due to financial losses.

 

Identifying the best strategy, architecture, and toolset for your business begins with defining your Recovery Time Objective (RTO), which is how long you can afford to have your business offline, and your Recovery Point Objective (RPO), which is how much data loss you can sustain before you run into compliance issues due to financial losses. The smaller your RTO and RPO goals are, the more costly the application will be. Every organization, regardless of its situation and goals, also needs to determine and factor in the costs to the business while the system is offline, and the costs for data loss and re-creation.


After you’ve defined the RPOs and RTOs that will guide your DR design, consider capacity planning and automation as part of your larger business continuity plan. Begin by making sure there’s enough capacity available to stand up a copy of a development system, so that you can control how to develop and transport any emergency SAP changes to the production system. Although initiating a DR plan is usually a manual task, recovery and startup should be automated to ensure fast and error-free recovery. With Google Cloud, infrastructure is considered as code—we believe that repeatable tasks like provisioning, configuration, and deployment should be automated.










Ramesh Suraparaju

Partner Technical Lead for SAP Strategy & Architecture, Google Cloud


Post a Comment

0 Comments