Every environment starts on its machine's own disk. When that is not enough, you buy a volume, a separate disk the provider attaches to the machine, and move your files onto it.
Two halves of one disk
Which half filled up decides what you do about it.
| Half | Holds | To grow it |
|---|---|---|
| Your files | Uploads, private files, and any directories your vallic.yaml asked for |
Buy a volume and move them onto it |
| The servers' own data | The database's files, a search index, a message broker's queues | Stays on the main disk: take a bigger machine |
Your files are stored under our names, not your framework's:
| Name | Holds |
|---|---|
public |
Whatever your application serves |
private |
What it keeps behind an access check |
mounts/ |
Anything your vallic.yaml declared |
Your code still sees its own paths: a Drupal site still writes to
web/sites/default/files. On the disk, in a backup and in the figures below,
it is public.
Your plan's memory sets how much server data you may keep, not the free disk. A database much larger than the machine's memory gets slower the bigger it grows. A 4 GB machine allows 20 GB of server data, an 8 GB machine 50 GB, and so on. The console shows where you are against it.
Buying storage does not raise that number. A database that has outgrown its machine needs a bigger machine or one of its own.
Dividing it between services
If your site runs more than one service that keeps data, you can give each a share of the allowance. The storage page then reports each against its own share.
- The shares must add up to no more than the allowance.
- You can leave some of the allowance unallocated.
- A service you leave out is measured against the whole allowance.
- A database that has outgrown its share needs a bigger machine.
- A search index that has outgrown its share can often be reindexed, or given a disk of its own.
These are budgets, not limits. Nothing stops a service growing past its share.
What can have its own disk
Each of these can be given a disk of its own, from the environment's Storage tab, one row at a time:
- Public files: what the site serves
- Private files, and with them your declared mounts
- A search index, if it has outgrown the machine and you accept that searches get slower
- A queue
The database always stays on the machine. Services that rebuild themselves from nothing, such as a cache or a proxy, are not offered a disk either.
The machine's own disk
You choose between regular and cloud native compute beside the datacentre when the project is set up.
| Compute | Root disk | To grow it |
|---|---|---|
| regular compute | Comes with the machine type. Local storage, the fastest disk there is. | Move to a different type, which is downtime. See Machines. |
| cloud native compute | A volume of its own, from 10 GB up, priced as its own line. You pick the size when you configure the project. | Grow it later without moving the machine. It pauses briefly while the filesystem is extended. The machine type and other prices do not change. |
On cloud native compute, the size you pick is the size you get. The volume underneath is larger, to hold the OS, the images, the journal, the releases kept for rollback and the database dumps held before they go offsite. None of that comes out of what you bought.
Buying more room
- On the Storage tab, choose Own disk… on the bucket's row.
- Pick a size. The first size offered is the smallest that holds what is budgeted for that bucket.
The disk is made straight away and shows under Disks while the provider attaches it. From then on it is on your monthly bill by the block.
| Disk | Rule |
|---|---|
| Sizes | From 10 GB: fives to 50 GB, tens to 100 GB, then fifties to 1 TB |
| Price | Based on what your machines' provider charges for storage. The rate per gigabyte falls past 50 GB. Each size shows its monthly price before you buy it. |
The disk arrives empty. Moving what is there onto it is a separate step, see below, because the site stops while the copy runs.
To enlarge a disk that filled up, choose Grow on the volume and pick a bigger size. The disk grows underneath the running site: nothing unmounts, nothing restarts, and no files move. Resizing the machine itself does require stopping it.
Growing happens in two parts, a few minutes apart:
- The disk itself grows at the provider, and your new size is what you are billed from then on.
- The filesystem on it grows to match, on the machine's next reconcile. Until
that happens
dfstill reports the old figure.
Disks only grow. A disk cannot be shrunk, so a size you pick is a floor for the rest of that disk's life.
Moving data between disks
Buying a disk does not move the data. Moving is its own action, per bucket.
The site stops while the copy runs. Choose Move data… on the row once the disk is ready. It stops the stack, copies that bucket's directory, verifies the copy, and only then mounts the disk in its place.
Nothing is deleted by the move. The old copy stays where it was, so undoing a move is a mount, not a restore from backup. Freeing that space is a separate, confirmed step under Left behind.
InfluxDB's data, or a cache's, carried onto a machine of its own is listed there too. That is the copy it left on the web machine, removed on the same step once that machine has stopped running the service.
When an environment is deleted
Nothing is kept for a grace period, so back up or download any files you need before you delete. Billing stops at deletion.
The environment's disks go with it:
- A disk on a machine that goes too is removed with the machine.
- A disk on a machine that stays, one that also carries your other environments, is unmounted there and destroyed.
What disk usage counts
The figures shown for an environment cover everything on disk, reported apart:
- public files: uploads, anything served to visitors
- private files: anything behind an access check
- the database
- releases: your code, once per release kept for rollback
- application logs: whatever your code writes to
/var/log/app
When your files grow, buy storage. When your database grows, take a bigger machine.
Application logs are the one figure with a limit rather than a budget, and they are not counted towards the storage you are assigned. The limit is a tenth of the storage the environment is assigned, between 100 MB and 20 GB. Past it the oldest files are removed, and never the one being written. See Logs.
Shared storage
On the Dedicated shape, with two or more web machines, an upload landing on one web machine does not exist on the other. So the shared directory is served from one machine to the others over the private network, never the public one. The machines write as their own environment's user, not as root.
This is set up for you. It does not change your application: if your code writes to a local path instead of the shared directory, shared storage cannot help it. See Shapes.
Next
- Backups: what is copied off the machine
- Logs: what your containers write
- Software stacks: what runs on top of all this
- Start here
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console