Skip to content

Migrating a standalone server to containers

Move a Canvus Server 3.x or 26.x standalone installation using the server's existing --backup and --restore --backup-path commands. The backup contains the Canvus database and assets; there is no separate SQL export or asset-copy procedure.

Follow the migration section for the destination host:

Each section covers backing up the old server, removing the old installation when reusing its machine, installing the containers, copying the backup/configuration/license files, running the restore through Podman, and restarting.

PostgreSQL version note

The deployments use different PostgreSQL major versions:

Deployment Bundled PostgreSQL
Linux standalone (.deb) 18 (18.6)
Windows standalone (MSI) 18 (18.6)
Containers (postgres image) 17 (17.11)

A Canvus backup stores the database as an SQL dump (db_dump.sql). The restore replays that dump into the container's database. It does not copy PostgreSQL data files, so you do not run pg_upgrade or move a data directory as part of this procedure.

Check compatibility before uninstalling the source:

  • The destination Canvus version must be the same as or newer than the source version. The restore refuses a backup made by a newer Canvus Server.
  • The source backup must finish successfully before proceeding. If it reports a PostgreSQL tool or version error, keep the source installed and contact MultiTaction support. Do not edit the backup to work around it.
  • If the restore reports an error, leave Canvus stopped on the destination, keep the source installed and contact MultiTaction support with the output.
  • When moving from 3.x to 26.x, update the clients to 26.x too. 3.x and 26.x clients/servers do not interoperate.

Files to keep separately

The Canvus backup does not include the server INI, license file or TLS certificate/private key files. Save these separately before uninstalling. See file locations.

On the destination, keep the container-generated mt-canvus-server.ini and bring across your site settings from the saved INI. Do not replace the new database connection settings and container paths with the standalone values. The installation pages show the correct mounted folders for the saved INI, license files and certificates.

Keep the original backup

Restore replaces the destination's existing Canvus data; it does not merge two servers. Use a new installation and retain the source backup until you have checked existing accounts, canvases, folders and media on the destination.

If moving to a different machine, leave the old installation intact and stopped until those checks are complete. Do not run both copies as active servers: changes made to one will not appear on the other.

For the full backup command reference, see Server backup and restore.