PROVISIONING AND MANAGING REPLICATED DATA INSTANCES
0 Assignments
0 Petitions
Accused Products
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.
-
Citations
43 Claims
-
1-23. -23 (canceled)
-
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. - View Dependent Claims (25, 26, 27, 28, 29, 30, 31, 32)
-
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. - View Dependent Claims (34, 35, 36, 37)
-
-
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. - View Dependent Claims (39, 40, 41, 42, 43)
-
Specification