Rebuild secondary database

Supported instance types

• MyBase MySQL High-availability Edition instances
• MyBase PostgreSQL instances

Notes

• Avoid read and write operations on the primary instance during the rebuild. Otherwise, data synchronization may fail and the rebuild will not succeed.
• The actual running time depends on your data volume and workload. Wait patiently.

Procedure

1. Log on to the ApsaraDB for MyBase console.
   
2. In the upper-left corner of the page, select the destination region.
   
3. In the navigation pane on the left, click Cluster list. In the Actions column for your target dedicated cluster, click Details.
4. In the navigation pane on the left, click Instances.
5. Find the target instance and click Rebuild secondary database in the Actions column.
   Rebuild secondary database is in the More drop-down menu.
6. The Rebuild secondary database page appears.
   • If you do not need to specify a host for the rebuild, click OK.
     Note When Specify Host is not enabled, the rebuild flow is as follows:

     • First, rebuild the secondary instance on its original host.
     • If the original host cannot be used, choose another host in the dedicated cluster (excluding the host of the primary instance) for the rebuild.
     • If no suitable host is found or there is insufficient space, the system shows that the rebuild cannot proceed. Add a host or scale out first.
   • To rebuild the secondary instance on a specific host, click the Specify Host button, then Click to select the target host, and click OK. The host selection panel lets you search and filter by Host ID. The list shows each host’s Hostname, Status, Allocatable CPU, Allocatable memory, Allocatable local disk, and Zone.

Related API