Make room for the data behind your project. Vault separates a dedicated NVMe boot drive from configurable SAN storage, with CPU, memory and transfer allowances you can size independently.
A storage-oriented Linux configuration with a listed 5,000 GB SAN allocation and a separate 50 GB NVMe boot drive. Two CPU cores, 8 GB of memory and 20 TB of traffic support archive and file-storage projects.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
The configuration lists an NVMe boot drive alongside SAN capacity, making the system volume distinct from the space intended for larger datasets.
Choose the SAN storage option that matches your data volume and expected growth. Read the units in the selector when calculating usable capacity.
Adjust CPU cores and memory for indexing, checksums, cataloguing or applications around the storage, rather than selecting capacity alone.
Select a traffic allowance and IPv4 count suited to the workflow. Storage capacity and monthly data transfer are separate parts of the configuration.
Keep larger collections behind an application that controls who can browse, upload or retrieve each item.
Provide a Swiss storage environment for project data, exports and research collections with a defined access policy.
Use storage as one component of an independent backup strategy, with encryption, retention and restoration tests under your control.
Count the data you already hold, the rate at which it grows and any temporary space needed for processing. Capacity options allow a larger data allocation, while the boot drive remains a separate specification. Filesystem overhead and your storage layout can change the space an application sees.
A large storage volume may be quiet most days or move substantial amounts of data. Initial uploads, regular backups and repeated downloads all affect traffic. Choose the bandwidth allowance alongside storage, then ensure your own connection and software can complete the workflow within the required time.
You control the software and access model around the stored files. Encrypt sensitive archives before upload where appropriate, keep encryption keys separate, and restrict storage interfaces to authorised users. A storage environment can hold a backup, but the existence of a second folder does not by itself make the original data recoverable.
Vault lists SAN capacity, an NVMe boot drive and Linux template choices. Decide whether applications will read a local volume or use a file-sharing service such as NFS or SMB, then check operating-system support and protect the interface. Ceph, RBD, replication and failover describe possible storage architectures; the operator must confirm the actual backend and recovery scope before they become service commitments.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
The catalogue lists the NVMe boot drive separately from the SAN allocation. Plan the operating system and large data volume as distinct storage components.
The catalogue preserves the source units for each specification and option. Compare the actual selected capacity and confirm the allocation rather than treating different unit labels as interchangeable.
No. SAN capacity and the bandwidth allowance have separate selectors. Check both in the configuration summary when preparing a data-heavy workflow.
Vault is a storage configuration. You still need backup software or a transfer process, retention rules, encryption where appropriate and a tested restoration procedure.
Yes. The configurator includes CPU-core and memory choices in addition to SAN storage, traffic and IPv4 addresses. Select resources for the applications using the data.
A supported Linux setup can run a suitable file-sharing service. Verify package support, authentication and firewall rules, and restrict storage access to the intended users or private network.
The current catalogue specifies SAN capacity, not a verified Ceph topology or RBD interface. Confirm backend technology, redundancy, failure handling and recovery responsibility with the operator.
The catalogue lists capacity options for the initial request. Later resizing, filesystem changes and any downtime must be confirmed for the installed environment.
Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem.
Read the guideChoose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue.
Read the guideA Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment.
Read the guideChoose your resources. Keep control of your identity.