Relational Database ServiceRelational Database Service

Compute
Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Anti-DDoS
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Compass
Cloud Certificate Manager
Anti-DDoS Service
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB NoSQL
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
ServiceStage
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
Blockchain
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
DevCloud
ProjectMan
CodeHub
CloudRelease
CloudPipeline
CloudBuild
CloudDeploy
Cloud Communications
Message & SMS
Cloud Ecosystem
Marketplace
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
enterprise-collaboration
Meeting
IoT
IoT
Intelligent EdgeFabric
DeveloperTools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Updated at: Apr 02, 2022 GMT+08:00

Cloning a DB Instance

Scenarios

Cloning a DB instance means cloning the service data of a primary DB instance within about half an hour, so that you can analyze the data without interrupting services.

The primary DB instance is accessible while being cloned. Data inherited by the cloned instance is the same as that of the primary DB instance from when the cloning action began. If you want a cloned instance that has the same data as the original after the cloning completes, disable access to the primary DB instance before starting to clone the instance.

Constraints

  • You can clone a DB instance only when your account balance is greater than or equal to $0 USD.
  • To clone a DB instance, you need to contact customer service to apply for the required permissions.
  • If the primary DB instance is kept accessible while being cloned, data inherited by the cloned instance will match that of the source instance from when the cloning began, not from when it finished.
  • The storage type and space of the new instance must be the same as those of the primary DB instance.
  • The AZ of the new instance must be the same as that of the primary DB instance.
  • The parameter template, DB engine version, and DB instance type of the new instance must be the same as those of the primary DB instance.
  • Microsoft SQL Server 2008 R2 Standard Edition and read replicas do not support instance cloning.
  • The following operations cannot be performed on a cloning primary DB instance:
    • Changing the instance class
    • Scaling up the storage space
    • Enabling Transparent Data Encryption (TDE)
    • Enabling or disabling FileStream
    • Migrating data
    • Restoring data to the primary DB instance
    • Modifying MSDTC configurations
    • Deleting the primary DB instance
    • Switching over the primary and standby DB instances
    • Resetting a password
    • Binding or unbinding an EIP
    • Changing DB instance type from single to primary/standby
    • Upgrading the version

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Database > Relational Database Service. The RDS console is displayed.
  4. On the Instance Management page, locate the DB instance to be cloned and choose More > Clone in the Operation column.
  5. On the displayed page, keep the configurations the same as the original DB instance or change them as required. Then, click Next.

    For details about how to configure a Microsoft SQL Server DB instance, see Buying a DB Instance.

  6. Confirm the instance configurations.

    • For pay-per-use DB instances, click Submit.
    • For yearly/monthly DB instances, click Pay Now.

  7. Refresh the DB instance list and check the clone result. If the status of the new instance is Available, the clone was successful.

    You can manage the cloned instance on the Instance Management page.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel