ApsaraDB RDS:Migrate full backup data to the cloud

SQL Server 2012 or later, or SQL Server 2008 R2 with cloud disks

1. Download the backup script and open it in SQL Server Management Studio (SSMS).

2. In the script, modify the parameters in the SELECT statement that are located under YOU HAVE TO INIT PUBLIC VARIABLES HERE.

   Configuration item	Description
   @backup_databases_list	The databases to be backed up. Separate multiple databases with semicolons (;) or commas (,).
   @backup_type	The backup type. Valid values: FULL: full backup. DIFF: differential backup. LOG: log backup.
   @backup_folder	The local directory where the backup file is stored. If the directory does not exist, it is automatically created.
   @is_run	Specifies whether to perform the backup. Valid values: 1: Perform the backup. 0: Perform only a check and do not perform the backup.

3. Run the backup script.

SQL Server 2008 R2 with high-performance local disks

1. Open the Microsoft SQL Server Management Studio (SSMS) client.

2. Log on to the database that you want to migrate.

3. Run the following command to check the current recovery model of the source database.

   USE master;
   GO
   SELECT name, CASE recovery_model
   WHEN 1 THEN 'FULL'
   WHEN 2 THEN 'BULK_LOGGED'
   WHEN 3 THEN 'SIMPLE' END model FROM sys.databases
   WHERE name NOT IN ('master','tempdb','model','msdb');
   GO

   • If the value of model in the result is not FULL, proceed to Step 4.

   • If the value of model in the result is FULL, proceed to Step 5.

4. Run the following command to set the recovery model of the source database to FULL.

   ALTER DATABASE [dbname] SET RECOVERY FULL;
   GO
   ALTER DATABASE [dbname] SET AUTO_CLOSE OFF;
   GO

   Important

   After you set the recovery model to FULL, the amount of log information in SQL Server increases. Ensure that you have sufficient disk space.

5. Run the following command to back up the source database.

   The following example shows how to back up the dbtest database to the backup.bak file.

   USE master;
   GO
   BACKUP DATABASE [dbtest] to disk ='d:\backup\backup.bak' WITH COMPRESSION,INIT;
   GO

6. Run the following command to verify the integrity of the backup file.

   USE master
    GO
    RESTORE FILELISTONLY 
      FROM DISK = N'D:\backup\backup.bak';

   Important

   • If a result set is returned, the backup file is valid.

   • If an error is reported, perform the backup again.

7. Optional: Run the following command to restore the original recovery model of the database.

   Important

   If the recovery model of the database is already FULL, you do not need to perform this step.

   ALTER DATABASE [dbname] SET RECOVERY SIMPLE;
   GO

SQL Server 2012 or later, or SQL Server 2008 R2 with cloud disks

1. Before you upload the backup file to OSS, you must create a bucket in OSS.

   • If a bucket already exists in OSS, ensure that it meets the following requirements:

     • The storage class of the bucket is Standard. Other storage classes, such as Infrequent Access, Archive, Cold Archive, and Deep Cold Archive, are not supported.

     • Server-side encryption is disabled for the bucket.

   • If no bucket exists in OSS, you must create one. (Make sure that you have activated OSS.)

     1. Log on to the OSS console, click Buckets, and then click Create Bucket.

     2. Configure the following key parameters. You can retain the default values for other parameters.

        Important

        • The bucket is created primarily for this data migration. you need to configure only the key parameters. You can delete the bucket after the migration is complete to prevent data breaches and reduce costs.

        • When you create the bucket, do not enable server-side encryption.

        Parameter	Description	Example
        Bucket Name	The name of the bucket. The name must be globally unique and cannot be changed after the bucket is created. Naming conventions: The name can contain only lowercase letters, digits, and hyphens (-). The name must start and end with a lowercase letter or a digit. The name must be 3 to 63 characters in length.	migratetest
        Region	The region where the bucket resides. If you upload data to the bucket from an ECS instance over the internal network and restore the data to an ApsaraDB RDS instance over the internal network, the bucket, ECS instance, and ApsaraDB RDS instance must be in the same region.	China (Hangzhou)
        Storage Class	Select Standard. The migration operation in this topic does not support buckets of other storage classes.	Standard

2. Upload the backup file to OSS.

   After you back up the local database, upload the backup file to an OSS bucket that is in the same region as your ApsaraDB RDS instance. If the bucket and the instance are in the same region, you can use the internal network for service interconnection. This method is free of charge for outbound internet traffic and provides faster data upload speeds. You can use one of the following methods:

   Use ossbrowser to upload the file (recommended)

   1. Download ossbrowser.

   2. The following steps use a Windows x64 operating system as an example. Decompress the downloaded oss-browser-win32-x64.zip package and double-click the oss-browser.exe application.

   3. Select Log On With AK, configure the AccessKeyId and AccessKeySecret parameters, keep the default values for the other parameters, and then click Log On.

      Note

      An AccessKey pair is used for identity verification. Keep your AccessKey pair confidential to ensure data security.

      

   4. Click the destination bucket.

   5. Click , select the backup file that you want to upload, and then click Open. The local file is uploaded to OSS.

   Use the OSS console to upload the file

   Note

   If the backup file is smaller than 5 GB, we recommend that you upload it from the OSS console.

   1. Log on to the OSS console.

   2. Click Buckets and then the name of the destination bucket.

   3. In the Objects list, click Upload Object.

   4. You can drag a backup file to the Files to Upload area, or click Select Files to select a file.

   5. Click the Upload Object button at the bottom of the page to upload a local backup file to OSS.

   Use the OSS API for multipart upload (Python 3 project example)

   Note

   If the backup file is larger than 5 GB, we recommend that you call the OSS API to perform a multipart upload to the OSS bucket.

   # -*- coding: utf-8 -*-
   """
   Alibaba Cloud OSS Python SDK v2
   Dependency: pip install alibabacloud-oss-v2
   """
   
   import os
   import sys
   from pathlib import Path
   import alibabacloud_oss_v2 as oss
   from alibabacloud_oss_v2 import exceptions as oss_ex
   
   
   def get_client_from_env(region: str, endpoint: str | None = None) -> oss.Client:
       """
       Create a v2 client from environment variables.
       - Prioritize using Region (recommended), but also support custom Endpoints (optional).
       - Compatible with both AK and STS:
           * AK: Requires OSS_ACCESS_KEY_ID / OSS_ACCESS_KEY_SECRET
           * STS: Also requires OSS_SESSION_TOKEN (compatible with the old variable OSS_SECURITY_TOKEN)
       """
       # Compatibility: If the user uses the old variable OSS_SECURITY_TOKEN, map it to the v2 expected OSS_SESSION_TOKEN
       sec_token_legacy = os.getenv("OSS_SECURITY_TOKEN")
       if sec_token_legacy and not os.getenv("OSS_SESSION_TOKEN"):
           os.environ["OSS_SESSION_TOKEN"] = sec_token_legacy
   
       ak = os.getenv("OSS_ACCESS_KEY_ID")
       sk = os.getenv("OSS_ACCESS_KEY_SECRET")
       st = os.getenv("OSS_SESSION_TOKEN")  # STS Token (optional)
   
       if not (ak and sk):
           raise ValueError("No valid AK found. Set the OSS_ACCESS_KEY_ID and OSS_ACCESS_KEY_SECRET environment variables. "
                            "If using STS, also set OSS_SESSION_TOKEN (or the old name OSS_SECURITY_TOKEN).")
   
       # Indicate the type of credential used
       if st:
           print("STS Token (OSS_SESSION_TOKEN) detected. Using STS credentials.")
       else:
           print("No STS Token detected. Using AccessKey (AK) credentials.")
   
       credentials_provider = oss.credentials.EnvironmentVariableCredentialsProvider()
       cfg = oss.config.load_default()
       cfg.credentials_provider = credentials_provider
   
       # Basic network configuration
       cfg.region = region  # Example: 'cn-hangzhou'
       if endpoint:
           # Optional: Custom Endpoint (e.g., internal network, accelerated, dedicated domain)
           cfg.endpoint = endpoint
   
       # You can also add other configurations here, such as: cfg.use_accelerate_endpoint = True
       return oss.Client(cfg)
   
   
   def resumable_upload_file_v2(
       client: oss.Client,
       bucket_name: str,
       object_key: str,
       file_path: str,
       part_size: int = 1 * 1024 * 1024,
       parallel_num: int = 4,
       checkpoint_dir: str | None = None,
   ):
       """
       Implement concurrent multipart upload with resumable upload.
   
       :param client: Initialized oss.Client
       :param bucket_name: Destination bucket name
       :param object_key: Destination object key (without bucket name)
       :param file_path: Full path of the local file
       :param part_size: Part size in bytes, default is 1 MB
       :param parallel_num: Number of concurrent upload threads, default is 4
       :param checkpoint_dir: Directory to store breakpoint information; if None, resumable upload is disabled
       """
       file_path = str(file_path)
       if not Path(file_path).exists():
           raise FileNotFoundError(f"Error: Local file not found. Check the file_path configuration: {file_path}")
   
       # Construct the Uploader; enable resumable upload based on whether checkpoint_dir is provided
       if checkpoint_dir:
           uploader = client.uploader(
               enable_checkpoint=True,
               checkpoint_dir=checkpoint_dir,
               part_size=part_size,
               parallel_num=parallel_num,
           )
       else:
           uploader = client.uploader(
               part_size=part_size,
               parallel_num=parallel_num,
           )
   
       print(f"Starting to upload file: {file_path}")
       print(f"Destination Bucket: {bucket_name}")
       print(f"Destination Object: {object_key}")
       print(f"Part size: {part_size} bytes, Concurrency: {parallel_num}")
       if checkpoint_dir:
           print(f"Resumable upload: Enabled (checkpoint_dir={checkpoint_dir})")
       else:
           print("Resumable upload: Disabled (set checkpoint_dir to enable)")
   
       # Execute the upload (Uploader automatically chooses between multi/single part concurrent upload based on size)
       result = uploader.upload_file(
           oss.PutObjectRequest(bucket=bucket_name, key=object_key),
           filepath=file_path,
       )
   
       print("-" * 30)
       print("File uploaded successfully!")
       print(f"HTTP Status: {result.status_code}")
       print(f"ETag: {result.etag}")
       print(f"Request ID: {result.request_id}")
       # CRC-64 checksum; v2 enables data validation by default
       print(f"CRC64: {result.hash_crc64}")
       print("-" * 30)
   
   
   def main():
       # Before running the code example, make sure you have set the corresponding environment variables.
       # macOS/Linux:
       #   AK method:
       #     export OSS_ACCESS_KEY_ID=YOUR_AK_ID
       #     export OSS_ACCESS_KEY_SECRET=YOUR_AK_SECRET
       #   STS method:
       #     export OSS_ACCESS_KEY_ID=YOUR_STS_ID
       #     export OSS_ACCESS_KEY_SECRET=YOUR_STS_SECRET
       #     export OSS_SECURITY_TOKEN=YOUR_STS_TOKEN
       #
       # Windows:
       #   Powershell: $env:OSS_ACCESS_KEY_ID="YOUR_AK_ID"
       #   cmd: set OSS_ACCESS_KEY_ID=YOUR_AK_ID
   
       # ===================== Parameters (modify as needed) =====================
       # Region example: 'cn-hangzhou'; we recommend using Region first
       region = "cn-hangzhou"
   
       # Optional: Custom Endpoint (for internal network, dedicated domain, accelerated domain name, etc.)
       # Example: 'https://oss-cn-hangzhou.aliyuncs.com'
       endpoint = 'https://oss-cn-hangzhou.aliyuncs.com'  
   
       # Bucket and Object
       bucket_name = "examplebucket"
       object_key = "test.bak"
   
       # Full path of the local file to upload.
       # Windows example: r'D:\localpath\examplefile.txt'  (note the r at the beginning)
       # macOS/Linux example: '/Users/test/examplefile.txt'
       file_path = r"D:\oss\test.bak"
   
       # Sharding and concurrency
       part_size = 1 * 1024 * 1024  # Default is 1 MB; OSS requires a minimum part size of 100 KB
       parallel_num = 4
   
       # Resumable upload directory (pass None to disable; we recommend specifying a writable directory)
       checkpoint_dir = str(Path.cwd() / ".oss_checkpoints")
       # =================== End of parameters ===================
   
       print("Script execution starts...")
       try:
           client = get_client_from_env(region=region, endpoint=endpoint)
           # If resumable upload is enabled, make sure the directory exists
           if checkpoint_dir:
               Path(checkpoint_dir).mkdir(parents=True, exist_ok=True)
   
           resumable_upload_file_v2(
               client=client,
               bucket_name=bucket_name,
               object_key=object_key,
               file_path=file_path,
               part_size=part_size,
               parallel_num=parallel_num,
               checkpoint_dir=checkpoint_dir,
           )
       except FileNotFoundError as e:
           print(e)
       except oss_ex.ServiceError as e:
           # Error returned by the OSS server
           print("\nAn OSS server-side error occurred.")
           print(f"HTTP Status: {getattr(e, 'status_code', 'N/A')}")
           print(f"Error Code: {getattr(e, 'code', 'N/A')}")
           print(f"Message: {getattr(e, 'message', 'N/A')}")
           print(f"Request ID: {getattr(e, 'request_id', 'N/A')}")
           print(f"Endpoint: {getattr(e, 'request_target', 'N/A')}")
       except oss_ex.BaseError as e:
           # SDK local/serialization/deserialization/credential errors
           print("\nAn OSS SDK client-side error occurred.")
           print(str(e))
       except Exception as e:
           print(f"\nAn unknown error occurred: {e}")
   
   
   if __name__ == "__main__":
       main()

SQL Server 2008 R2 with high-performance local disks

1. Before you upload the backup file to OSS, you must create a bucket in OSS.

   • If a bucket already exists in OSS, ensure that it meets the following requirements:

     • The storage class of the bucket is Standard. Other storage classes, such as Infrequent Access, Archive, Cold Archive, and Deep Cold Archive, are not supported.

     • Server-side encryption is disabled for the bucket.

   • If no bucket exists in OSS, you must create one. (Make sure that you have activated OSS.)

     1. Log on to the OSS console, click Buckets, and then click Create Bucket.

     2. Configure the following key parameters. You can retain the default values for other parameters.

        Important

        • The bucket is created primarily for this data migration. you need to configure only the key parameters. You can delete the bucket after the migration is complete to prevent data breaches and reduce costs.

        • When you create the bucket, do not enable server-side encryption.

        Parameter	Description	Example
        Bucket Name	The name of the bucket. The name must be globally unique and cannot be changed after the bucket is created. Naming conventions: The name can contain only lowercase letters, digits, and hyphens (-). The name must start and end with a lowercase letter or a digit. The name must be 3 to 63 characters in length.	migratetest
        Region	The region where the bucket resides. If you upload data to the bucket from an ECS instance over the internal network and restore the data to an ApsaraDB RDS instance over the internal network, the bucket, ECS instance, and ApsaraDB RDS instance must be in the same region.	China (Hangzhou)
        Storage Class	Select Standard. The migration operation in this topic does not support buckets of other storage classes.	Standard

2. Upload the backup file to OSS.

   After you back up the local database, upload the backup file to an OSS bucket that is in the same region as your ApsaraDB RDS instance. If the bucket and the instance are in the same region, you can use the internal network for service interconnection. This method is free of charge for outbound internet traffic and provides faster data upload speeds. You can use one of the following methods:

   Use ossbrowser to upload the file (recommended)

   1. Download ossbrowser.

   2. The following steps use a Windows x64 operating system as an example. Decompress the downloaded oss-browser-win32-x64.zip package and double-click the oss-browser.exe application.

   3. Select Log On With AK, configure the AccessKeyId and AccessKeySecret parameters, keep the default values for the other parameters, and then click Log On.

      Note

      An AccessKey pair is used for identity verification. Keep your AccessKey pair confidential to ensure data security.

      

   4. Click the destination bucket.

   5. Click , select the backup file that you want to upload, and then click Open. The local file is uploaded to OSS.

   Use the OSS console to upload the file

   Note

   If the backup file is smaller than 5 GB, we recommend that you upload it from the OSS console.

   1. Log on to the OSS console.

   2. Click Buckets and then the name of the destination bucket.

   3. In the Objects list, click Upload Object.

   4. You can drag a backup file to the Files to Upload area, or click Select Files to select a file.

   5. Click the Upload Object button at the bottom of the page to upload a local backup file to OSS.

   Use the OSS API for multipart upload (Python 3 project example)

   Note

   If the backup file is larger than 5 GB, we recommend that you call the OSS API to perform a multipart upload to the OSS bucket.

   # -*- coding: utf-8 -*-
   """
   Alibaba Cloud OSS Python SDK v2
   Dependency: pip install alibabacloud-oss-v2
   """
   
   import os
   import sys
   from pathlib import Path
   import alibabacloud_oss_v2 as oss
   from alibabacloud_oss_v2 import exceptions as oss_ex
   
   
   def get_client_from_env(region: str, endpoint: str | None = None) -> oss.Client:
       """
       Create a v2 client from environment variables.
       - Prioritize using Region (recommended), but also support custom Endpoints (optional).
       - Compatible with both AK and STS:
           * AK: Requires OSS_ACCESS_KEY_ID / OSS_ACCESS_KEY_SECRET
           * STS: Also requires OSS_SESSION_TOKEN (compatible with the old variable OSS_SECURITY_TOKEN)
       """
       # Compatibility: If the user uses the old variable OSS_SECURITY_TOKEN, map it to the v2 expected OSS_SESSION_TOKEN
       sec_token_legacy = os.getenv("OSS_SECURITY_TOKEN")
       if sec_token_legacy and not os.getenv("OSS_SESSION_TOKEN"):
           os.environ["OSS_SESSION_TOKEN"] = sec_token_legacy
   
       ak = os.getenv("OSS_ACCESS_KEY_ID")
       sk = os.getenv("OSS_ACCESS_KEY_SECRET")
       st = os.getenv("OSS_SESSION_TOKEN")  # STS Token (optional)
   
       if not (ak and sk):
           raise ValueError("No valid AK found. Set the OSS_ACCESS_KEY_ID and OSS_ACCESS_KEY_SECRET environment variables. "
                            "If using STS, also set OSS_SESSION_TOKEN (or the old name OSS_SECURITY_TOKEN).")
   
       # Indicate the type of credential used
       if st:
           print("STS Token (OSS_SESSION_TOKEN) detected. Using STS credentials.")
       else:
           print("No STS Token detected. Using AccessKey (AK) credentials.")
   
       credentials_provider = oss.credentials.EnvironmentVariableCredentialsProvider()
       cfg = oss.config.load_default()
       cfg.credentials_provider = credentials_provider
   
       # Basic network configuration
       cfg.region = region  # Example: 'cn-hangzhou'
       if endpoint:
           # Optional: Custom Endpoint (e.g., internal network, accelerated, dedicated domain)
           cfg.endpoint = endpoint
   
       # You can also add other configurations here, such as: cfg.use_accelerate_endpoint = True
       return oss.Client(cfg)
   
   
   def resumable_upload_file_v2(
       client: oss.Client,
       bucket_name: str,
       object_key: str,
       file_path: str,
       part_size: int = 1 * 1024 * 1024,
       parallel_num: int = 4,
       checkpoint_dir: str | None = None,
   ):
       """
       Implement concurrent multipart upload with resumable upload.
   
       :param client: Initialized oss.Client
       :param bucket_name: Destination bucket name
       :param object_key: Destination object key (without bucket name)
       :param file_path: Full path of the local file
       :param part_size: Part size in bytes, default is 1 MB
       :param parallel_num: Number of concurrent upload threads, default is 4
       :param checkpoint_dir: Directory to store breakpoint information; if None, resumable upload is disabled
       """
       file_path = str(file_path)
       if not Path(file_path).exists():
           raise FileNotFoundError(f"Error: Local file not found. Check the file_path configuration: {file_path}")
   
       # Construct the Uploader; enable resumable upload based on whether checkpoint_dir is provided
       if checkpoint_dir:
           uploader = client.uploader(
               enable_checkpoint=True,
               checkpoint_dir=checkpoint_dir,
               part_size=part_size,
               parallel_num=parallel_num,
           )
       else:
           uploader = client.uploader(
               part_size=part_size,
               parallel_num=parallel_num,
           )
   
       print(f"Starting to upload file: {file_path}")
       print(f"Destination Bucket: {bucket_name}")
       print(f"Destination Object: {object_key}")
       print(f"Part size: {part_size} bytes, Concurrency: {parallel_num}")
       if checkpoint_dir:
           print(f"Resumable upload: Enabled (checkpoint_dir={checkpoint_dir})")
       else:
           print("Resumable upload: Disabled (set checkpoint_dir to enable)")
   
       # Execute the upload (Uploader automatically chooses between multi/single part concurrent upload based on size)
       result = uploader.upload_file(
           oss.PutObjectRequest(bucket=bucket_name, key=object_key),
           filepath=file_path,
       )
   
       print("-" * 30)
       print("File uploaded successfully!")
       print(f"HTTP Status: {result.status_code}")
       print(f"ETag: {result.etag}")
       print(f"Request ID: {result.request_id}")
       # CRC-64 checksum; v2 enables data validation by default
       print(f"CRC64: {result.hash_crc64}")
       print("-" * 30)
   
   
   def main():
       # Before running the code example, make sure you have set the corresponding environment variables.
       # macOS/Linux:
       #   AK method:
       #     export OSS_ACCESS_KEY_ID=YOUR_AK_ID
       #     export OSS_ACCESS_KEY_SECRET=YOUR_AK_SECRET
       #   STS method:
       #     export OSS_ACCESS_KEY_ID=YOUR_STS_ID
       #     export OSS_ACCESS_KEY_SECRET=YOUR_STS_SECRET
       #     export OSS_SECURITY_TOKEN=YOUR_STS_TOKEN
       #
       # Windows:
       #   Powershell: $env:OSS_ACCESS_KEY_ID="YOUR_AK_ID"
       #   cmd: set OSS_ACCESS_KEY_ID=YOUR_AK_ID
   
       # ===================== Parameters (modify as needed) =====================
       # Region example: 'cn-hangzhou'; we recommend using Region first
       region = "cn-hangzhou"
   
       # Optional: Custom Endpoint (for internal network, dedicated domain, accelerated domain name, etc.)
       # Example: 'https://oss-cn-hangzhou.aliyuncs.com'
       endpoint = 'https://oss-cn-hangzhou.aliyuncs.com'  
   
       # Bucket and Object
       bucket_name = "examplebucket"
       object_key = "test.bak"
   
       # Full path of the local file to upload.
       # Windows example: r'D:\localpath\examplefile.txt'  (note the r at the beginning)
       # macOS/Linux example: '/Users/test/examplefile.txt'
       file_path = r"D:\oss\test.bak"
   
       # Sharding and concurrency
       part_size = 1 * 1024 * 1024  # Default is 1 MB; OSS requires a minimum part size of 100 KB
       parallel_num = 4
   
       # Resumable upload directory (pass None to disable; we recommend specifying a writable directory)
       checkpoint_dir = str(Path.cwd() / ".oss_checkpoints")
       # =================== End of parameters ===================
   
       print("Script execution starts...")
       try:
           client = get_client_from_env(region=region, endpoint=endpoint)
           # If resumable upload is enabled, make sure the directory exists
           if checkpoint_dir:
               Path(checkpoint_dir).mkdir(parents=True, exist_ok=True)
   
           resumable_upload_file_v2(
               client=client,
               bucket_name=bucket_name,
               object_key=object_key,
               file_path=file_path,
               part_size=part_size,
               parallel_num=parallel_num,
               checkpoint_dir=checkpoint_dir,
           )
       except FileNotFoundError as e:
           print(e)
       except oss_ex.ServiceError as e:
           # Error returned by the OSS server
           print("\nAn OSS server-side error occurred.")
           print(f"HTTP Status: {getattr(e, 'status_code', 'N/A')}")
           print(f"Error Code: {getattr(e, 'code', 'N/A')}")
           print(f"Message: {getattr(e, 'message', 'N/A')}")
           print(f"Request ID: {getattr(e, 'request_id', 'N/A')}")
           print(f"Endpoint: {getattr(e, 'request_target', 'N/A')}")
       except oss_ex.BaseError as e:
           # SDK local/serialization/deserialization/credential errors
           print("\nAn OSS SDK client-side error occurred.")
           print(str(e))
       except Exception as e:
           print(f"\nAn unknown error occurred: {e}")
   
   
   if __name__ == "__main__":
       main()

3. Set the validity period for the backup file link and obtain the URL of the file.

   1. Log on to the OSS console.

   2. Click Buckets. Then, click the name of the destination bucket.

   3. In the navigation pane on the left, select File Management > Files.

   4. In the Actions column for the destination database backup file, click Details. In the panel that appears, set Expiration (Seconds) to 28800 (8 hours).

      Important

      When you migrate a backup file from OSS to ApsaraDB RDS, you must use the URL of the backup file. The data migration fails if the link expires.

   5. Click Copy File URL to copy the file URL.

      

   6. Modify the obtained URL of the data backup file.

      By default, the public endpoint of the file is retrieved. To migrate data over the internal network, you must change the endpoint in the file URL to an internal endpoint.

      For example, if the URL of the backup file is http://rdstest.oss-cn-shanghai.aliyuncs.com/testmigraterds_20170906143807_FULL.bak?Expires=15141****&OSSAccessKeyId=TMP****, you must change oss-cn-shanghai.aliyuncs.com in the URL to oss-cn-shanghai-internal.aliyuncs.com.

      Important

      The internal endpoint varies based on the network type and region. For more information, see Endpoints and data centers.

SQL Server 2012 or later, or SQL Server 2008 R2 with cloud disks

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 navigation pane on the left, click Backup and Restoration.

3. At the top of the page, click the Migrate OSS Backup Data to RDS button.

4. In the Import Guide, click Next twice to proceed to the data import step.

   Note

   • When you use the Restore from OSS Backup feature for the first time, you must authorize ApsaraDB RDS to access OSS. Click the Authorization URL and grant the required permissions. If this authorization is not granted, the OSS Bucket drop-down list will be empty.

   • If you cannot find the destination file on this page, check whether the file name extension of the backup file in OSS meets the requirements. For more information, see the Notes section of this topic. Also, make sure that the ApsaraDB RDS instance and the OSS bucket are in the same region.

5. Set the following parameters.

   Configuration item	Description
   Database Name	Enter the name of the destination database on your RDS instance. The destination database is used to store the data that is migrated from the source database on the self-managed SQL Server instance. The name of the destination database must meet the requirements of open source SQL Server. Important Before migration, you must make sure that the names of the databases on the destination RDS instance are different from the name of the database that you want to restore by using the specified backup file. In addition, make sure that database files with the same name as the database that you want to restore by using the specified backup file are not added to the databases on the destination RDS instance. If both preceding requirements are met, you can restore the database by using a database file in the backup set. Note that the database file must have the same name as the database that you want to restore. If a database with the same name as the database specified in the backup file already exists on the destination instance, or if there are unattached database files with the same name, the restoration operation will fail.
   OSS Bucket	Select the OSS bucket where the backup file is stored.
   OSS File	Click the button on the right to perform a fuzzy search by the prefix of the backup file name. The file name, file size, and update time are displayed. Select the backup file that you want to migrate.
   Cloud Migration Method	Immediate Access (Full Backup): This option is for full migration and is suitable for scenarios where only one full backup file is migrated. In this case, select Immediate Access (Full Backup). The BackupMode parameter in the CreateMigrateTask operation is set to FULL, and the IsOnlineDB parameter is set to True. Access Pending (Incremental Backup): This option is for incremental migration and is suitable for scenarios where a full backup file plus log backups (or differential backup files) are migrated. In this case, the BackupMode parameter in the CreateMigrateTask operation is set to UPDF, and the IsOnlineDB parameter is set to False.
   Consistency Check Mode	Asynchronous DBCC: The system does not run DBCC CheckDB when opening the database. Instead, it asynchronously runs DBCC CheckDB after the database is opened. This reduces the time overhead of opening the database (DBCC CheckDB is very time-consuming for large databases) and minimizes your business downtime. If you are highly sensitive to business downtime and do not care about the DBCC CheckDB result, we recommend that you use this option. In this case, the CheckDBMode parameter in the CreateMigrateTask operation is set to AsyncExecuteDBCheck. Synchronous DBCC: Compared with asynchronous execution, some users are very concerned about the DBCC CheckDB result to identify data consistency errors in their on-premises databases. In this case, we recommend that you select this option. The impact is that it will prolong the time it takes to open the database. In this case, the CheckDBMode parameter in the CreateMigrateTask operation is set to SyncExecuteDBCheck.

6. Click OK.

   Wait for the migration task to complete. You can click Refresh to check the task status. If the task fails, use its description to troubleshoot the error. For more information, see the Common errors section of this topic.

   Note

   After data migration is complete, the system backs up the ApsaraDB RDS instance at the specified backup time based on the automatic backup policy. You can manually adjust the backup time. The resulting backup set contains the migrated data and is available on the Backup and Restoration page of the ApsaraDB RDS instance.

   To generate a backup in the cloud before the scheduled backup time, you can also perform a manual backup.

SQL Server 2008 R2 with high-performance local disks

1. Log on to the ApsaraDB RDS console and 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 Databases.

3. For the destination database, click Migrate Backup Files from OSS in the Actions column.

   

4. In the Import Guide dialog box, review the information and click Next.

5. Review the prompts for the OSS upload and click Next.

6. In the OSS URL of Backup File field, enter the OSS URL of the backup file and click OK.

   

   Note

   ApsaraDB RDS for SQL Server 2008 R2 instances with high-performance local disks support only a one-time import of a full backup file.

SQL Server 2012 or later, or SQL Server 2008 R2 with cloud disks

Go to the Backup and Restoration page of the ApsaraDB RDS instance. On the Cloud Migration Records of Backup Data tab, you can view the migration records, including the task status, start time, and end time. By default, records from the last week are displayed. You can adjust the time range as needed.

SQL Server 2008 R2 with high-performance local disks

On the Data Migration To Cloud page of the ApsaraDB RDS instance, find the destination migration task to view its progress.