For the complete documentation index, see llms.txt. This page is also available as Markdown.

Frequently Asked Questions

Frequently asked questions about Object Storage: what it is, buckets and objects, S3 access and clients, and data protection.

Each answer links to the concept, guide, or reference where the detail is.

What it is

What is Object Storage?

It is a high-capacity, S3-compatible storage space where you store large volumes of data: backups, application files, exports, and logs. It is not managed by folders like a disk, but by software that speaks S3. More in What is Object Storage?

How is it different from File Storage?

File Storage is for day-to-day work on files, accessed by people via the web or a network drive. Object Storage is for storing large volumes, accessed by software via the S3 protocol. The quick rule: if a person opens and edits it daily, it's Files; if software writes or reads it, it's Objects.

What is it commonly used for?

As a backup target with S3-compatible tools, archiving and retention of large volumes, application data and exports, logs and technical artifacts, and repositories for restoration and version preservation.

Buckets and objects

How are the data organized?

In repositories (buckets) that contain objects. An object is data together with its associated information, stored as a unit. The organization is flat: objects are identified by their name, and the prefixes in that name act as "folders" when you need them. More in Buckets and objects.

What does versioning do?

With versioning enabled, every time an object is overwritten, the previous version is preserved, so you can return to a previous state if something is overwritten or corrupted. It is especially useful when the repository receives automatic backups that are rewritten. The detail is in Versioning and immutability.

Can I prevent an object from being deleted or modified for a period of time?

Immutability (Object Lock) is designed for that: it locks objects against deletion or modification for a period, useful for retention and protection against ransomware. It is a capability under development, so we confirm its scope and availability with the current platform before publishing the configuration details.

Can I make expired objects be deleted automatically?

Yes, you can rely on automatic deletion rules so that objects that are no longer needed are deleted after a period, so the repository does not grow uncontrollably.

S3 access and clients

What do I need to connect software via S3?

Four pieces of data: the endpoint (the access URL), the repository name (which acts as the path), the access key, and the secret key. The owner user accesses directly; the rest must specify the repository name when configuring access. The data and commands are in S3 credentials and access.

What software can I connect?

Any S3-compatible client works, with no custom development: backup software (Veeam, Acronis, Bacula, Veritas, Ahsay), NAS (QNAP), desktop clients (Cyberduck, S3 Browser), and command line (AWS CLI, s3cmd, rclone). The S3 standard is the advantage: you use the tool you already have. More in Compatible clients.

Can I have multiple users with different access levels in a repository?

Yes, a repository can have several S3 users, each with their own credentials and access level. You can create, enable, or disable them without deleting them, and rotate their keys. The recommendation is one credential per service or per client, with minimum privileges, so you can revoke or rotate one without affecting the rest. More in Users and permissions.

Data protection

How is data durability protected?

Each object is stored in triple replica (three disks on three different servers), and at least one copy is kept in a different data center. The design is intended for very high data durability. More in Resilience, encryption, and compliance.

Are the data encrypted?

Yes, in transit over HTTPS and at rest in storage. In addition, there are firewalls, IDS/IPS, and anti-DDoS protection at the perimeter, the logical isolation of each client, and the S3 credentials that you control and rotate.

Where do the data reside?

The region determines where the data reside, which is key for sovereignty and compliance requirements, and you choose it when activating the service. We confirm the available regions with the current platform before publishing them. The quota is configurable and can be increased as the volume grows, without recreating the repository. More in Quota and regions.

Next steps

Last updated

Was this helpful?