Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
- 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
Show all
Solution Overview
By default, an SFS Turbo file system can only be accessed by Elastic Cloud Servers (ECSs) or Cloud Container Engine (CCE) containers in the same Virtual Private Cloud (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, Virtual Private Network (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.
You can use an ECS that can access the Internet to migrate data to SFS Turbo.
- Mount the SFS Turbo file system to the ECS and migrate data from the local Network Attached Storage (NAS) to the SFS Turbo file system.
- If the connection cannot be established through file system mounting, migrate data through the ECS over the Internet.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
