Optimizing the number and type of database backups to achieve a given recovery time objective (RTO)
US-9430335-B2 · Aug 30, 2016 · US
US2016162378A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016162378-A1 |
| Application number | US-201615043127-A |
| Country | US |
| Kind code | A1 |
| Filing date | Feb 12, 2016 |
| Priority date | Sep 23, 2013 |
| Publication date | Jun 9, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method for recovery comprising: under the control of one or more computer systems configured with executable instructions, causing, in response to a detected failure event in a first data region, failover to a failover data region by coordinating a selected set of one or more virtual machine computing resources based at least in part on dependencies among the selected set of one or more virtual machine computing resources, the failover to a failover data region corresponding to a recovery plan comprising: a recovery time objective, a recovery point objective, a selection of one or more virtual machine computing resources hosted by one or more services of a computing resource service provider in a first data region, the virtual machine computing resources configured for instantiating at least one virtual machine, and a failover data region. 2 . The computer-implemented method of claim 1 , wherein the recovery time objective defines a duration of time for the one or more virtual machine computing resources to be restored as a result of the detected failure event. 3 . The computer-implemented method of claim 1 , wherein the recovery point objective defines a maximum amount of time in which customer data may be lost due to the detected failure event. 4 . The computer-implemented method of claim 1 , wherein the one or more virtual machine computing resources includes at least one of the following: virtual machine instances, databases, data archives or logical data containers. 5 . The computer-implemented method of claim 1 , wherein: the first data region comprises one or more data centers comprising one or more systems configured to permit the computing resource service provider to host the one or more virtual machine computing resources; and the failure event occurs when a threshold of failures of the one or more data centers has been reached. 6 . The computer-implemented method of claim 1 , wherein the failover to the failover data region occurs as a result of the failure event being detected. 7 . The computer-implemented method of claim 1 , wherein causing the selected one or more virtual machine computing resources to be reproduced includes transmitting one or more executable instructions to one or more services provided by the computing resource service provider, the one or more executable instructions causing the one or more services to reproduce the one or more virtual machine computing resources and update the one or more virtual machine computing resources over the amount of time. 8 . The computer-implemented method of claim 1 , wherein the one or more computer systems are in a third data region, different from the first data region and the failover data region. 9 . A computer system, comprising: a system that implements a recovery plan by at least causing, in response to a detected failure event, failover to a failover data region by coordinating a selected set of one or more virtual machine computing resources based at least in part on a recovery plan comprising: one or more recovery performance parameters; a selection of one or more or more virtual machine computing resources hosted by one or more services of a computing resource service provider in a first data region, the virtual machine computing resources configured for instantiating at least one virtual machine; dependencies among the selected one or more virtual machine computing resources; a failover data region; and the selected one or more virtual machine computing resources being redundantly maintained based at least in part on the dependencies among the selected one or more virtual machine computing resources to enable failover to the failover data region in compliance with the recovery performance parameters in response to a detected failure event. 10 . The computer system of claim 9 , wherein the recovery performance parameters includes a recovery time objective and a recovery point objective. 11 . The computer system of claim 10 , wherein the recovery time objective defines a duration of time for the one or more virtual machine computing resources to be restored as a result of the failure event. 12 . The computer system of claim 10 , wherein the recovery point objective defines a maximum amount of time in which customer data may be lost due to the detected failure event. 13 . The computer system of claim 9 , wherein the first data region and the failover data region each comprise one or more data processing facilities of the computing resource service provider. 14 . The computer system of claim 9 , wherein the failure event occurs when one or more performance metrics for the one or more services fail to satisfy a threshold, the threshold corresponding to minimum performance requirements for the one or more services. 15 . The computer system of claim 9 , wherein the selected one or more virtual machine computing resources are redundantly maintained by transmitting one or more executable instructions to the one or more services causing the one or more services to reproduce and update the selected one or more virtual machine computing resources based at least in part on the recovery performance parameters. 16 . The computer system of claim 9 , wherein the management sub-system is further configured to cause failover to the failover data region in compliance with the recovery performance parameters as a result of the failure event. 17 . One or more non-transitory computer-readable storage media having collectively stored therein instructions that, when executed by one or more processors of a recovery service, cause the recovery service to: generate a recovery plan based at least in part on information provided through an interface, the information including a selection of one or more virtual machine computing resources hosted by one or more services of a computing resource service provider in a first data region, and a selection of a failover data region, the virtual machine computing resources configured for instantiating at least one virtual machine; and coordinate failover preparation by at least transmitting one or more executable instructions to the one or more services, causing the selected one or more virtual machine computing resources to be redundantly maintained based at least in part on dependencies among the selected one or more virtual machine computing resources to enable failover to the failover data region. 18 . The one or more non-transitory computer-readable storage media of claim 17 , wherein: the information further includes a recovery time objective, the recovery time objective defines a duration of time for the one or more virtual machine computing resources to be restored as a result of the detected failure event; and the one or more virtual machine computing resources are redundantly maintained by the one or more services in accordance with the recovery time objective. 19 . The one or more non-transitory computer-readable storage media of claim 17 , wherein: the information further includes a recovery point objective, the recovery point objective defines a maximum amount of time in which customer data may be lost as a result of the detected failure event; and the one or more virtual machine computing resources are redundantly maintained by the one or more services in accordance with the recovery point objective. 20 . The one or more non-transitory computer-readable storage media of claim 17 , wherein the selected one or mo
eliminating a faulty processor or activating a spare · CPC title
where the redundant components share neither address space nor persistent storage · CPC title
Error detection or correction of the data by redundancy in hardware · CPC title
switching over of hardware resources · CPC title
with a single idle spare processing component · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.