Automated multi-region application recovery
AssigneeAmazon Technologies, Inc.
InventorsJohn Paul Formento, Danilo Ayar Duran, Christopher L. Cmolik, Shanshan Li, Mikhail Ivanovich Golovnykh
Life of this patent
Estimating the term…
Abstract
A recovery orchestrator system receives a recovery plan, which may be used for a hosted-computing environment. The recovery plan includes multiple steps. The recovery orchestrator system receives monitoring metrics. The recovery orchestrator system executes the recovery plan based on the monitoring metrics. The recovery orchestrator system executes steps from the recovery plan in multiple fault domains. The recovery orchestrator system monitors the status of the execution of the recovery plan and provides the status update to a computing device.
Claims20
A computer-implemented method comprising:
- receiving a recovery plan for a server based software application associated with a first region, the recovery plan comprising (i) a first recovery configuration and (ii) a plurality of steps;
- receiving a first alarm indication associated with the recovery plan, wherein the first alarm indication is for a first monitoring metric associated with the first region;
- executing the recovery plan, wherein executing the recovery plan further comprises:
- causing, based on a first step from the plurality of steps and the first recovery configuration, a first recovery action to occur with respect to a first server associated with at least one of the first region or a second region;
- receiving an output associated with the first recovery action;
- determining, based on the first recovery configuration, that the output fails to satisfy a threshold;
- and
- causing a second recovery action to occur with respect to the first server;
- receiving a status update regarding execution of the recovery plan and the second region;
- and
- causing presentation, via a graphical user interface, of an indicator of the status update.
A system comprising:
- A non-transitory data storage medium to store specific computer-executable instructions;
- and a computer hardware processor in communication with the non-transitory data storage medium, wherein the specific computer-executable instructions configure the computer hardware processor to at least:
- receive a recovery plan for a server based software application associated with a first fault domain, the recovery plan comprising a recovery configuration and a plurality of steps;
- receive an alarm indication associated with the recovery plan, wherein the alarm indication is for a monitoring metric;
- execute the recovery plan, wherein to execute the recovery plan, the specific computer-executable instructions configure the computer hardware processor to at least:
- cause, based on a first step from the plurality of steps and the recovery configuration, a first recovery action to occur with respect to a first server associated with at least one of the first fault domain or a second fault domain;
- receive an output associated with the first recovery action;
- determine, based on the recovery configuration, that the output fails to satisfy a threshold;
- and cause a second recovery action to occur with respect to the first server;
- receive a status update regarding execution of the recovery plan and the second fault domain;
- and cause presentation, via a graphical user interface, of an indicator of the status update.
A system comprising:
- a non-transitory data storage medium to store specific computer-executable instructions;
- and a computer hardware processor in communication with the non-transitory data storage medium, wherein the specific computer-executable instructions configure the computer hardware processor to at least:
- receive a recovery plan for a server-based software application associated with a first fault domain, the recovery plan comprising a first recovery configuration and a plurality of steps;
- execute the recovery plan, wherein to execute the recovery plan, the specific computer-executable instructions configure the computer hardware processor to at least:
- cause, based on a first step from the plurality of steps and the first recovery configuration, a first recovery action to occur with respect to a first server associated with a particular fault domain;
- receive an output associated with the first recovery action;
- determine, based on the first recovery configuration, that the output fails to satisfy a threshold;
- and cause a second recovery action to occur with respect to the first server;
- receive a status update regarding execution of the recovery plan and a second fault domain;
- and provide the status update to a computing device.
Dependencies are inferred from the claim text.