You can migrate an instance to another availability zone (AZ) within the same region. All attributes and configurations (including the private network address and the subnet) of the instance remain unchanged after migration. The amount of time required is proportional to the volume of data in the instance. The more data there is, the longer the data migration takes. In addition, the instance access is not affected during migration.
If a primary instance of dual-server high availability edition or cluster edition has read-only instances or implements the pub/sub messaging paradigm, you need to submit a ticket to migrate it across AZs.
The region where the instance resides must have multiple AZs.
After you click Submit, instance data will be migrated to the target AZ at the underlying layer without affecting instance running and access.
After instance data is migrated, an instance switch will occur (upon migration completion or during maintenance time), causing a flash disconnection. After the switch is done, the whole process of cross-AZ migration is completed.
You can view cross-AZ migration tasks in the Running Tasks box in the upper-right corner of the Database Management tab.
If the instance is scheduled to be switched during the maintenance time according to the configurations of its cross-AZ migration task, but you need to switch it urgently under special circumstances, you can click Switch Now in the Operation column in the instance list in the TencentDB for SQL Server console.