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
On this page

Show all

Troubleshooting Data Migration Failures

Updated on 2024-07-29 GMT+08:00

When you use the console to migrate data, the migration may fail if you select an inappropriate migration scheme, the SYNC and PSYNC commands are not allowed on the source Redis instance, or the network between the source and target Redis instances is disconnected.

This section describes how to troubleshoot data migration failures on the DCS console.

Procedure

  1. Check the migration logs.

    • If the following error information is displayed, the underlying resources are insufficient to support the migration task. In this case, contact technical support.
      create migration ecs failed, flavor
    • If the following error information is displayed, the SYNC and PSYNC commands are disabled on the source Redis instance. In this case, contact technical support to enable the commands.
      source redis unsupported command: psync

  2. Check whether you used the appropriate migration scheme. If you migrate data between DCS Redis instances, the source instance cannot be a higher version than the target instance.
  3. Check whether the SYNC and PSYNC commands are enabled on the source Redis instance and whether the underlying resources of the migration task are connected to the source and target Redis instances.

    This operation is required only for online migration.

    For online migration, the source and target Redis instances must be connected, and the SYNC and PSYNC commands must be enabled on the source Redis instance. Otherwise, the migration will fail.

    • Check the network.

      Check whether the source Redis instance, the target Redis instance, and the VMs used for the migration task are in the same VPC. If they are in different VPCs, create a VPC peering connection. For details, see "VPC Peering Connection" in the Virtual Private Cloud User Guide.

      If they are in the same VPC, check the security group rules (for DCS Redis 3.0 instances) or whitelists (for DCS Redis 4.0/5.0/6.0 instances) to ensure that the IP addresses and ports of the Redis instances are accessible.

      The source and target Redis instances must be accessible to the underlying VMs used for the migration task. For details about how to configure a security group or whitelist, see Security Group Configurations and Managing IP Address Whitelist.

      If the source and target Redis instances are on different clouds, create a Direct Connect connection.

    • Check the commands.
      By default, the SYNC and PSYNC commands are disabled by cloud vendors. To enable the commands, contact the O&M personnel of the cloud vendors.
      • Migration within DCS:
        • By default, the SYNC and PSYNC commands can be used when self-hosted Redis is migrated to DCS.
        • During online migration between DCS instances in the same region under the same account, the SYNC and PSYNC commands are automatically enabled.
        • During online migration between DCS instances in different regions or under different accounts within a region, the SYNC and PSYNC commands are not automatically enabled, and online migration on the console cannot be used. You can migrate data using backup files instead.
      • Migration from other cloud vendors to DCS:
        • Generally, cloud vendors disable the SYNC and PSYNC commands. If you want to use online migration, contact the O&M personnel of the source cloud vendor to enable the commands. For offline migration, you can import backup files.
        • If incremental migration is not required, you can perform full migration by referring to Online Full Migration of Redis from Another Cloud with redis-shake. This method does not depend on SYNC and PSYNC.

  4. Check the source Redis instance for big keys.

    If the source Redis instances has big keys, split them into small keys before migration.

  5. Check the specifications of the target Redis instance and whether other tasks are being performed on the instance.

    If the memory of the target Redis instance is smaller than the size of the data to be migrated, the memory will be used up during the migration and the migration will fail.

    If a master/standby switchover is being performed on the target Redis instance, contact technical support to stop the master/standby switchover task and start it only after the data migration is completed.

  6. Check whether the migration task is performed correctly.

    Check whether the IP address and the instance password are correct.

  7. Check the whitelist.
  8. If the fault persists, contact technical support.

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