Every service in vallic.yaml names a version:
services:
- mariadb: '11.4'
- valkey: '8.1'
That is the version your environment runs, from the next deploy. A version the platform does not offer is not honoured: the service stays on the current default. Software stacks lists what each service offers.
Services that keep nothing
Caches (Valkey, Redis, Memcached) and Vinyl Cache (Varnish) move up or down freely. Their contents may be empty afterwards; your application refills them as it is used. A cache rebuild helps a Drupal site along.
Services that keep data
Databases (MariaDB, MySQL, PostgreSQL), search (Solr, Meilisearch), time series (InfluxDB) and the queue (RabbitMQ) keep data on disk in the format of the version that wrote it. The new version starts on the files the old one left:
| Service | Moving to a newer version | Moving to an older version |
|---|---|---|
| MariaDB, MySQL | Generally reads the older data and upgrades it in place. The server's own tables (accounts, grants) are upgraded once it starts: MySQL does that itself, and the platform runs mariadb-upgrade for MariaDB. After that the older version cannot read the data again |
Does not start on data a newer version wrote |
| PostgreSQL | A different major version does not start at all on the old data | Does not start |
| Solr | Reads one major version back; rebuild the index to be sure | Does not reliably read it; rebuild the index |
| Meilisearch | Does not read another version's index; rebuild it | Rebuild it |
| InfluxDB | Moves its own records forward on the first start of a newer 2.x | Does not start on records a newer version moved; they are taken back with influxd downgrade, which a version change does not run |
| RabbitMQ | Keeps its queues across minor versions | Empty the queues first |
Your application's own data is never touched by any of this, only the service's files on the machine. Your site is down while a database does not start, so pick a path below before you push.
Before you change anything
-
Take a backup: Backups → Back up now on the environment. Database backups are SQL dumps, which restore into any version.
-
Keep a dump of your own as well, over shell access:
ssh -p 2417 vc-t-acme@production.acme.vallic.cloud db-export > before-upgrade.sql -
Try it on staging first. Backups → Copy from another environment puts production's data on staging. Change the version on the branch staging tracks and deploy.
Moving a database to a version that can read the old data
MariaDB or MySQL, to a newer version.
- Take the backup above.
- Change the version in
vallic.yamland deploy. - Check the site. If anything is wrong, restore the backup as Going back describes. Changing the version back on its own does not work: the data has already been upgraded.
Moving a database to a version that cannot read the old data
PostgreSQL to another major version, or any database to an older version. There are three ways, from the least to the most disruptive.
A new environment, then move to it
The safest: the old environment is not touched until the new one is proven.
-
Create a new environment, or a new project for production, whose
vallic.yamlnames the new version from its first deploy. -
Deploy it, then load your data into it. Use Backups → Copy from another environment for a staging environment, or
db-importwith the dump you kept:ssh -p 2417 vc-t-acme@production.acme-new.vallic.cloud db-import < before-upgrade.sql -
Move your files if they need to go too. Shell access covers rsync.
-
Check the new environment, then move your domains across and remove the old one.
The same environment, with its database reset
When a new environment is not practical. Backups → Reset database does it in one action. It backs up the database while it still answers, empties its files on the machine, then restores the newest backup into the empty database. Each step waits for the one before.
Your site is unavailable from the reset until the restore finishes, and the reset deletes every table. Do it at a quiet time, and consider switching the site offline first so visitors see a page saying so. Only an Admin or the Owner can reset a database.
-
Keep a dump of your own, as above.
-
Change the version in
vallic.yamland deploy. On a version that cannot read the old files the database does not start; that is expected. -
Open Backups → Reset database and set the two options:
Option Setting Take a database backup first Ticked if the database still answers: before step 2, or on a version change that did start. Unticked if it no longer starts; the backups already taken are restored then Restore the newest database backup Ticked. Untick it to load your own dump with db-importinstead -
Type the environment's name to confirm.
The database starts empty on the version vallic.yaml declares, and the
backup loads into it.
Reimporting without clearing
Only for a database that did start on the new version but whose data you
want rebuilt anyway: to shed an old format, or after an upgrade that left
things half-converted. db-import replaces what is there:
| Database | What db-import does |
|---|---|
| MariaDB, MySQL | A dump from db-export carries DROP TABLE statements and replaces each table as it goes |
| PostgreSQL | Empties the schema before it loads |
Search indexes and queues
- Solr and Meilisearch: after changing the version, rebuild the index from
your application. For Drupal, run
drush search-api:reindexand thendrush search-api:index. An index is built from your database, so nothing is lost that the rebuild cannot put back. - RabbitMQ: let the queues drain, or stop what feeds them, before a change that is not a minor version. Messages still waiting when the service is replaced may not be there afterwards.
Going back
- A cache or Varnish: change the version back and deploy.
- A database that did not start on the new version: change the version back and deploy. Its files are untouched.
- A database that ran on the new version: the old version may no longer
read its files. Take the same environment, database reset path in reverse.
Put the old version back in
vallic.yaml, deploy, then Reset database with the backup unticked. That restores the backup you took before you started.
Who can do this
| Action | Who |
|---|---|
| Change a version | Whoever can push to the branch the environment tracks |
| Back up, restore, copy (the environment's Backups tab) | The roles Teams lists |
| Reset a database | An Admin or the Owner; on production, the Owner |
Next
- Configuration — the rest of
vallic.yaml - Backups — taking, restoring and copying
- Software stacks — which versions each service offers
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