Configuring disaster recovery for a cloud based application

1. A computer implemented method for enabling disaster recovery for a first instance of a cloud-based application deployed at a first cloud platform landscape, the method comprising:

determining that a second instance of the cloud-based application is deployed at a second cloud platform landscape;

replicating, at a second database at the second cloud platform landscape, at least a portion of data from a first database at the first cloud platform landscape, the data from the first database being associated with the first instance of the cloud-based application;

configuring a domain name system (DNS) service to include a custom domain of the cloud-based application, a primary universal resource locator (URL) for the first instance of the cloud-based application, and a secondary URL for the second instance of the cloud-based application, the custom domain of the cloud-based application being mapped by the DNS service to the secondary URL instead of to the primary URL in the event of a failure at the first cloud platform landscape; and

performing one or more tests to determine a compliance of the enabled disaster recovery with respect to a recovery point objective (RPO) and/or a recovery time objective (RTO), the performing of the one or more tests comprising:

simulating a failure at the first cloud platform landscape; and

performing a traffic switch by at least configuring the DNS service to map the custom domain of the cloud-based application to the secondary URL of the second instance of the cloud-based application instead of to the primary URL of the first instance of the cloud-based application, the mapping of the custom domain of the cloud-based application to the secondary URL causing requests for the custom domain of the cloud-based application to be routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

2. The computer-implemented method of claim 1 , wherein the deploying of the second instance of the cloud-based application and the replicating of the data from the first database at the second database generate a fully operational copy of the cloud-based application at the second cloud platform landscape.

3. The computer-implemented method of claim 1 , wherein the traffic switch comprises a partial traffic switch during which requests for the custom domain of the cloud-based application originating from one or more specific internet protocol (IP) addresses are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

4. The computer-implemented method of claim 1 , wherein the traffic switch comprises a full traffic switch during which all requests for the custom domain of the cloud-based application are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

5. The computer-implemented method of claim 1 , further comprising:

applying, to the second instance of the cloud-based application, one or more configurations that are the same as at least some of a plurality of configurations applied at the first instance of the cloud-based application.

6. The computer-implemented method of claim 5 , wherein the one or more configurations include the custom domain for the cloud-based application, permissions, subscriptions, and/or destinations.

7. The computer-implemented method of claim 1 , further comprising:

receiving, from a client, a first ticket requesting enablement of disaster recovery for the first instance of the cloud-based application deployed at the first cloud platform landscape; and

responding to the receiving of the first ticket by at least generating a second ticket requesting an installation of the second database and/or a configuration of the first database for replication.

8. The computer-implemented method of claim 7 , wherein the replicating of at least the portion of the data from the first database at the first cloud platform landscape includes requesting a transfer of quotas from the first cloud platform landscape to the second cloud platform landscape, and wherein the quotas include an allocation of resources amongst the first instance of the cloud-based application, the second instance of the cloud-based application, the first database, the second database, and the custom domain of the cloud-based application.

9. A system for enabling disaster recovery for a first instance of a cloud-based application deployed at a first cloud platform landscape, the system comprising:

at least one processor; and

at least one memory including program code which when executed by the at least one processor provides operations comprising:

determining that a second instance of the cloud-based application is deployed at a second cloud platform landscape;

replicating, at a second database at the second cloud platform landscape, at least a portion of data from a first database at the first cloud platform landscape, the data from the first database being associated with the first instance of the cloud-based application;

configuring a domain name system (DNS) service to include a custom domain of the cloud-based application, a primary universal resource locator (URL) for the first instance of the cloud-based application, and a secondary URL for the second instance of the cloud-based application, the custom domain of the cloud-based application being mapped by the DNS service to the secondary URL instead of to the primary URL in the event of a failure at the first cloud platform landscape; and

performing one or more tests to determine a compliance of the enabled disaster recovery with respect to a recovery point objective (RPO) and/or a recovery time objective (RTO), the performing of the one or more tests comprising:

simulating a failure at the first cloud platform landscape; and

performing a traffic switch by at least configuring the DNS service to map the custom domain of the cloud-based application to the secondary URL of the second instance of the cloud-based application instead of to the primary URL of the first instance of the cloud-based application, the mapping of the custom domain of the cloud-based application to the secondary URL causing requests for the custom domain of the cloud-based application to be routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

10. The system of claim 9 , wherein the deploying of the second instance of the cloud-based application and the replicating of the data from the first database at the second database generate a fully operational copy of the cloud-based application at the second cloud platform landscape.

11. The system of claim 9 , wherein the traffic switch comprises a partial traffic switch during which requests for the custom domain of the cloud-based application originating from one or more specific internet protocol (IP) addresses are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

12. The system of claim 9 , wherein the traffic switch comprises a full traffic switch during which all requests for the custom domain of the cloud-based application are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

13. The system of claim 9 , further comprising:

applying, to the second instance of the cloud-based application, one or more configurations that are the same as at least some of a plurality of configurations applied at the first instance of the cloud-based application, the one or more configurations including the custom domain for the cloud-based application, permissions, subscriptions, and/or destinations.

14. The system of claim 9 , further comprising:

receiving, from a client, a first ticket requesting enablement of disaster recovery for the first instance of the cloud-based application deployed at the first cloud platform landscape; and

responding to the receiving of the first ticket by at least generating a second ticket requesting an installation of the second database and/or a configuration of the first database for replication.

15. The system of claim 9 , wherein the replicating of at least the portion of the data from the first database at the first cloud platform landscape includes requesting a transfer of quotas from the first cloud platform landscape to the second cloud platform landscape, and wherein the quotas include an allocation of resources amongst the first instance of the cloud-based application, the second instance of the cloud-based application, the first database, the second database, and the custom domain of the cloud-based application.

16. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising:

determining that a second instance of the cloud-based application is deployed at a second cloud platform landscape;

replicating, at a second database at the second cloud platform landscape, at least a portion of data from a first database at the first cloud platform landscape, the data from the first database being associated with the first instance of the cloud-based application;

configuring a domain name system (DNS) service to include a custom domain of the cloud-based application, a primary universal resource locator (URL) for the first instance of the cloud-based application, and a secondary URL for the second instance of the cloud-based application, the custom domain of the cloud-based application being mapped by the DNS service to the secondary URL instead of to the primary URL in the event of a failure at the first cloud platform landscape; and

performing one or more tests to determine a compliance of the enabled disaster recovery with respect to a recovery point objective (RPO) and/or a recovery time objective (RTO), the performing of the one or more tests comprising:

simulating a failure at the first cloud platform landscape; and

performing a traffic switch by at least configuring the DNS service to map the custom domain of the cloud-based application to the secondary URL of the second instance of the cloud-based application instead of to the primary URL of the first instance of the cloud-based application, the mapping of the custom domain of the cloud-based application to the secondary URL causing requests for the custom domain of the cloud-based application to be routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

17. The computer-readable medium of claim 16 , wherein the traffic switch comprises a partial traffic switch during which requests for the custom domain of the cloud-based application originating from one or more specific internet protocol (IP) addresses are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

18. The computer-readable medium of claim 16 , wherein the traffic switch comprises a full traffic switch during which all requests for the custom domain of the cloud-based application are routed to the second instance of the cloud-based application instead of to the first instance of the cloud-based application.

19. The computer-readable medium of claim 16 , further comprising:

receiving, from a client, a first ticket requesting enablement of disaster recovery for the first instance of the cloud-based application deployed at the first cloud platform landscape; and

responding to the receiving of the first ticket by at least generating a second ticket requesting an installation of the second database and/or a configuration of the first database for replication.

20. The computer-readable medium of claim 16 , wherein the replicating of at least the portion of the data from the first database at the first cloud platform landscape includes requesting a transfer of quotas from the first cloud platform landscape to the second cloud platform landscape, and wherein the quotas include an allocation of resources amongst the first instance of the cloud-based application, the second instance of the cloud-based application, the first database, the second database, and the custom domain of the cloud-based application.