Multilevel disaster recovery

• US 10,261,872 B2
• Filed: 05/31/2017
• Issued: 04/16/2019
• Est. Priority Date: 05/31/2017
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Boshev, Stoyan, Petev, Petio, Walter, Thomas, Vatkov, Bogdan, Dobtchev, Hristo, Arnaudov, Borislav
• Primary Examiner(s): Chu, Gabriel
• Application Number:
  US15/610,609
• Publication Number:
  US 20180349238A1
• Time in Patent Office: 685 Days
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

Account data comprising metadata for primary application instances running at a primary active cloud environment instance (ACEI) is stored. Application data associated with the primary application instances is stored at primary databases (DBs). The account and application data are transferred to secondary DBs at a secondary ACEI. The secondary ACEI may be a backup instance to substitute services provided by the primary ACEI in case of unavailability. For example, the location where the primary ACEI is hosted may be affected by a disaster. To failover a primary data center hosting the primary ACEI, a database takeover to the secondary DBs is performed. The secondary ACEI is configured correspondingly to the primary ACEI based on the transferred account data. Secondary application instances corresponding to the primary application instances are started at the secondary ACEI. Requests directed to the primary application instances are redirected to the secondary application instances.

Claims

1. A computer implemented method to recover data upon a disaster, the method comprising:

receiving account data of an account at a secondary active cloud environment instance (ACEI) hosted at a secondary data center, wherein the account data comprises metadata for one or more primary application instances of a plurality of primary application instances running at a primary ACEI hosted at a primary data center, wherein the account is associated with the primary ACEI and the secondary ACEI;

receiving, at one or more secondary databases (DBs) of the secondary ACEI, application data associated with the one or more primary application instances from the primary ACEI;

receiving a request at the secondary data center to failover the primary data center;

performing a database (DB) takeover to the one or more secondary DBs;

starting, in the secondary ACEI, one or more secondary application instances corresponding to the one or more primary application instances, wherein the one or more secondary application instances are configured based on the account data, and wherein the one or more secondary application instances are associated with the one or more secondary DBs; and

receiving a redirected request to a primary application instance of the one or more primary application instances at a corresponding application instance of the one or more secondary application instances.

2. The method of claim 1, further comprising:

upon performing the DB takeover, configuring transfer of the account data from the secondary ACEI to a tertiary ACEI hosted at a tertiary data center, wherein the account data comprises metadata for the one or more secondary application instances; and

configuring replication of the one or more secondary DBs to one or more tertiary DBs associated with the tertiary ACEI, wherein the one or more tertiary DBs are associated with one or more tertiary application instances running at the tertiary ACEI.

3. The method of claim 1, wherein the application data is associated with implemented functionality at the one or more primary application instances and with a cloud service provided at the primary ACEI, wherein the cloud service is consumed by at least one of the one or more primary application instances, and wherein the account data defines at least one relationship between the cloud service and the at least one of the one or more primary application instances.

4. The method of claim 1, further comprising:

at the primary ACEI;

polling a repository of the primary ACEI for changes in the account data, wherein the account data is persisted at the repository;

when the account data includes changes, exporting a portion of the account data to a replication service of the primary ACEI, wherein the portion of the account data includes the changes;

encrypting the exported portion of the account data in a message;

sending the message to a messaging service of the primary ACEI; and

transferring the message from the messaging service of the primary ACEI to a messaging service of a secondary ACEI.

5. The method of claim 1, further comprising:

polling a messaging service of the secondary ACE for messages comprising the account data, wherein the account data is exported from a repository of the primary ACEI;

when a message is in the messaging service of the secondary ACEI, reading the message;

deleting the message from the messaging service of the secondary ACEI;

decrypting the message to extract the account data; and

importing the account data to a repository of the secondary ACEI.

6. The method of claim 1, further comprising:

determining premium disaster recovery (DR) is enabled for the one or more primary application instances; and

triggering replication of one or more primary DBs associated with the one or more primary application instances to the one or more secondary DBs, wherein the one or more primary application instances persist the application data in the one or more primary DBs.

7. The method of claim 6, further comprising:

upon receiving the request to failover the primary data center, determining at least one primary application instance associated with the account of the plurality of primary application instances, wherein a standard DR is enabled for the at least one primary application instance;

terminating network traffic to the at least one primary application instance running at the primary ACEI;

activating a standby cloud environment instance (CEI) in the secondary data center, wherein the standby CEI is pre-configured in accordance with a configuration of the primary ACEI;

restoring one or more databases associated with one or more services at the standby CEI, based on a backup copy of one or more primary databases associated with one or more primary services, wherein the backup copy is stored at the second data center; and

restoring at least one database associated with at least one application instance at the standby CEI based on a backup copy of at least one primary database associated with the at least one primary application instance, wherein the at least one application instance corresponds to the at least one primary application instance.

8. A computer system to prevent data loss, the system comprising:

a processor;

a memory in association with the processor storing instructions related to;

instantiating a primary disaster recovery (DR) interface at a primary active cloud environment instance (ACEI) to enable replication of account data and one or more primary application databases associated with one or more primary application instances running in the primary ACEI, wherein the primary DR interface is configured to;

export the account data associated with a plurality of premium DR accounts defined in the primary ACEI to a messaging service of the primary ACEI; and

trigger replication of the one or more primary application databases to one or more secondary application databases in a secondary ACEI, wherein the primary ACEI runs in a primary data center, and wherein the one or more primary application instances are associated with the plurality of premium DR accounts; and

instantiating a secondary DR interface at the secondary ACEI to enable failover of the primary data center, wherein the secondary DR interface is configured to;

import the account data from a messaging service of the secondary ACEI, wherein the secondary ACEI runs in a secondary data center; and

trigger a database takeover to the one or more secondary application databases, wherein the one or more secondary application databases are associated with one or more secondary application instances corresponding to the one or more primary application instances.

9. The system of claim 8 further storing instructions related to:

instantiating a standby DR interface in a standby cloud environment instance (CEI) of the secondary data center, wherein the standby DR interface is configured to;

restore, from a backup copy created at the primary data center and transported to the secondary data center, account data associated with a plurality of standard DR accounts defined in the primary ACEI;

restore application data from one or more primary application databases of one or more primary application instances associated with the plurality of standard DR accounts; and

redirect network traffic to the standby CEI.

10. The system of claim 8, wherein the primary DR interface is further configured to:

change a parameter in metadata of an account of the plurality of premium DR accounts to define the account as premium DR account, wherein the account data comprises the metadata of the account;

send a request to a primary replication service of the primary ACEI to export the account data from a repository of the primary ACEI to the messaging service of the primary ACEI; and

send a request to a database admin service of the primary ACEI to enable replication of the one or more primary application databases.

11. The system of claim 10, wherein the primary replication service is further operable to;

poll the repository of the primary ACEI for changes in the account data; and

encrypt the account data to a message and sends the message to the messaging service of the primary ACEI.

12. The system of claim 8, wherein secondary DR interface is further configured to:

send a request to a database admin service of the secondary ACEI to stop replication of the one or more primary application databases to the one or more secondary application;

send a request to the database admin service of the secondary ACEI to perform the database takeover from the one or more primary application databases to the one or more secondary application databases;

start the one or more secondary application instances in the secondary ACEI, wherein the one or more secondary application instances are associated with the one or more secondary application databases and with the plurality of premium DR accounts; and

send a request to a global traffic management (GTM) service of the secondary ACEI to redirect network traffic from the primary data center to the secondary data center.

13. The system of claim 12, wherein the secondary replication service is further operable to:

upon receiving a request from the secondary DR interface, read one or more messages comprising the account data from the messaging service of the secondary ACEI;

decrypt the one or more messages to extract the account data; and

import the account data in a repository of the secondary ACEI.

14. A non-transitory computer readable medium storing instructions which when executed by at least processor cause a computer system to perform operations comprising:

receive account data of an account at a secondary active cloud environment instance (ACEI) hosted at a secondary data center, wherein the account data comprises metadata for one or more primary application instances of a plurality of primary application instances running at a primary ACEI hosted at a primary data center, wherein the account is associated with the primary ACEI and the secondary ACEI;

receive, at one or more secondary databases (DBs) of the secondary ACEI, application data associated with the one or more primary application instances from the primary ACEI;

receive a request at the secondary data center to failover the primary data center;

perform a database (DB) takeover to the one or more secondary DBs;

start, in the secondary ACEI, one or more secondary application instances corresponding to the one or more primary application instances, wherein the one or more secondary application instances are configured based on the account data, and wherein the one or more secondary application instances are associated with the one or more secondary DBs; and

receive a redirected request to a primary application instance of the one or more primary application instances at a corresponding application instance of the one or more secondary application instances.

15. The computer readable medium of claim 14 further storing instructions to;

upon performing the DB takeover, configure transfer of the account data from the secondary ACEI to a tertiary ACEI hosted at a tertiary data center, wherein the account data comprises metadata for the one or more secondary application instances; and

configure replication of the one or more secondary DBs to one or more tertiary DBs associated with the tertiary ACEI, wherein the one or more tertiary DBs are associated with one or more tertiary application instances running at the tertiary ACEI.

16. The computer readable medium of claim 14, wherein the application data is associated with implemented functionality at the one or more primary application instances and with a cloud service provided at the primary ACEI, wherein the cloud service is consumed by at least one of the one or more primary application instances, and wherein the account data defines at least one relationship between the cloud service and the at least one of the one or more primary application instances.

17. The computer readable medium of claim 14 further storing instructions to:

at the primary ACEI;

poll a repository of the primary ACEI for changes in the account data, wherein the account data is persisted at the repository;

when the account data includes changes, export a portion of the account data to a replication service of the primary ACEI, wherein the portion of the account data includes the changes;

encrypt the exported portion of the account data in a message;

send the message to a messaging service of the primary ACEI; and

transfer the message from the messaging service of the primary ACEI to a messaging service of a secondary ACEI.

18. The computer readable medium of claim 14 further storing instructions to:

poll a messaging service of the secondary ACEI for messages comprising the account data, wherein the account data is exported from a repository of the primary ACEI;

when a message is in the messaging service of the secondary ACEI, read the message;

delete the message from the messaging service of the secondary ACEI;

decrypt the message to extract the account data; and

import the account data to a repository of the secondary ACEI.

19. The computer readable medium of claim 14 further storing instructions to:

determine premium disaster recovery (DR) is enabled for the one or more primary application instances; and

trigger replication of one or more primary DBs associated with the one or more primary application instances to the one or more secondary DBs, wherein the one or more primary application instances persist the application data in the one or more primary DBs.

20. The computer readable medium of claim 19 further storing instructions to:

upon receiving the request to failover the primary data center, determine at least one primary application instance associated with the account of the plurality of primary application instances, wherein a standard DR is enabled for the at least one primary application instance;

terminate network traffic to the at least one primary application instance running at the primary ACEI;

activate a standby cloud environment instance (CEI) in the secondary data center, wherein the standby CEI is pre-configured in accordance with a configuration of the primary ACEI;

restore one or more databases associated with one or more services at the standby CEI, based on a backup copy of one or more primary databases associated with one or more primary services, wherein the backup copy is stored at the second data center; and

restore at least one database associated with at least one application instance at the standby CEI based on a backup copy of at least one primary database associated with the at least one primary application instance, wherein the at least one application instance corresponds to the at least one primary application instance.