Provisioning and managing replicated data instances

• US 8,335,765 B2
• Filed: 10/26/2009
• Issued: 12/18/2012
• Est. Priority Date: 10/26/2009
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Sivasubramanian, Swaminathan, McAlister, Grant Alexander MacDonald
• Primary Examiner(s): Nguyen, Cindy
• Application Number:
  US12/606,093
• Publication Number:
  US 20110099147A1
• Time in Patent Office: 1,149 Days
• Field of Search: 707/610, 707/634, 707/639, 714/43
• US Class Current: 707/639
• CPC Class Codes: G06F 11/0727 in a storage system, e.g. in a DASD or network based storage system drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2076 Synchronous techniques
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A replicated database instance can be provisioned that provides primary and secondary replicas that can be provisioned in different data zones or geographical locations. The database can be installed on the primary replica, and both the primary and secondary replica can have installed a block level replication mechanism that allows any I/O operation to be replicated by between the primary and secondary replicas. Any failure or outage of the primary replica can be addressed by performing a failover operation to the secondary replica. A DNS name or other such approach can be used such that the name can be aliased to the secondary replica during a failover, such that there is no action needed on the part of the customer to utilize the “new” primary replica. The creation of the database and provisioning of the replicated instance can be initiated using a Web service call to a control environment.

Claims

1. A computer-implemented method of provisioning a replicated relational database in a database environment using one or more self-service Web services of a control environment, comprising:

under control of one or more computer systems configured with executable instructions,

providing a plurality of application programming interfaces (APIs) each enabling a user to submit a Web service request to a control environment, the Web service request including at least a request to create a replicated relational database for the user in a database environment;

in response to receiving the request to create the replicated relational database for the user to the control environment through a first API of the plurality of APIs, instantiating a workflow including tasks for;

provisioning a primary instance replica in a first data zone in the database environment;

installing a database engine in the primary instance replica;

provisioning a secondary instance replica in a second data zone in the database environment using one or more snapshots of the primary instance replica; and

connecting a block level replication mechanism to each of the primary instance replica and secondary instance replica, the block level replication mechanism configured to intercept any read or write for the primary instance replica and cause any data updated for the primary instance replica to be synchronously updated to the secondary instance replica; and

providing the user with an alias name enabling the user to interact with the database engine installed in the primary instance replica, the interacting through the alias name causing the block level replication mechanism to update the data to the secondary instance replica, the alias name automatically updated to be associated with the secondary instance replica upon a failure of the primary instance replica.

2. The computer-implemented method of claim 1, wherein each of the primary instance replica and the secondary instance replica is run on a separate database in the database environment, each separate database being attached to one or more dedicated block storage volumes.

3. The computer-implemented method of claim 2, wherein the block-level replication mechanism is operable to synchronously replicate the data between the one or more dedicated block storage volumes of the primary instance replica and the secondary instance replica.

4. A computer-implemented method of enabling a user to create a replicated database in a database environment using a control environment, comprising:

under control of one or more computer systems configured with executable instructions,

providing a plurality of application programming interfaces (APIs) each enabling a user to submit a Web service request to a control environment, each API corresponding to a desired action to be performed with respect to a database for the user in a database environment;

in response to receiving the Web service request to create a replicated database from the user to the control environment through one of the plurality of APIs, causing a primary instance replica and a secondary instance replica for the replicated database to be provisioned in the database environment, causing a block-level replication mechanism to be established, the block-level replication mechanism configured to intercept any write operation for the replicated database at the primary instance replica and synchronously replicate changes for the write operation to the secondary instance replica; and

associating an alias with the primary instance replica, the alias enabling the user to access the replicated database via the primary instance replica, the alias being updated to be associated with the secondary instance replica in an event of failure of the primary instance replica.

5. The computer-implemented method of claim 4, wherein the primary instance replica and secondary instance replica are provisioned in a single data zone, in separate data zones at separate geographical locations, in the single data zone across multiple geographical locations, or across multiple data zones in a single geographical region.

6. The computer-implemented method of claim 4, wherein the control environment is configured to automatically perform a failover operation to the secondary instance replica if the primary instance replica becomes unavailable.

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

causing a host manager to be installed for each of the primary instance replica and the secondary instance replica, each host manager operable to communicate with the control environment and perform one or more tasks in the database environment.

8. The computer-implemented method of claim 4, wherein secondary block storage volumes for the secondary instance replica are created using one or more snapshots of primary block storage volumes for the primary instance replica.

9. The computer-implemented method of claim 4, wherein the primary instance replica and the secondary instance replica are provisioned in the database environment when the Web service request received from the user includes a replication parameter value indicating that the replicated database is to be created.

10. The computer-implemented method of claim 4, wherein the user is provided with the alias enabling the user to communicate with a current primary instance replica, including when a failover operation causes the secondary instance replica to become a new current primary instance replica.

11. The computer-implemented method of claim 4, further comprising:

enabling the user to convert a non-replicated database to the replicated database using an applicable Web service request submitted to the control environment through one of the plurality of APIs.

12. The computer-implemented method of claim 4, further comprising:

capturing one or more snapshots of the replicated database in response to receiving the Web service request through one of the plurality of APIs.

13. The computer-implemented method of claim 12, wherein the one or more snapshots are taken on the secondary instance replica.

14. The computer-implemented method of claim 4, further comprising:

in response to the Web service request, executing a workflow in the control environment including tasks for provisioning, configuring, and connecting the primary instance replica and the secondary instance replica in the database environment.

15. The computer-implemented method of claim 4, further comprising:

monitoring health information for the primary instance replica and the secondary instance using at least one monitoring component of the control environment.

16. The computer-implemented method of claim 4, further comprising:

storing configuration information for the primary instance replica and the secondary instance replica to a data store in the control environment.

17. The computer-implemented method of claim 4, wherein the block-level replication mechanism is database engine independent.

18. A system for enabling a user to create a replicated database in a database environment using a control environment, comprising:

a processor; and

a memory device including instructions that, when executed by the processor, cause the processor to;

provide a plurality of application programming interfaces (APIs) each enabling a user to submit a Web service request to a control environment, each API corresponding to a desired action to be performed with respect to a database for the user in a database environment;

in response to receiving the Web service request to create a replicated database from the user to the control environment through one of the plurality of APIs, cause a primary instance replica and a secondary instance replica for the replicated database to be provisioned in the database environment, cause a block-level replication mechanism to be established, the block-level replication mechanism configured to intercept any write operation for the replicated database at the primary instance replica and synchronously replicate changes for the write operation to the secondary instance replica; and

associate an alias with the primary instance replica, the alias enabling the user to access the replicated database via the primary instance replica, the alias being updated to be associated with the secondary instance replica in an event of failure of the primary instance replica.

19. The system of claim 18, wherein the primary instance replica and the secondary instance replica are provisioned in a single data zone, in separate data zones at separate geographical locations, in the single data zone across multiple geographical locations, or across multiple data zones in a single geographical region.

20. The system of claim 18, wherein the instructions when executed further cause the processor to:

in response to the Web service request, execute a workflow in the control environment including tasks for provisioning, configuring, and connecting the primary instance replica and the secondary instance replica in the database environment.

21. The system of claim 18, wherein the instructions when executed further cause the processor to:

cause a host manager to be installed for each of the primary instance replica and the secondary instance replica, each host manager operable to communicate with the control environment and perform one or more tasks in the database environment.

22. A non-transitory computer-readable storage medium storing instructions for enabling a user to create a replicated database in a database environment using a control environment, the instructions when executed by a processor causing the processor to:

provide a plurality of application programming interfaces (APIs) each enabling a user to submit a Web service request to a control environment, each API corresponding to a desired action to be performed with respect to a database for the user in a database environment;

in response to receiving the Web service request to create a replicated database from the user to the control environment through one of the plurality of APIs, cause a primary instance replica and a secondary instance replica for the replicated database to be provisioned in the database environment, cause a block-level replication mechanism to be established, the block-level replication mechanism configured to intercept any write operation for the replicated database at the primary instance replica and synchronously replicate changes for the write operation to the secondary instance replica; and

associate an alias with the primary instance replica, the alias enabling the user to access the replicated database via the primary instance replica, the alias being updated to be associated with the secondary instance replica in an event of failure of the primary instance replica.

23. The non-transitory computer-readable storage medium of claim 22, wherein the primary instance replica and the secondary instance replica are provisioned in a single data zone, in separate data zones at separate geographical locations, in the single data zone across multiple geographical locations, or across multiple data zones in a single geographical region.

24. The non-transitory computer-readable storage medium of claim 22, wherein the instructions when executed further cause the processor to:

in response to the Web service request, execute a workflow in the control environment including tasks for provisioning, configuring, and connecting the primary instance replica and the secondary instance replica in the database environment.

25. The non-transitory computer-readable storage medium of claim 22, wherein the instructions when executed further cause the processor to:

cause a host manager to be installed for each of the primary instance replica and the secondary instance replica, each host manager operable to communicate with the control environment and perform one or more tasks in the database environment.