In a Linux File-Level Migration, How Do I Exclude Specific Directories from Migration and Synchronization?
Scenario
When you migrate a Linux server using the file-level migration method, you can exclude certain files or directories from a full migration. You can also include or exclude certain files or directories from the incremental synchronization.
Procedure
- Log in to the SMS console.
- In the navigation pane on the left, choose Servers.
- In the server list, locate the source server to be migrated and click Configure Target in the Migration Stage/Status column.
- On the Configure Basic Settings tab page, select Configure now next to Advanced Settings to expand advanced settings.
- At the bottom of the page, select Configure now next to Advanced Options.
- Configure Exclude Migration Paths, Exclude Sync Paths, and Include Sync Paths by referring to the following table. You can specify which directories and files to be excluded, for example, /root/data/path,/data/file.txt.
Table 1 Parameter description Parameter
Description
Remarks
Exclude Migration Paths
Excludes directories or files you do not want to migrate from the full migration.
- Absolute paths are required.
- SMS does not check whether the configured paths can be found. You check that yourself.
- Use commas (,) to separate multiple paths.
- The Exclude Migration Paths settings will become invalid in incremental synchronizations. If you do not want to synchronize these directories or files, add the absolute paths to Exclude Sync Paths.
- You can configure both Exclude Sync Paths and Include Sync Paths. Exclude Sync Paths overrides Include Sync Paths. If a path is configured for Exclude Sync Paths and Include Sync Paths, Exclude Sync Paths takes precedence, and the path will not be synchronized.
Include Sync Paths
Includes the directories and files you want to synchronize in incremental synchronizations. Other directories and files will be skipped during synchronizations.
Exclude Sync Paths
Excludes the directories and files you do not want to synchronize from incremental synchronizations. Data in the excluded paths will not be synchronized.
Modifying Advanced Options
You can only modify the advanced migration options if a task has the target server configured but is not started, is paused, or is waiting to execute an incremental synchronization. After locating the task, in the Operation column, choose More > Manage Migration Settings > Configure Advanced Options. Then you can modify the settings of Data Compression, Compression Threads, and Cache Node Size.
Product Consultation FAQs
- Can I Migrate Servers from Other Clouds to Huawei Cloud Using SMS?
- Can I Migrate ECSs from Huawei Cloud to On-Premises Environments or Other Clouds Using SMS?
- Can I Ask Huawei Cloud Technical Support to Help Me Migrate Services?
- Can I Migrate Workloads to a DeH, DeC, Kunpeng ECS, or BMS Using SMS?
- Does SMS Support Resumable Data Transfer?
- How Do I Migrate an ECS from One Account to Another Using SMS?
- How Do I Migrate an ECS from One Region to Another Using SMS?
- Will My Services on the Source Server Be Interrupted During Migration?
- How Do I Obtain an AK/SK Pair for a Huawei Cloud Account?
- How Do I Obtain an AK/SK Pair for an IAM User?
- How Do I Migrate a Linux Source Server as a Non-root User?
- What Information Does SMS Collect About Source Servers?
- How Do I Select a Target Server?
- How Do I Create an ECS?
- What Is Block-Level Migration?
- What are Valid Data Blocks?
- How Does Migration Using SMS Differ from Migration Using IMS?
- Why Is the OS Name of the Target ECS Displayed on the ECS Console Different from That of the Source Server?
- How Do I Determine Whether a Migration Is Complete?
- Can I Migrate Only Some Workloads from a Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- How Do I Download the SMS-Agent for Windows and the SHA256 Verification File?
- Can I Migrate a Source Server If There Is No Corresponding Image Available on Huawei Cloud?
- How Does SMS Differ from IMS in the Migration Scenario?
- How Do I Display the OS Name of a Target Server on the ECS Console?
- What Are the Snapshots of a Target Server Used for?
- In a Linux File-Level Migration, How Do I Exclude Specific Directories from Migration and Synchronization?
- Will an Incremental Synchronization Overwrite Existing Data on a Launched Target Server?
- How Do I Create a Target Server That Meets the SMS Requirements?
- Can I Use SMS to Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can I Use an AK/SK Pair of a Federated User (Virtual IAM User) for Authentication During the SMS-Agent Startup?
- How Do I Synchronize Data in Specific Directories After a Linux File-Level Migration Is Complete?
- Will the Migration Be Affected If the SSH Service Does Not Use Default Port 22 on the Source Server?
- How Do I Obtain the SMS Domain Name?
- How Many Resources Will Be Used for a Linux Block-Level Migration?
- How Do I Configure Data Compression for a Linux Block-Level Migration?
- Do I Need to Activate the Windows OS and Paid Software After the Migration Is Complete?
- What Do I Do If the Source Server's Clocks Are Not Synchronized to the Target Server?
- How Do I Set the Number of Concurrent Processes for Linux File-Level Migrations?
- Which Directories Are Not Synchronized by Default During Incremental Synchronization on a Linux Server?
- How Do I Verify Data Consistency Between the Source and Target Servers?
- Can I Use a Temporary AK/SK Pair for Migration?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore