Method for controlling changes of replication directions in a multi-site disaster recovery environment for high available application

Patent metadata

Field	Value
Publication number	US-9953293-B2
Application number	US-201213527692-A
Country	US
Kind code	B2
Filing date	Jun 20, 2012
Priority date	Apr 30, 2010
Publication date	Apr 24, 2018
Grant date	Apr 24, 2018

Abstract

A running of an application resource of a first site of at least two sites is stopped from accessing a storage device of the first site. A running of a replication resource is brought to a stop. The replication resource is configured to control a replication of data between the storage device on the first site on which data from the running application resource on the first site are stored to the storage device on the second site. A replication request is submitted to the automation engine for changing a replication direction to run from the second site to the first site. The application resource is started on the second site only after changing the replication direction to start from the storage device on the second site instead of from the storage device of the first site.

First claim

What is claimed is:

1. A method for processing a disaster recovery setup using a policy-based automation engine controlling at least two sites of a computing environment, the method comprising:
running an application resource of a first site of the at least two sites to access a storage device of the first site, each of the at least two sites comprising a server with an application resource and a storage device for storing data of the application resource, wherein the application resource on a second site of the at least two sites is online;
running a replication resource, the replication resource being central to and an intermediary between the first site and the second site and configured to control a replication of data between the storage device on the first site on which data from the running application resource on the first site are stored to the storage device on the second site;
submitting a replication request to the automation engine for changing a replication direction to run from the second site to the first site, while the application resource and the replication resource on the first site are online;
detecting a mismatch between the requested replication direction and an existing replication direction;
in response to the detected mismatch, propagating offline input/output (I/O) requests to the application resource on the first site and the application resource on the second site respectively based on a highest priority of the offline I/O requests, and subsequently stopping the running of the application resource on the first site;
stopping the running of the replication resource on the first site, after the stopping of the running of the application resource on the first site;
changing the replication direction to run from the second site to the first site; and
after changing the replication direction, removing the propagated offline I/O requests and starting the application resource in order of relationship, and running the replication resource on the second site; wherein the relationship is defined as one of a set of rules in the replication resource, and the replication resource on the second site is only commenced if the relationship of the replication direction between the first site and the second site is specified within the set of rules.

2. The method according to claim 1 , wherein the automation engine is goal-driven by prioritizing requests on the application resources and the replication resource such that the resource replication request for changing the replication direction is given the highest priority.

3. The method according to claim 1 , wherein the automation engine is event-driven by receiving events from controlled resources at a change of status to determine a final state of the application resources and the replication resource.

4. The method according to claim 1 , wherein the application resource is defined with corresponding state of availability and relationship rules for constraints between the application resources of each site.

5. The method according to claim 1 , wherein the replication resource is defined by an availability state and a replication direction state, the availability state and the replication direction state both being updated within the automation engine.

6. A computer system for a disaster recovery setup comprising:
at least two sites each including a server, the server comprising a processing device for running an application resource and a storage device in communication with the processing device for storing data of the application resource, each of the application resources being defined with corresponding state of availability and relationship rules for constraints between the application resources, the computer system being controlled by a policy-based automation engine; and
wherein the processing device performs controlling, by a replication resource being central to and an intermediary between a first site and a second site, a replication of data between the storage device of the first site on which data from a running application resource of the first site are stored to the storage device on the second site, the replication resource being defined by an availability state and a replication direction state, both the availability state and the replication direction state being updated within the automation engine and being defined by relationship rules between the replication resource and the application resources controlled by the automation engine to perform a change of replication direction after bringing to a stop the running application resource of the first site accessing the storage device of the first site, then bringing to a stop the running replication resource, executing a submission to the automation engine of a replication request for changing the replication direction from one site to another site by the automation engine taking into account the relationship rules, detecting a mismatch between the requested replication direction and an existing replication direction, in response to the detected mismatch, propagating offline input/output (I/O) requests to the application resource on the first site and the application resource on the second site respectively based on a highest priority of the offline I/O requests, and subsequently stopping the running of the application resource on the first site, stopping the running of the replication resource on the first site, after the stopping of the running of the application resource on the first site, changing replication direction to start from a storage device of the second site towards the storage device on the first site, and subsequent to the changing of the replication direction, removing the propagated offline I/O requests and starting the application resource in order of relationship, and the replication resource on the second site; wherein the relationship is defined as one of a set of rules in the replication resource, and the replication resource on the second site is only commenced if the relationship of the replication direction between the first site and the second site is specified within the set of rules.

7. The computer system according to claim 6 , wherein the automation engine is goal-driven by prioritizing requests on the application resources and the replication resource such that the resource replication request for changing the replication direction is given the highest priority.

8. The computer system according to claim 6 , wherein the automation engine is event-driven by receiving events from the resources at a change of status to determine final state of the application resources and the replication resource.

9. The computer system according to claim 6 , further comprising a processor in communication with each site and configured to run the automation engine.

10. The computer system according to claim 6 , wherein the first site comprises a production site.

11. The computer system according to claim 6 , wherein the second site comprises a backup site.

12. The computer system according to claim 6 , wherein each application resource further comprises a data processing server.

13. A computer program product for processing a disaster recovery setup using a policy-based automation engine controlling at least two sites of a computer system, the computer program product including a non-transitory computer readable storage medium comprising:
computer code for stopping a running application resource of a first site of the at least two sites from accessing a storage device of the first site, each of the at least two sites comprising a server with an application resource and a storage device for storing data of the application resou

Assignees

• Benke Oliver
• Jostmeyer Bernd
• Lumpp Thomas
• Mueller Markus
• Reitz Martin
• Schaeberle Wolfgang
• Schueppen Walter
• Schwertle Isabell
• IBM

Inventors

• Benke Oliver
• Jostmeyer Bernd
• Lumpp Thomas
• Mueller Markus
• Reitz Martin
• Schaeberle Wolfgang
• Schueppen Walter
• Schwertle Isabell

Classifications

• G06F11/2023

  Failover techniques · CPC title

• G06F11/2038

  with a single idle spare processing component · CPC title

• G06Q10/10 Primary

  Office automation; Time management · CPC title

• G06F11/2097

  maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title