This topic describes how to restore the data of an ApsaraDB RDS for SQL Server instance from a cross-region backup file to a new RDS instance. The new RDS instance must reside in the same region as the cross-region backup file.
- For more information about how to restore the data of an ApsaraDB RDS for MySQL instance across regions, see Restore the data of an ApsaraDB RDS for MySQL instance across regions.
- For more information about how to restore the data of an ApsaraDB RDS for PostgreSQL instance across regions, see Restore the data of an ApsaraDB RDS for PostgreSQL instance across regions.
Restore data to a new RDS instance
- Log on to the RDS management console, in the left-side navigation pane, click Backups , and then select a region above.
- On the Backup Instances tab of the Cross-region Backup tab, find your RDS instance and click the ID of the instance. On the page that appears, find the backup file that you want to use, and click Restore in the Actions column.
- Select Restore to New Instance and click OK.
- On the Restore Database page, click the Subscription or Pay-As-You-Go tab and configure the following parameters.
Parameter Description Restore Mode
- By Backup Set: allows you to restore the data of your RDS instance from a data backup file.
- By Time: allows you to restore the data of your RDS instance to a specific point in time. The point in time must be within the specified log backup retention period.
Backup Set The data backup file from which you want to restore the data of your RDS instance. This parameter appears only when you set the Restore Mode parameter to By Backup Set. Restore Point The point in time to which you want to restore the data of your RDS instance. This parameter appears only when you set the Restore Mode parameter to By Time.Note Both local and cross-region log backup files can be used to restore the data of your RDS instance to a specific point in time. Region The region to which the new RDS instance belongs.Note You can select only the region to which the cross-region backup files of your RDS instance are stored. Zone The zone where the new RDS instance resides. Each zone is an independent physical location within a region. Zones in the same region provide the same services. You can create the new RDS instance in the same zone as the Elastic Compute Service (ECS) instance to which you want to connect. You can also create the new RDS instance in a different zone than the ECS instance to which you want to connect. CPU and Memory The specifications of the new RDS instance. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum input/output operations per second (IOPS). For more information, see Primary instance types. Capacity The storage capacity that the new RDS instance has available to store data files, system files, archived log files, and transaction files. Network Type
Note The settings of some parameters cannot be modified. These parameters include Database Engine, Version, and Edition. The same settings of these parameters must be specified for both your RDS instance and the new RDS instance.
- Classic Network: the traditional type of network.
- VPC: the recommended type of network. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and higher performance than the classic network. If you select the VPC network type, you must also select a vSwitch that is associated with the specified VPC.
- Specify the Duration and Quantity parameters. Then, click Buy Now. You must specify the Duration parameter when the new RDS instance is billed on a subscription basis.
After you create an RDS instance, you must configure IP address whitelists or security groups and create accounts. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for SQL Server instance and Create an account on an ApsaraDB RDS for SQL Server instance. If you want to connect to the RDS instance over the Internet, you must also apply for a public endpoint. For more information, see Apply for or release a public endpoint on an ApsaraDB RDS for SQL Server instance. After you complete these operations, you can connect to the RDS instance. For more information, see Connect to an ApsaraDB RDS for SQL Server instance.
|Check cross-region backup||Checks whether an ApsaraDB RDS instance has a cross-region data backup file that can be used to restore data across regions.|
|Restore data to a new instance across regions||Restores the data of an ApsaraDB RDS instance to a new RDS instance that resides in a different region than the original RDS instance.|
|Modify cross-region backup settings||Modifies the cross-region backup settings of an ApsaraDB RDS instance.|
|Query cross-region backup settings||Queries the cross-region backup settings of an ApsaraDB RDS instance.|
|Query cross-region data backup files||Queries the cross-region data backup files of an ApsaraDB RDS instance.|
|Query cross-region log backup files||Queries the cross-region log backup files of an ApsaraDB RDS instance.|
|Query regions that support cross-region backup||Queries the regions to which the cross-region backup files from the current region can be restored.|
|Query the time range to which you can restore data by using a cross-region backup set||Queries the restorable time range that is supported by a cross-region backup file.|
|Query ApsaraDB for RDS instances on which cross-region backup is enabled||Queries the ApsaraDB RDS instances for which the cross-region backup feature is enabled in a region and the cross-region backup settings of these instances.|