Attachment
Region and infrastructure compatibility matter. A volume cannot be assumed to attach to every server in the catalog.
BLOCK STORAGE
Block storage for server workloads
A separate volume for a server: an application disk, database storage or persistent working data. Plan the volume together with the compute resource it will connect to.
A volume connected to your server
The operating system uses the attached volume as a block device. Filesystem creation, mounting and application consistency remain part of the deployment plan.
Compute↔Volume→Filesystem
ATTACHMENT PLAN
From a volume to application data
- Select the target server
- Confirm region and attachment compatibility
- Attach the volume
- Prepare and mount the filesystem
Plan how the data is used
I/O profile
Specify latency, IOPS and throughput requirements. Capacity alone does not describe disk performance.
Growth and snapshots
Check supported resize and snapshot operations. Expanding a volume may also require expanding the filesystem inside the server.
Choose the right storage model
Object storage
An object, a key, an API
Object storageBlock storage
A volume connected to your server
File storage
Shared paths, coordinated access
File storageQuestions before you start
Can I attach this volume to several servers?
Do not assume multi-attach support. It depends on the service and filesystem. For shared directory access, compare file storage instead.
Is storage the same as backup?
No. A working copy can be overwritten or deleted. A recovery strategy needs separate copies, retention rules and a tested restore procedure.