Snapshots and Clones
With snapshots and clones, you can leverage fast and thin point-in-time snapshots/clones of Lightbits volumes. A snapshot can be taken from a volume, and a volume can be created from a snapshot (aka a clone).
Snapshots cannot be exported as a volume; only clones of that snapshot can be accessed.
Snapshots and clones will be created on the same failure domain. There is no limit on the per-volume number of snaps and clones, and no limit on the per-failure domain number of snaps and clones.
For snapshot scheduling, create a snapshot of a volume in a predetermined schedule managed by the cluster (multiple schedulers can exist for the same volume).
With regards to Management APIs, snapshots are separate entities and clones are the same as volumes. Clones can be deleted by using the delete volume API. To delete a snapshot, you will need to call the delete snapshot API.
Plugins
OpenStack and Kubernetes are both supported and require compatible plugin versions. OpenStack and Kubernetes support must be updated to include snapshots and cloning. This applies to all plugin versions in production.
Rollback
The Rollback operation takes a volume and restores it back to a snapshot state (data + md). It is recommended to either remove active mounts, detach the volume, or flush caches before performing this operation.
The process should be as follows:
Stop process/es that use the volume.
Unmount FS create on top of the volume; e.g., for mount point /mnt/volumetorollback.
a. Unmount /mnt/volumetorollback.
Perform rollback via lbcli.
Mount the volume: mount /mnt/volumetorollback.
Snapshots and Clone Commands
List the existing volumes: lbcli -J $JWT list volumes:
Create a snapshot from the volume:
Check that the snapshot was created:
Get snapshot info:
Create a volume from snapshot (clone):
Create a snapshot-policy:
List snapshot-policies:
Get snapshot-policies:
Rollback volume:
Delete snapshots/snapshot-policy:
© 2026 Lightbits Labs™