Segal Volumes
Keep block storage persistent across the lifecycle of a compatible compute instance.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Project-scoped volumes and compatible regional attachments. Backups and snapshots must be specified separately.
- 1
Create a volume with the required size and storage class
- 2
Attach it to a compatible regional instance
- 3
Format, mount and back it up within the workload’s operating procedure
Service architecture
- Volume attachment and filesystem mounting are separate operations
- Snapshots have their own retention and storage footprint
- Capacity planning includes IOPS and throughput requirements
Operating boundaries
- Instance and volume must satisfy regional and attachment constraints
- Deleting a VM must not silently delete retained customer data
- A snapshot is not a substitute for an application-consistent backup
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Block Storage. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference