Scalable File Service Turbo
Scalable File Service Turbo
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API
- Lifecycle Management
- Connection Management
- Tag Management
- Name Management
- File System Management
-
Storage Interworking Management
- Adding a Backend Target
- Querying Backend Targets
- Obtaining Details About a Backend Target
- Deleting a Backend Target
- Updating the Properties of a Storage Backend
- Updating the Auto Synchronization Policy of a Storage Backend
- Creating an Import or Export Task
- Querying Details About an Import or Export Task
- Listing Import and Export Tasks
- Deleting an Import or Export Task
- Updating a File System
- Directory Management
-
Permissions Management
- Creating a Permission Rule
- Querying Permission Rules of a File System
- Querying a Permission Rule of a File System
- Modifying a Permission Rule
- Deleting a Permissions Rule
- Creating and Binding the LDAP Configuration
- Querying the LDAP Configuration
- Modifying the LDAP Configuration
- Deleting the LDAP Configuration
- Task Management
- Permissions Policies and Supported Actions
- Common Parameters
- Appendix
- SDK Reference
-
FAQs
- SFS Turbo Concepts
- SFS Turbo Specifications
- SFS Turbo Billing
-
SFS Turbo Mount
- What Can I Do If Data of My SFS Turbo File System Is Not the Same When Accessed from Two Client Servers?
- Can I Mount an SFS Turbo File System Across Regions?
- Can I Mount an SFS Turbo File System Across Accounts?
- How Many Cloud Servers Can I Mount an SFS Turbo File System To?
- How Do I Mount a File System to a Linux ECS as a Non-root User
- What Can I Do If Mounting a Subdirectory of a File System Failed?
- SFS Turbo Access
- SFS Turbo Capacity Expansion
- SFS Turbo Deletion
- SFS Turbo Migration
- SFS Turbo Performance
-
Others
- Does the Security Group of a VPC Affect the Use of SFS Turbo?
- What Resources Does SFS Turbo Occupy?
- How Do I Check Whether an SFS Turbo File System Is Available on a Linux Server?
- Can I Upgrade an SFS Turbo File System from the Standard Type to the Performance Type?
- Does SFS Turbo File Systems Support Multi-AZ Deployment?
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- File System Performance Was Poor
- Creating an SFS Turbo File System Failed
- File System Automatically Unmounted
- A Client Server Failed to Access a File System
- Abnormal File System Status
- Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
- Writing to a File System Failed
- Error Message "wrong fs type, bad option" Was Displayed During File System Mounting
- General Reference
On this page
Help Center/
Scalable File Service Turbo/
Best Practices/
Migrating Data to SFS Turbo/
Migrating Data Between File Systems
Copied.
Migrating Data Between File Systems
Solution Overview
You can migrate data from an SFS Capacity-Oriented file system to an SFS Turbo file system or the other way around.
In this solution, a Linux ECS is used to connect the SFS Capacity-Oriented file system and the SFS Turbo file system.
Notes and Constraints
- Only Linux ECSs can be used to migrate data.
- The Linux ECS, SFS Capacity-Oriented file system, and SFS Turbo file system must be in the same VPC.
- Incremental migration is supported, so you can only migrate the changed data.
Prerequisites
- You have created a Linux ECS.
- You have created an SFS Capacity-Oriented file system and an SFS Turbo file system and have obtained their addresses.
Resource Planning
Table 1 describes the resource planning in this solution.
Procedure
- Log in to the ECS console.
- Log in to the Linux ECS.
- Mount either the SFS Capacity-Oriented or SFS Turbo file system to the ECS.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock,tcp Address of the file system /mnt/src
- Mount the other file system to the ECS.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock,tcp Address of the other file system /mnt/dst
- Download and install rclone. For the download address, see https://rclone.org/downloads/.
- Synchronize data.
rclone copy /mnt/src /mnt/dst -P --transfers 32 --checkers 64 --links --create-empty-src-dirs
NOTE:
The parameters are described as follows. Set transfers and checkers based on the system specifications.
- /mnt/src: source path
- /mnt/dst: destination path
- --transfers: number of files that can be transferred concurrently
- --checkers: number of local files that can be scanned concurrently
- -P: data copy progress
- --links: replicates the soft links from the source. They are saved as soft links in the destination.
- --copy-links: replicates the content of files to which the soft links point. They are saved as files rather than soft links in the destination.
- --create-empty-src-dirs: replicates the empty directories from the source to the destination.
After data synchronization is complete, go to the target file system to check whether data is migrated.
Verification
- Log in to the Linux ECS.
- Check the file synchronization results on the destination server.
cd /mnt/dst ls | wc -l
- If the data volume is the same as that on the source server, data is migrated successfully.
Parent topic: Migrating Data to SFS Turbo
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot