Migrating Data from SFS Capacity-Oriented to SFS Turbo Using fpart
Solution Overview
This section describes how to use fpart to migrate data from SFS Capacity-Oriented to SFS Turbo. The migration aims to efficiently and securely migrate data while ensuring data integrity and consistency. The entire process includes a full migration (no impact on services), a first incremental migration (no impact on services), unmounting the SFS Capacity-Oriented file system (services are interrupted), a second incremental migration (services are interrupted), and changing the mount point (services are interrupted).
Constraints
- This solution is only applicable when a Linux ECS is used to migrate data.
- The Linux ECS, SFS Capacity-Oriented file system, and SFS Turbo file system must be in the same VPC.
- SFS Capacity-Oriented file systems using CIFS or those mounted to Windows clients cannot be migrated.
- If the SFS Turbo file system is used by a CCE cluster, the CCE cluster must be upgraded to version 1.15+, and the everest add-on version must be later than 1.1.13.
Solution Architecture

Resource Planning
Table 1 describes the resource planning in this solution.
Resource |
Example Configuration |
Description |
---|---|---|
ECS |
Specifications: 8 vCPUs | 16 GiB | c7.2xlarge.2 OS: Linux Region: CN-Hong Kong VPC: VPC1 |
Ensure that the /mnt/src and /mnt/dst directories have been created. |
Preparations
- Create an SFS Turbo file system on the Huawei Cloud console in the VPC where the SFS Capacity-Oriented file system resides. If no VPC is available, create one in the same region and then create the SFS Turbo file system. For how to create an SFS Turbo file system, see Creating an SFS Turbo File System. For how to create a VPC, see Creating a VPC with a Subnet.
- If a Linux ECS is available, skip this step. If not, buy a Linux ECS on the Huawei Cloud console. You are advised to buy an ECS with 8 or 16 vCPUs. This ECS must be in the VPC where the SFS Capacity-Oriented and SFS Turbo file systems belong and can communicate with the file systems.
- Install fpart on the Linux ECS.
yum -y install fpart rsync
- Create two local mount points on the Linux ECS.
mkdir /mnt/src
mkdir /mnt/dst
- Obtain the mount points of the SFS Capacity-Oriented and SFS Turbo file systems from the console. Then, mount the file systems on the created local mount points (/mnt/src and /mnt/dst).
mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-SFS-Capacity-Oriented-file-system> /mnt/src
mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-SFS-Turbo-file-system> /mnt/dst
- If the mount fails, install the corresponding tool package by referring to Mounting an NFS File System to ECSs (Linux).
Procedure
- Full migration: Migrate all files from the SFS Capacity-Oriented file system to the SFS Turbo file system.
- Log in to the ECS using VNC and run the following command to synchronize data:
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
- n: the number of parallel copy threads
- f: the number of files each thread can copy
- o: the rsync configuration option
- v: the output detailed logs
- If there are a large number of files, you can run the command concurrently for the subdirectories in /mnt/src.
- You can adjust the n and f options based on the file and directory structure.
- The default run log files are stored in /tmp/fpsync, under which log stores task run logs, parts stores file partition logs, queue stores execution configurations, and work stores the copy commands. You can check the task running status based on these logs.
- Log in to the ECS using VNC and run the following command to synchronize data:
- First incremental migration: Synchronize the incremental data written to the SFS Turbo file system during the full migration.
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
Take note of the start time and end time of this operation. This period is approximately equal to how long customer services need to be stopped in the following steps.
- Unmounting the SFS Capacity-Oriented file system: To prevent new data from being written to the file system, before synchronizing the incremental data, stop the service application that uses the source file system on all ECSs and containers.
- Ensure that the SFS Capacity-Oriented file system is unmounted from all service ECSs (or cloud containers). Otherwise, after the migration, data in the SFS Turbo file system may be inconsistent with that in the SFS Capacity-Oriented file system.
- Do not unmount the SFS Capacity-Oriented file system from the ECS that you use to perform the migration.
- The operations vary in ECS and CCE scenarios. Refer to the operations based on your scenario.
- Ensure that services are stopped when you perform this step.
ECS scenario:
- Log in to each service ECS that mounts the SFS Capacity-Oriented file system.
- Unmount the SFS Capacity-Oriented file system.
umount -f <local-mount-point>
CCE scenario:
- Second incremental migration: Synchronize the incremental data generated during the first incremental migration to the SFS Turbo file system. After the synchronization, data in the SFS Turbo file system will be the same as that in the SFS Capacity-Oriented file system.
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
- Check that data in the SFS Turbo file system is the same as that in the SFS Capacity-Oriented file system.
- Ensure that services are stopped when you perform this step.
- Mounting the SFS Turbo file system: Unmount the SFS Capacity-Oriented file system from the ECS that you use to perform the migration and re-mount the SFS Turbo file system to this ECS.
ECS scenario:
- Log in to the ECS that you use to perform the migration and run the following command to unmount the SFS Capacity-Oriented file system:
umount -f <local-mount-point>
- Mount the SFS Turbo file system.
mount -t nfs -o vers=3,nolock <mount-point-SFS-Turbo-file-system>
CCE scenario: Mount the file system by referring to Migrating Containerized Application Data from SFS 1.0 to General-Purpose File System or SFS Turbo.
- Ensure that the mount parameters and directories are correct. Or, services may be affected.
- The operations vary in ECS and CCE scenarios. Refer to the operations based on your scenario.
- Log in to the ECS that you use to perform the migration and run the following command to unmount the SFS Capacity-Oriented file system:
- The customer restores services and checks whether services are normal.
- After observing the services for a period of time, the customer can release the SFS Capacity-Oriented file system resources to prevent unintended charges.
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.
Chatbot