FAQ

Yes, LUKS keys can be used to encrypt the storage at rest.

Typically every 1-2 months.

We offer 3 levels of support: Basic: Business hours, email-only support, with a 2-business day maximum initial response time Plus: Business hours, email or phone support, with a 4-hour maximum initial emergency response time, and an 8-hour maximum non-emergency initial response time Enterprise: 24×7, 365-day support, with 1-hour emergency response time, and a 4-hour non-emergency response time – LINBIT SDS is only sold with Enterprise support

LINBIT SDS is comprised of a control-plane and data-plane, which can be updated independently. Updates to LINSTOR (the control plane) can happen without impacting applications access to existing volumes, during the upgrade new volumes will not be provisioned until after the upgrade completes. An upgrade to the data-plane requires workloads to be migrated away from the host that is being upgraded.

If you use the replication features of LINBIT SDS (DRBD), then yes.  DRBD storage replication is fully synchronous by default. Volumes are RWO (read write once). Quorum and internal protocols determine whether or not a specific replica may be promoted (become RW).

Yes, LINBIT SDS supports the latest version of TLS.

Yes, LINBIT SDS supports any algorithm LUKS supports.

Yes, all access is controlled through standard Kubernetes user access controls.

LINSTOR achieved 14.8 million IOPS on a 12 node cluster built from standard off-the-shelf Intel servers. This is (or at least was) the highest storage performance reached by a hyper-converged system on the market, for this hardware basis.

Yes, you can add more physical nodes with storage.  This will increase the capacity of hyper-converged worker nodes. You can also add additional storage to existing nodes to either create new storage-pools or expand existing storage-pools which can increase performance and/or capacity.

There is a 1PiB limit on an individual volumes. However, you can have many volumes with combined storage capacity greater than 1PiB.

Yes, LINBIT SDS (LINSTOR) exposes a Prometheus metric endpoint on the controller, which can report on storage-pool utilization, resource definition counts, node states, etc.  DRBD, the replication used in LINBIT SDS, also supports exposing Prometheus metrics.

Yes, when “allowVolumeExpansion: true” is set on the StorageClass and the PV is created dynamically.

Yes, most options for LINBIT SDS (LINSTOR) volumes are configured in the StorageClass objects.

Yes, LINBIT SDS uses DRBD to replicate volumes – up to 32 replicas.

Yes, LINBIT SDS (LINSTOR) has a REST API. In k8s environments the API can be accessed through the LINSTOR controller’s Kubernetes service (created by the LINSTOR Operator).

LINBIT SDS supports any encryption that is supported by the Linux Kernel and that is available on all nodes.

Yes, LINBIT SDS (LINSTOR) has native LUKS support that can be enabled/disabled.

Yes, you can have multiple storage classes defined within LINSTOR. Each storage class could be backed by different classes of physical storage. Larger slower SSDs could make up one LINSTOR storage pool, while smaller lower latency NVMe devices could be used as another storage pool.

Yes, you can populate new persistent volumes from snapshots of other volumes.

Yes, LINBIT SDS (LINSTOR) supports thin and thick provisioned storage-pools/storageClasses.

Yes.  Trilio, Bacula, Kasten, and Velero have been tested, but any CSI compliant backup solution should work since LINBIT SDS (LINSTOR) is also CSI compliant.

Yes, using another LINBIT product, DRBD Proxy.  You will need a license, please contact sales for assistance.

Yes.  LINBIT SDS (LINSTOR) has the concept of storage-pools, which are intended to group like storage. These storage-pools are then defined in storage Classes, so users can choose storage based on their application’s performance requirements.

Yes, LINBIT SDS (LINSTOR) supports creating new volumes from snapshots of existing volumes.

Yes.  Snapshots are supported with thin provisioned LINBIT SDS (LINSTOR) storage-pools.

Yes, LINBIT SDS (LINSTOR) is fully compliant with CSI standards.

Yes.

LINBIT SDS (LINSTOR) can replicate persistent volumes across all availability zones (AZ) in any region. LINBIT SDS (LINSTOR) provisions RWO volumes, so they may only be accessed in one AZ at a time. However, data is available if cross AZ rescheduling occurs.

Yes.  Multi-container pods generally have the ability to do this with their persistent volumes; LINBIT SDS is no different.