Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
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
- SDK Reference
- FAQs
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- 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
On this page
Show all
Data Migration Overview
Updated on 2024-12-24 GMT+08:00
By default, an SFS Turbo file system can only be accessed by ECSs or CCE containers in the same VPC as the file system. To access an SFS Turbo file system from an on-premises data center or a different VPC, you need to establish network connections using Direct Connect, VPN, or VPC peering connections.
- To access from on premises or another cloud, use Direct Connect or VPN.
- To access from a different VPC using the same account in the same region, use VPC peering.
- To access using a different account in the same region, use VPC peering.
- To access from a different region, use Cloud Connect.
This section mainly introduces how to migrate data from the local NAS storage to SFS Turbo through direct file system mount to an ECS that can access the Internet. There are two scenarios:
- Mount and access the SFS Turbo file system.
- If the connection cannot be established through file system mounting, migrate data through the ECS over the Internet.
Parent topic: Data Migration
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.