Safe updates and backups

Update a package installation through Elowen's supported updater, and keep a matching backup before a change that could affect production data. This procedure is for administrators with host access; access to this article does not grant server permissions. Elowen does not provide a built-in backup or restore command.

Before updating

1. Check that the installation has a valid licence and that the host has network access to its licensing server.
2. Review the release and plugin compatibility information, and schedule a suitable maintenance window.
3. Back up the PostgreSQL database and the complete instance root together. Stop Elowen while capturing them so both represent the same state. The root includes the licence record, the key required to decrypt database-stored plugin credentials, plugin data, attachments and update records.

For the supported package installation, run:

elowen update

The updater checks the release against the licence, verifies the download, applies it, restarts services and checks startup. If startup checks fail, the updater restores the previous executable and plugin set. A database migration is not reversed by this rollback. It retains only the current and previous owned releases after success. A source checkout follows a different path: update core from its source repository and rebuild; do not use this package procedure for it.

Update Elowen

1. Run the command from the host as an operator authorized to update this installation.
2. Alternatively, open Settings → System and select Update now to start the update from the Web UI.
3. Follow the command output or update status panel and wait for completion; a queued request is not a completed update.
4. If recovery or operator attention is reported, preserve the update files and follow the displayed recovery instructions. Do not delete journals or lock files.

Verify the update

Check elowen status and confirm the daemon and Web UI answer. Open the application and complete a real interaction. Review service logs for startup errors and plugin load failures. If a plugin was skipped or rolled back, read its reported reason; see Plugin lifecycle for plugin-specific steps.

Back up and restore

Store the database dump and complete instance root as one dated backup set, and keep them protected together. Restoring a database without its matching root can leave plugin data unreadable because the root contains the plugin-secret key. The root also contains the licence record and update recovery files; do not substitute another instance's root or delete these files to force an update.

Restore both components from the same capture using your PostgreSQL and host backup procedures, then start Elowen and check its status and logs. Database migrations run at startup, so keep an untouched backup until the restored instance is verified. See Configuration for instance and database locations, and Production & Updates for the detailed updater and recovery behavior.