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

Check compatibility before uninstalling the source:

The destination Canvus version must be the same as or newer than the source version.
These instructions require a PostgreSQL 18 container release, aligned with the standalone installers. They are not instructions for upgrading an existing PostgreSQL 17 container's data directory or restoring an 18.x backup into an older database.
The source backup must finish successfully before proceeding. If it reports a PostgreSQL tool/version error, keep the source installed and contact MultiTaction support; do not alter the backup to work around it.
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.