# US 2016/0253400 A1 · Provisioning and managing replicated data instances

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0253400 A1
- Document ID: US20160253400A1
- Status: Published application
- Kind: A1
- Application number: 15/150,370
- Filed: 2016-05-09
- Published: 2016-09-01
- Earliest claimed: 2009-10-26
- Assignees: Amazon Technologies, Inc.
- Applicants: Amazon Technologies, Inc.
- Inventors: Grant Alexander MacDonald McAlister; Swaminathan Sivasubramanian
- Web page: https://patentgrep.com/patent/US20160253400A1

## CPC

- G06F 16/275: {Synchronous replication}
- G06F 11/2076: {Synchronous techniques}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- 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)}
- G06F 11/0766: {Error or fault reporting or storing}
- G06F 11/1446: Point-in-time backing up or restoration of persistent data
- G06F 11/2069: {Management of state, configuration or failover}
- G06F 2201/80: Database-specific techniques
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A replicated database 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. A replicated database can also be scaled according to storage or computing capacity with no disruption of service using a Web service call to the control environment.

## Claims

### Claim at position 1

-23 (canceled)

### Claim 24

A method, comprising:
performing, with one or more computing devices:
receiving a service request to scale storage for a replicated database having a first instance replica and a second instance replica, wherein the replicated database is configured to apply a write operation of the first instance replica to the second instance replica;
scaling the storage for the first instance replica and the second instance replica;
in response to a failure of the first instance replica, associating network address information of the first instance replica with the second instance replica.

### Claim 25 (depends on 24)

The method of claim 24, further comprising executing a workflow via a workflow service, wherein the workflow includes scaling the storage for the first instance replica and the second instance replica.

### Claim 26 (depends on 25)

The method of claim 25, wherein the workflow service is configured to:
generate a workflow task corresponding to the service request; and
provide a state for the workflow task.

### Claim 27 (depends on 26)

The method of claim 26, wherein the workflow task includes at least one of:
modifying an existing number of respective block storage volumes of each of the first instance replica and the second instance replica to a new number of block storage volumes;
causing one or more of the block storage volumes to be rebalanced according to the new number of block storage volumes;
causing one or more respective logical volumes for each of the first instance replica and the second instance replica to be resized according to the new number of block storage volumes; and
causing a respective file system for each of the first instance replica and the second instance replica to be resized according to the new number of block storage volumes.

### Claim 28 (depends on 24)

The method of claim 24, wherein the replicated database comprises a replication mechanism configured to apply the write operation of the first instance replica to the second instance replica.

### Claim 29 (depends on 28)

The method of claim 28, further comprising resizing the replication mechanism based at least in part on a respective new configuration for each of the first instance replica and the second instance replica.

### Claim 30 (depends on 24)

The method of claim 24, further comprising providing an interface configured to receive one or more service requests, wherein each of the one or more service requests correspond to a respective specified action to be performed at a database, and wherein the one or more service requests includes the service request.

### Claim 31 (depends on 24)

The method of claim 24, wherein the network address information includes a domain name system (DNS) name.

### Claim 32 (depends on 24)

The method of claim 24, further comprising causing the first instance replica to failover to the second instance replica, wherein scaling the storage for the second instance replica occurs prior to scaling the storage for the first instance replica.

### Claim 33

A method, comprising:
receiving a service request to scale computing capacity for a replicated database having a first instance replica and a second instance replica;
provisioning a third instance replica and a fourth instance replica for the replicated database based at least in part on a specified compute class, wherein network address information corresponding to the third instance replica is based on network address information corresponding to the first instance replica;
in response to a failure of the third instance replica, associating the network address information corresponding to the third instance replica with the fourth instance replica.

### Claim 34 (depends on 33)

The method of claim 33, wherein the third instance replica and the fourth instance replica are provisioned as part of a workflow service, wherein the workflow service is configured to:
generate a workflow task corresponding to the service request; and
provide a state for the workflow task.

### Claim 35 (depends on 33)

The method of claim 33, further comprising configuring a replication mechanism of the replicated database to apply any write operation of the third instance replica to the fourth instance replica.

### Claim 36 (depends on 33)

The method of claim 33, further comprising causing the first instance replica to failover to the third instance replica in response to provisioning the third instance replica.

### Claim 37 (depends on 36)

The method of claim 36, wherein the third instance replica is provisioned prior to provisioning the fourth instance replica.

### Claim 38

A non-transitory computer-readable storage medium storing instructions that, when executed on one or more processors, cause the one or more processors to:
receiving a service request to scale storage for a replicated database having a first instance replica and a second instance replica, wherein the replicated database is configured to apply a write operation of the first instance replica to the second instance replica;
scaling the storage for the first instance replica and the second instance replica;
in response to a failure of the first instance replica, associating network address information of the first instance replica with the second instance replica.

### Claim 39 (depends on 38)

The non-transitory computer-readable storage medium of claim 38, wherein the instructions further cause the one or more processors to execute a workflow via a workflow service in a control environment, wherein the workflow is configured to:
generate one or more workflow tasks; and
provide a respective state for the one or more workflow tasks.

### Claim 40 (depends on 39)

The non-transitory computer-readable storage medium of claim 39, wherein the one or more workflow tasks correspond to one or more host tasks to be performed by one or more host managers in a data environment, and wherein the data environment is distinct from the control environment.

### Claim 41 (depends on 38)

The non-transitory computer-readable storage medium of claim 38, wherein the instructions further cause the one or more processors to resize a replication mechanism of the replicated database according to a respective new configuration for each of the first instance replica and the second instance replica.

### Claim 42 (depends on 38)

The non-transitory computer-readable storage medium of claim 38, wherein the instructions further cause the one or more processors to provide the network address information of the first instance replica to enable access to the replicated database via the first instance replica.

### Claim 43 (depends on 38)

The non-transitory computer-readable storage medium of claim 38, wherein the service request is based upon at least one of a user request, user preferences, or configuration information.
