Storage Options

The instance already has a root disk. Volumes are extra.

Use a volume when the guest needs more disk than the flavor root disk, or when that disk should outlive the server. Create it under Cloud → Volumes, then attach it from the server page. Launch is in Creating and Managing Virtual Machines.

Create a volume

From Cloud → Volumes, stay on the Volumes tab. Click + Create Volume.

1. Location is SiouxFalls.
2. Volume source is No source, empty volume unless you are cloning from a snapshot.
3. Storage type is whatever this project offers. A lab project may show test; pick the type listed for your project.
4. Size is 25 GB, 100 GB, 500 GB, 1000 GB, or Other. This example is 25 GB.
5. Name it something you will recognize. This example is docs-vol.
6. Click + Create Volume.

Attach it to a server

Open the server (Cloud → Servers, click the name). The Volumes tab is extra disks on top of the root disk. Until one is attached you will see There are no volumes. Click + Attach Volume and pick docs-vol.

Format and mount

SSH in, then find the new disk:

lsblk

Format it once, mount it, and persist the mount by UUID from blkid:

sudo mkfs.ext4 /dev/vdb
sudo mkdir /mnt/data
sudo mount /dev/vdb /mnt/data
sudo blkid /dev/vdb

Put that UUID in /etc/fstab so the volume remounts after reboot:

UUID=YOUR-UUID /mnt/data ext4 defaults 0 2

Snapshots

On Cloud → Volumes, open the Snapshots tab. That is a point-in-time copy of a volume. An empty project shows There are no snapshots.

The server page also has a Snapshots tab. That one is a copy of the instance disk, not the extra volume. Take one before a risky change.

Object storage

For files and backups that are not a disk, use Cloud → Object Storage. Uploading in the portal is size-limited. For full-size transfers use the S3 API: Using Cyberduck with Gozunga's Object Storage API and Configuring s3cmd with Gozunga Cloud Files.