Create a Read Replica

Create a Read Replica to get a read-only copy of your DBaaS instance that you can query. The replica can be in the same region or in the other one. A DBaaS instance can have up to four Read Replicas, and you pay for each one separately; see Read Replicas.

Before you begin

• The primary DBaaS instance is Running.
• SSL is on for the primary; see Enable SSL on a DBaaS instance.
• For a replica in the other region, the primary is unencrypted and attached to a VPC with an active VPC peering connection to that region.
• On a prepaid account, you have enough infra credits to run the replica for about 24 hours.

Create the replica

On the DBaaS instance’s Read Replica tab, click Create Read Replica. In Add Read Replica:

1. Choose the Target Region, Delhi or Chennai. A replica in the primary’s region takes read traffic off the primary. A replica in the other region does the same, and also keeps a copy of your data in that region.
2. For a replica in the other region, choose the VPC Peering to use.
3. In Please choose a Committed / Uncommitted Read Replica, choose how to pay for the replica. MyAccount creates the replica on the primary’s plan. Hourly Billed suits a replica you are trying out. A committed period suits one you will keep, and longer periods save more.
4. Click Create Replica Node.

The replica appears on the Read Replica tab. If the primary has a public IP, the replica gets its own Public IP too, shown on its row. To move a replica to a committed plan later, see Convert a DBaaS instance to a committed plan.

You now have a Read Replica that serves read-only queries. Once its status reads Running, you can turn it into an independent DBaaS instance; see Promote a Read Replica to Master Node. If creating the replica shows an error, see Troubleshooting DBaaS.

Keep a replica in the other region in sync

A replica in the other region syncs through the primary’s VPC and its peering connection. Detaching the VPC pauses that sync until you reattach the VPC. Deleting the peering connection ends the sync for good. To keep the replica as an independent DBaaS instance, promote it before making either change; see Promote a Read Replica to Master Node.

Delete a Read Replica

Deleting a replica is permanent, so take a snapshot of the primary first if you need the data.

1. In the replica’s row menu, click Delete read replica.
2. Check I understand the associated risk and want to delete read-only node.
3. Click Delete.

The replica is gone and its charge stops; the primary keeps running as before.