Scalable File Service
Scalable File Service
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- Troubleshooting
-
FAQs
- Concepts
- Specifications
- Restrictions
- Networks
- Billing
-
Others
- How Do I Access a File System from a Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
- What Resources Does SFS Occupy?
- Can a File System Be Accessed Across Multiple AZs?
- How Can I Migrate Data Between SFS and EVS?
- Can I Directly Access SFS from On-premises Devices?
- How Do I Delete .nfs Files?
- How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
- How Do Second- and Third-level Directory Permissions of an SFS Turbo File System Be Inherited?
On this page
Show all
Help Center/
Scalable File Service/
FAQs/
Others/
Can a File System Be Accessed Across Multiple AZs?
Can a File System Be Accessed Across Multiple AZs?
Updated on 2024-08-26 GMT+08:00
- A single file system can be created only in one AZ, for example, AZ 1, but can be mounted to and accessed from any AZ.
- A file system does not support data redundancy across AZs. If the AZ where a file system resides is unavailable, the file system is unavailable.
Parent topic: Others
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.