Are my MySQL instances always available during scaling and specification changing?
Currently, RDS for MySQL supports disk scaling and CPU/memory specification changing. Instances need to be restarted during disk scaling and specification changing. Instances are not available until capacity scaling and specification changes are complete and they are restarted. During capacity scaling and specification changing, the master-slave switching may occur, which may cause the service to be temporarily interrupted. Please perform these operations during off-peak periods to avoid abnormal business interruption.
Why does the instance status become abnormal after the port is changed?
Issue Description
• The instance status becomes Abnormal after the port is changed.
• The instance cannot be connected using the new port number.
Possible Cause
The submitted database port is temporarily occupied.
Procedure
Use the port number and retry the port change again.
If the change is successful, the previous change failed because the port was temporarily occupied.
If the change still fails, please contact our technical staff.
Does the MySQL instance support changing VPCs?
No.
However, you can switch to the target VPC by restoring a full backup of the existing RDS for MySQL to a new instance. Details are as follows:
1. Select the target VPC when creating an RDS for MySQL instance. For details, see Quick Start-Connecting to a MySQL Instance Through an Intranet.
2. Use full backups to restore to the new instance. For details, see Backup and Restoration-Restoring an Instance From Full Backup Files.