Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Data Replication Service/ Backup Migration/ Creating an RDS Backup Migration Task

Creating an RDS Backup Migration Task

Updated on 2024-11-30 GMT+08:00

Supported Source and Destination Databases

Table 1 Supported databases

Source DB

Destination DB

RDS for SQL Server full backup file versions:

  • Microsoft SQL Server 2008 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2012 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2014 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2016 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2017 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2019 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2022 Enterprise Edition, Standard Edition, and Web Edition

RDS for SQL Server

  • Microsoft SQL Server 2008 Enterprise Edition, Standard Edition, and Web Edition (Existing versions)
  • Microsoft SQL Server 2012 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2014 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2016 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2017 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2019 Enterprise Edition, Standard Edition, and Web Edition
  • Microsoft SQL Server 2022 Enterprise Edition, Standard Edition, and Web Edition
NOTE:
  • The major version of the destination database must be the same as or later than that of the source database.
  • The edition of the destination database must be the same as or later than that of the source database, for example, from Web Edition to Standard Edition, from Standard Edition to Enterprise Edition, or from Enterprise Edition to Enterprise Edition.

Prerequisites

Before Backing Up File

Learn the backup migration constraints before starting a migration task.

Table 2 Before Backing Up File

Scenario

Preparations

RDS full backup files

The source Microsoft SQL Server DB instance has full backups. If there are no full backups, create a full backup for the DB instance. For details, see Creating a Manual Backup in Relational Database Service User Guide.

Precautions

This section describes constraints on backup migrations of Microsoft SQL Server databases.

Table 3 Precautions

Type

Restrictions

Database permissions

Before creating a backup migration task, ensure that the account has the permission to operate the RDS service.

For details about RDS permissions and operations, see RDS Service Overview.

Backup database names

  • Backup database names are case-insensitive, must be unique, and cannot be any of the following:
    • msdb
    • master
    • model
    • tempdb
    • rdsadmin
    • resource

New database name

  • The new database name must be unique and cannot be any of the following (case-insensitive):
    • msdb
    • master
    • model
    • tempdb
    • rdsadmin
    • resource
  • The new database name contains 1 to 64 characters, including letters, digits, underscores (_), hyphens (-), and periods (.).

Backup file sources

  • RDS full backups: Backup files are manually or automatically created for RDS DB instances.

Precautions

  • The available disk space of the destination database is at least 1.5 times the total data size of the backup database.
  • Backup database name is case-sensitive and must be the same as the database name in the backup file.
  • Backup migration is not supported for a source database with TDE enabled.
  • The database backup file from a database of later version cannot be restored on the instance database of an earlier version (for example, restored from version 2017 to 2016).
  • The restoration from Enterprise Edition to Standard Edition to Web Edition may fail. That depends on whether the features of the later version are enabled.
  • During a migration, if Overwrite Data is set to Yes, high availability of the destination database is disabled by default. After the migration is complete, high availability is restored automatically.
  • During a migration, stop writing transactions to the destination database.
  • If a primary/standby switchover of the destination database is performed, the backup migration fails. In this case, the migration task cannot be restored.

Procedure

This section describes how to create an RDS full backup migration task. You can use the full backups of Microsoft SQL Server DB instances in the cloud to migrate data.

  1. On the Backup Migration Management page, click Create Migration Task.
  2. On the Select Backup page, specify information about the task and backup files. Then, click Next.

    Figure 1 Task information
    Table 4 Task information

    Parameter

    Description

    Region

    The region where your service is running. You can change the region. To reduce latency and improve access speed, select the region closest to your services.

    Project

    The project corresponds to the current region and can be changed.

    Task Name

    The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

    Description

    The description can contain up to 256 characters and cannot contain special characters !=<>&'\"

    Figure 2 Backup file information
    Table 5 Backup file information

    Parameter

    Description

    Database Type

    Select Microsoft SQL Server.

    Backup File Source

    Select RDS full backup.

    NOTE:

    Select a backup file whose status is Completed.

    Enterprise Project

    An enterprise project you would like to use to centrally manage your cloud resources and members. Select an enterprise project from the drop-down list. The default project is default.

    For more information about enterprise projects, see Enterprise Management User Guide.

    To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Project Management Service page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.

    Tags

    • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
    • If your organization has configured tag policies for DRS, add tags to tasks based on the policies. If a tag does not comply with the policies, task creation may fail. Contact your organization administrator to learn more about tag policies.
    • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.

  3. On the Select Destination page, specify database information and click Next.

    Figure 3 Database information
    Table 6 Database information

    Parameter

    Description

    Destination RDS DB Instance Name

    Select a destination RDS DB instance.

    Backup Database Name

    After you select the destination RDS DB instance, all databases to be restored are automatically displayed. You can select databases to be restored as required and rename them.

    • Backup Database Name: Name of the database to be restored.
    • New Database Name: The backup database name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.). If the name is not specified, the original database name is used.
    NOTE:
    • The backup database can be renamed. A maximum of 100 backup databases can be created.
    • The new database name cannot be the same as the name of any other database in the source.

  4. On the Confirm Task page, check configuration details, read and agree to the agreement, and click Next.

    NOTE:

    If the SQL Server source contains non-clustered index tables, the index information of non-clustered index tables will become invalid after the SQL Server backups are restored to a new database. For the best performance, rebuild the indexes after the backup migration. In addition, the backup files store only database-level information. If the SQL Server source contains some instance-level configurations, such as login, permission, DBlink, and job, migrate these configurations by referring to Best Practices.

  5. In the task list on the Backup Migration Management page, check whether the task is in the Restoring status. If the migration is successful, the task status becomes Successful.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback