ApsaraDB RDS:Switch the vSwitch for an RDS for SQL Server instance

Impacts

• When your RDS instance is being switched to a different vSwitch, you may encounter a network interruption that lasts approximately 30 seconds. Make sure that your application is configured to automatically reconnect to your RDS instance.

• Switching the vSwitch changes the virtual IP address (VIP). It's better to connect to your instance using its endpoint instead of its IP address in your application.

• VIP changes disrupts RDS connections to Data Management (DMS) and Data Transmission Service (DTS) , which will resume automatically once the change is complete.

• Client-side caching can cause data to become read-only. Clear the cache to enable write operations.

Procedure

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the left navigation pane, click Database Connection, and then click Switch vSwitch.

   

3. Select a vSwitch and click OK.

   Note

   • You can switch the instance only to a vSwitch that is in the same zone. To create a VPC or vSwitch, go to the VPC console.

   • Only ApsaraDB RDS for SQL Server 2008 R2 instances that use cloud disks support VPC changes. Other instance versions do not support VPC switching. If your instance does not support direct VPC changes, you must purchase a new ApsaraDB RDS instance, select the destination VPC during the purchase, and then migrate the data to the new instance.

   

4. In the dialog box, review the risks of the switch and click OK.

References

• To switch the instance to a vSwitch in a different zone, see Migrate an instance across zones.

• You can also switch the vSwitch of an instance by calling the SwitchDBInstanceVpc - Switch the VPC and vSwitch for an RDS instance API operation.