ApsaraDB RDS:Migrate data from a self-managed SQL Server instance to an ApsaraDB RDS for SQL Server instance

Prerequisites

• The RDS instance runs SQL Server 2012 or later.

• The source database is a self-managed SQL Server instance.

• If you use a RAM user to migrate data, make sure that the AliyunOSSFullAccess and AliyunRDSFullAccess policies are attached to the RAM user. For more information about how to grant permissions to RAM users, see Use RAM to manage OSS permissions and Use RAM to manage ApsaraDB RDS permissions.

Limits

Only full backup files can be used for the data migration.

Preparations

1. Install Python 2.7.18. For more information, visit the Python official website.

2. Check whether Python 2.7.18 is installed.

   • Windows operating systems

     Run the c:\Python27\python.exe -V command to check the Python version. If Python 2.7.18 is displayed, Python 2.7.18 is installed.

     If the system prompts that the preceding command is not an internal or external command, add the Python installation path and the pip command path to the Path environment variable.

     

   • Mac, Linux, or Unix operating systems

     Run the python -V command to check the Python version. If Python 2.7.18 is displayed, Python 2.7.18 is installed.

3. Use one of the following methods to install the SDK dependency package:

   • Run the pip command

     pip install aliyun-python-sdk-rds
     pip install oss2

   • Use the source code

     # Clone the API repository.
     git clone https://github.com/aliyun/aliyun-openapi-python-sdk.git
     # Install the SDK core repository of Alibaba Cloud.
     cd aliyun-python-sdk-core
     python setup.py install
     # Install the ApsaraDB RDS SDK.
     cd aliyun-python-sdk-rds
     python setup.py install
     # Clone the OSS SDK.
     git clone https://github.com/aliyun/aliyun-oss-python-sdk.git
     cd aliyun-oss-python-sdk
     # Install oss2.
     python setup.py install

4. Create an OSS bucket. Make sure that the OSS bucket resides in the same region as the RDS instance. For more information, see Create buckets.

   Note

   If an OSS bucket that resides in the same region as the RDS instance already exists, skip this step.

5. Create databases on the RDS instance. Make sure that each database whose data you want to migrate has a counterpart with an identical name on the RDS instance. In addition, keep the created databases empty.

   • If the RDS instance runs SQL Server 2012 or later, skip this step.

   • If the RDS instance runs SQL Server 2008 R2, create databases based on the descriptions in Create an account and a database for an ApsaraDB RDS instance that runs SQL Server 2008 R2.

6. Back up all databases on the self-managed SQL Server instance.

   Warning

   • For data consistency purposes, we recommend that you stop data writes to these databases during the full backup.

   • If you do not use the backup script to perform the full backup, the names of the generated backup files must follow the format of Database name_Backup type_Backup time.bak, such as Testdb_FULL_20180518153544.bak. If the name is in a different format, the backup fails.

   1. Download the backup script file.

   2. Double-click the backup script file to open it by using Microsoft SQL Server Management Studio (SSMS). For more information about how to use SSMS for connections, see official documentation.

   3. Configure the following parameters.

      Parameter	Description
      @backup_databases_list	The name of the self-managed database that you want to back up. If you specify multiple databases, separate the names of these databases with semicolons (;) or commas (,).
      @backup_type	The backup type. Valid values: FULL: full backup DIFF: incremental backup LOG: log backup Important In this example, set the value to FULL.
      @backup_folder	The directory that is used to store backup files on the self-managed database. If the specified directory does not exist, the system automatically creates one.
      @is_run	Specifies whether to perform a backup or a check. Valid values: 1: performs a backup. 0: performs a check.

      Examples:

      SELECT
          /**
          * Databases list needed to backup, delimiter is : or ,
          * empty('') or null: means all databases excluding system database
          * example: '[testdb]: TestDR, Test, readonly'
          **/
          @backup_databases_list = N'[dtstestdata],[testdb]'
          @backup_type = N'FULL',                    -- Backup Type? FULL: FULL backup; DIFF: Differential backup; LOG: Log backup
          @backup_folder = N'C:\BACKUP'              -- Backup folder to store backup files.
          @is_run = 1                                -- Check or run? 1, run directly; 0, just check

   4. Run the backup script to back up the specified databases and store the backup files to the specified directory.

      

7. Use one of the following methods to upload the backup files to the OSS bucket that you created.

   Warning

   Make sure that the OSS bucket and the RDS instance reside in the same region. This allows the RDS instance to read the backup files at faster speeds. This also helps prevent failures that may occur if the backup files cannot be downloaded.

   Method	Description
   Use ossbrowser to upload backup files	We recommend that you use ossbrowser to upload backup files to the OSS bucket. For more information, see Use ossbrowser. Important If the self-managed instance is deployed in an Elastic Compute Service (ECS) instance that resides in a virtual private cloud (VPC), you can upload the backup files to the specified OSS bucket by using the VPC endpoint of the OSS bucket. This improves upload efficiency.
   Use the OSS console to upload backup files	If the size of backup files is smaller than 5 GB, you can upload the files by using the OSS console. For more information, see Upload objects.
   Call OSS API operations to upload backup files	If you want to upload the backup files unattended, use the OSS API operations to perform resumable uploads. For more information, see Multipart upload.

Procedure

1. Download the migration script package.

2. Decompress the migration script package and run the following command to view the parameters that you need to specify:

   python ~/Downloads/RDSSQLCreateMigrateTasksBatchly.py -h

   A similar result is returned:

   RDSSQLCreateMigrateTasksBatchly.py -k <access_key_id> -s <access_key_secret> -i <rds_instance_id> -e <oss_endpoint> -b <oss_bucket> -d <directory>

   Table 1. Parameters

   Parameter	Description
   access_key_id	The AccessKey ID of the Alibaba Cloud account to which the RDS instance belongs.
   access_key_secret	The AccessKey secret of the Alibaba Cloud account to which the RDS instance belongs.
   rds_instance_id	The ID of the RDS instance.
   oss_endpoint	The endpoint of the OSS bucket that stores the backup files. For more information about how to obtain the endpoint, see Bucket overview.
   oss_bucket	The name of the OSS bucket that stores the backup files.
   directory	The folder that stores the backup files in the OSS bucket. If the backup files are stored in the root folder, enter a forward slash (/).

3. Run the migration script to complete the migration task.

   Examples:

   You can run the migration script to migrate all the backup files that meet the specified conditions from the Migrationdata folder in the OSS bucket named testdatabucket to the RDS instance whose ID is rm-2zesz5774ud8s****.

   python ~/Downloads/RDSSQLCreateMigrateTasksBatchly.py -k LTAIQ**** -s BMkIUhroub******** -i rm-2zesz5774ud**** -e oss-cn-beijing.aliyuncs.com -b testdatabucket -d Migrationdata

4. View the progress of the migration task.

   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. Perform the following steps based on the SQL Server version of your RDS instance:

      • SQL Server 2008 R2

        In the left-side navigation pane of the page that appears, click Database Migration to Cloud. You can view all the migration tasks that you have submitted.

        Note

        You can click Refresh in the upper-right corner of the page to view the latest status of the migration tasks.

      • SQL Server 2012 and later

        In the left-side navigation pane of the page that appears, click Backup and Restoration. Then, click the Backup Data Upload History tab.

        Note

        By default, the migration records over the last seven days are displayed. You can specify a time range to view the migration tasks over the specified time range.

Common errors

Related operations