Shared Network Storage
Danger
This service has been discontinued and is no longer available
Description
Shared Network Storage provides access to files over the network. Your data is stored on high-speed SSD storage. We operate two clusters in separate data centers, each consisting of multiple individual nodes. All nodes within a cluster form an integrated system. Consequently, data is evenly distributed across multiple hard drives and nodes. The capacity is provided as a global file system that scales linearly by adding more nodes. As a customer, you order shared volumes, which come with a standard quota limit of 10 terabytes. Each volume is mirrored to the remote cluster, ensuring a simple and rapid failover mechanism is available even after a complete data center outage. Please note that mirroring is asynchronous; this means the mirror is not an exact copy of the source volume at every moment. The quota serves to protect the storage system. We monitor volume storage usage and increase the quota during standard business hours if a volume's free space falls below a specific threshold, preventing operational disruptions caused by quota limits. Outside standard business hours, our incident management team handles quota increases in response to a reported issue.
What we aim to achieve with this service
- Centralized file availability for multiple application servers
- Provision of large storage volumes
- Faster recovery of virtual servers, as large portions of the file system are stored on shared network storage
- Faster deployment
- Cost savings compared to redundant local data storage
- Prevention of incidents caused by insufficient local disk space on virtual servers
- Reduction of identical changes across virtual servers
What you can expect from our LTM
- Data and metadata stored on SSDs
- 10 Gigabit Ethernet connectivity for cluster nodes
- Triple redundancy for data and metadata per volume
- Mirrored volumes
- Volume backups to a remote cluster following the 7x4x3 standard
Optional service features
- Quota adjustment based on customer requirements.
Important Notes
The following points will help you avoid performance degradation. The closer you get to these maximum limits, the more likely it is that your application will experience performance issues.
- Number of files in a directory: 10,000. We therefore recommend distributing files across subdirectories where necessary—for example, using dynamic directory hashing.
- Number of subdirectories in a directory: 10,000
- File size: 1 TB
- We recommend using a volume in only one environment and one project at a time.
- 200 million files per volume
Application Requirements
- If two clients require simultaneous write access to the same file, the customer application must handle file locking; otherwise, inconsistent results may occur.
Fair Use Policy
In the interest of all customers, we aim to avoid imposing hard limits on the use of shared infrastructure. This approach allows for unexpected load spikes in your setups. Please adhere to our recommendations. Should a customer's unusual use of shared infrastructure cause service disruptions for other customers, we reserves the right to take measures to restore the intended performance level for the affected customers. we reserve the right to modify the technical infrastructure and associated performance and service parameters of the service at any time.