ApsaraDB RDS:Migrate an ApsaraDB RDS for SQL Server instance across zones

Billing rules

You are not charged for the cross-zone migration. This applies even if you migrate your RDS instance from one zone to multiple zones.

Impacts

• If you start a task to migrate an RDS instance across zones, you cannot cancel the task.

• The configurations of your RDS instance, such as the name, endpoints, tags, and database accounts, remain unchanged after the migration.

• The migration process triggers data migration. During the process, your RDS instance runs as expected, and the workloads on the RDS instance are not affected.

• The period of time that is required to complete the migration varies based on the data volume of your RDS instance. In most cases, the migration requires approximately 20 minutes. If a large number of operations are performed during the migration, the period of time to complete the migration is prolonged. We recommend that you upgrade your RDS instance during an appropriate period of time.

• During the switchover, your RDS instance becomes unavailable for a few minutes. Make sure that your application is configured to automatically reconnect to your RDS instance.

• The migration causes changes to the virtual IP addresses (VIPs) of your RDS instance. We recommend that you use an endpoint of your RDS instance instead of an IP address to connect your application to your RDS instance.

• After the migration is complete, you must immediately delete the cached DNS records from the database client. If the database client runs on a JVM, we recommend that you set the time-to-live (TTL) in the JVM configuration to 60 seconds or less. This way, if the VIP that is bound to the in-use endpoint of your RDS instance changes, your application can query the related DNS records again to obtain the new VIP. Then, your application can connect to the new VIP.

  Note

  The following TTL-setting methods are provided for reference:

  • For all JVM-based applications: Set the networkaddress.cache.ttl parameter in the $JAVA_HOME/jre/lib/security/java.security file to 60.

  • For local applications, configure the networkaddress.cache.ttl java.security.Security.setProperty("networkaddress.cache.ttl" , "60"); setting in the initialization code of local applications. The configuration must be completed before you call the InetAddress.getByName() function for the first time to establish a network connection.

• If your RDS instance has an ongoing Data Transmission Service (DTS) task, you must restart the DTS task after the migration is complete.

Limits

Migration scenarios

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 Basic Information section of the page that appears, click Migrate Across Zones.

   

3. In the dialog box that appears, specify the destination zone, VPC, vSwitch, and migration time.

   Note

   • For more information about how to create a VPC, see Create and manage a VPC.

   • For more information about how to create a vSwitch, see Work with vSwitches.

4. Click OK.

   After you click OK, the system starts to replicate the data of your RDS instance to the destination zone. This process does not interrupt the workloads on your RDS instance. After all data is replicated to the destination zone, the system switches the workloads over to the destination zone within the specified time period. You can set the switching time to Switch Now or Switch Within Maintenance Window.

   Important

   During the switchover, your RDS instance becomes unavailable for a few minutes. Make sure that your application is configured to automatically reconnect to your RDS instance.

FAQ

Can I directly upgrade or change the deployment mode of an RDS instance that runs SQL Server Web on RDS Basic Edition to the multi-zone deployment mode? Can the primary and secondary RDS instances reside in different zones?

Related operations