Failover and recovery for replicated data instances

US2016210205A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016210205-A1
Application numberUS-201615083210-A
CountryUS
Kind codeA1
Filing dateMar 28, 2016
Priority dateOct 26, 2009
Publication dateJul 21, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information synchronously replicated to the secondary replica at a block level, such that the primary and secondary replicas are in sync. In the event that the monitoring component is not able to communicate with one of the replicas, the monitoring component can attempt to determine whether those replicas can communicate with each other, as well as whether the replicas have the same data generation version. Depending on the state information, the monitoring component can automatically perform a recovery operation, such as to failover to the secondary replica or perform secondary replica recovery.

First claim

Opening claim text (preview).

What is claimed is: 1 . A computer-implemented method for managing a replicated database, comprising: under control of one or more computer systems configured with executable instructions, obtaining a generation identifier for a primary instance replica and a secondary instance replica of the replicated database upon initial pairing of the primary instance replica and the secondary instance replica, the primary instance replica and the secondary replica associated with a data environment; synchronizing data between the primary instance replica and the secondary instance replica using a block-level replication mechanism; periodically providing status information to a monitoring component of a control environment, the control environment being separate from the data environment; and providing failure information to the monitoring component in response to the primary instance replica being unable to communicate with the secondary instance replica, the failure information including at least the generation identifier. 2 . The computer-implemented method of claim 1 , further comprising: in response to the primary instance replica being able to communicate with the monitoring component, obtaining a second generation identifier for the primary instance replica; and performing one or more input/output (I/O) operations via the primary instance replica. 3 . The computer-implemented method of claim 2 , further comprising: re-pairing the primary instance replica and the secondary instance replica; synchronizing the data between the primary instance replica and the secondary instance replica based on the one or more I/O operations performed via the primary instance replica, the one or more I/O operations performed after generating the second generation identifier; and obtaining a third generation identifier for the primary instance replica and the secondary instance replica. 4 . The computer-implemented method of claim 2 , further comprising: pairing the primary instance replica with a new secondary instance replica; synchronizing the data between the primary instance replica and the new secondary instance replica; and generating a third generation identifier for the primary instance replica and the new secondary instance replica. 5 . The computer-implemented method of claim 1 , further comprising: in response to the primary instance replica being unable to communicate with the monitoring component, verifying that the generation identifier of the secondary instance replica corresponds to a last known generation identifier of the primary instance replica; promoting the secondary instance replica to be a new primary instance replica; pairing the new primary instance replica with a new secondary instance replica; synchronizing the data between the new primary instance replica and the new secondary instance replica; and obtaining a second generation identifier for the new primary instance replica and the new secondary instance replica. 6 . A system for managing a replicated database, comprising: a processor; and a memory device including instructions that, when executed by the processor, cause the processor to: synchronize data between a primary instance replica and a secondary instance replica of the replicated database, the primary instance replica and the secondary replica associated with a data environment; provide status information to a monitoring component of a control environment, the control environment being separate from the data environment; and provide failure information to the monitoring component in response to the primary instance replica being unable to communicate with the secondary instance replica. 7 . The system of claim 6 , wherein the instructions when executed further cause the processor to: obtain data generation information for the primary instance replica and the secondary instance replica upon initial pairing of the primary instance replica and the secondary instance replica, wherein the failure information includes at least the data generation information. 8 . The system of claim 6 , wherein the instructions when executed to cause the system to synchronize the data between the primary instance replica and the secondary instance replica is performed based at least in part upon using a block-level replication mechanism. 9 . The system of claim 6 , wherein the instructions when executed further cause the processor to: in response to the primary instance replica being able to communicate with the monitoring component, obtain second data generation information for the primary instance replica; and perform one or more I/O operations via the primary instance replica. 10 . The system of claim 9 , wherein the instructions when executed further cause the processor to: re-pair the primary instance replica and the secondary instance replica; synchronize the data between the primary instance replica and the secondary instance replica based on the one or more I/O operations performed via the primary instance replica, the one or more I/O operations performed after generating the second data generation information; and obtain third generation identifier for the primary instance replica and the secondary instance replica. 11 . The system of claim 9 , wherein the instructions when executed further cause the processor to: pair the primary instance replica with a new secondary instance replica; synchronize the data between the primary instance replica and the new secondary instance replica; and obtain third data generation information for the primary instance replica and the new secondary instance replica. 12 . The system of claim 6 , wherein the instructions when executed further cause the processor to: verify that the data generation information of the secondary instance replica corresponds to last known data generation information of the primary instance replica; promote the secondary instance replica to be a new primary instance replica; pair the new primary instance replica with a new secondary instance replica; synchronize the data between the new primary instance replica and the new secondary instance replica; and obtain second data generation information for the new primary instance replica and the new secondary instance replica. 13 . The system of claim 6 , wherein the data generation information comprises a universally unique identifier. 14 . A non-transitory computer-readable storage medium storing instructions for managing a replicated database, the instructions when executed by a processor causing the processor to: obtain data generation information for a primary instance replica and a secondary instance replica of the replicated database upon initial pairing of the primary instance replica and the secondary instance replica, the primary instance replica and the secondary replica associated with a data environment synchronize data between the primary instance replica and the secondary instance replica; provide status information to a monitoring component of a control environment, the control environment being separate from the data environment; and provide failure information to the monitoring component in response to the primary instance replica being unable to communicate with the secondary instance replica, the failure information including at least the data generation information. 15 . The non-transitory computer-readable storage medium of claim 14 , wherein the instructions when executed to cause the processor to synchronize the data between the primary instance replica and the secondary instance replica is p

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016210205A1 cover?
Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information sync…
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/2025. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Jul 21 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).