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
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/ Server Migration Service/ User Guide (Kuala Lumpur Region)/ FAQs/ Product Consulting/ How Do I Verify Data Consistency Between the Source and Target Servers?

How Do I Verify Data Consistency Between the Source and Target Servers?

Updated on 2024-03-15 GMT+08:00

SMS consistency verification allows you to verify data consistency before and after the migration. You can enable this function when you start an incremental synchronization.

Precautions

  • Before enabling this function, you are advised to stop services (and databases if any) on the source server. If they are not stopped, data on the source server keeps changing, which will affect the consistency.
    NOTE:

    It is normal for some directories on the source and target servers to have slight differences. For instance, there are directories on the source server where data is always changing, such as the directory where SMS-Agent was installed and the /var/log directory where stores system logs.

  • The time required for consistency verification depends on the number and size of files to be verified. If consistency verification takes a long time during the final incremental synchronization, the time required for service cutover will also increase. Evaluate the impact on your services.
  • Consistency verification occupies significant source disk I/O resources. Evaluate the potential impacts on your source services.

Constraints

  • Consistency verification does not apply to migration scenarios where disks or partitions are adjusted. In this case, directories and paths on the source and target servers are not perfectly mapped to each other.
  • It is not applicable to verification of cross-file system files or shared folders.
  • To ensure your services can run normally on the source server, a maximum of 100,000 files can be verified in a single directory.
  • To prevent excessive memory usage, only files whose paths do not exceed 1024 bytes are verified.

Enabling Consistency Verification

  1. Open the Sync Incremental Data dialog box by referring to section Synchronizing Incremental Data.
  2. Enable Verify Consistency and correctly enter the directories for which data consistency is to be verified. If the entered directories are incorrect or empty, 0 will be displayed for these directories in the verification results.

    NOTICE:
    • The larger the amount of data to be verified, the longer the consistency verification goes on. You are advised to verify only key directories.
    • The following directories will be excluded from consistency verification by default:
      • /, /etc, /dev, /sys, /usr, /boot, and /run in Linux
      • Root directories of partitions in Windows, for example, C:\ and D:\.

  3. Select a verification method.

    • Quick verification: compares the file size and last modification time.
    • CRC verification: compares CRC64 checksums. This method scans file content in binary mode, which occupies a large amount of disk I/O resources and takes a long time but is more accurate.

  4. (Optional) Enable Verify Inconsistencies to verify files that were verified to be inconsistent in the previous verification. This option can only be enabled after at least one consistency verification is complete.
  5. Click Yes to synchronize incremental data and verify consistency. After the synchronization and verification are complete, you can view the verification results by referring to Viewing Verification Results.

Disabling Consistency Verification

If you want to disable consistency verification after the incremental synchronization starts, perform the following steps:

  1. Choose More > Pause in the Operation column to pause the synchronization task.
  2. Click Start in the Operation column.
  3. In the displayed dialog box, disable Verify Consistency and click Yes.

Viewing Verification Results

To view the data consistency verification results, choose More > View Verification Results in the Operation column.

If 0 is displayed in the Files Verified column, it means the specified directory could not be found or is empty.

All files verified to be inconsistent are recorded in the log file sms_cmp_result.log in the SMS-Agent installation directory (*/SmsAgent/agent/Logs/ on Linux and C://SMS-Agent-Py*/Logs on Windows) on the source server.

Verification Time Estimation

The following table lists the verification time tested on servers where only the migration process runs but is for reference only.

OS

Specifications

Disk Performance

Verification Time (per 100 GB)

Windows

2 vCPUs and 4 GB of memory

5,000 IOPS/150 MB/s

About 17 minutes

Linux

2 vCPUs and 4 GB of memory

5,000 IOPS/150 MB/s

About 13 minutes

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