Skip to main content

Updates and Backups

Treat a NuQloud upgrade as a transaction, not a container restart.

Before an upgrade​

  • review the target Nextcloud major and every required intermediate major;
  • run app compatibility and infrastructure preflight checks;
  • confirm database, configuration, data, and custom-app backup coverage;
  • verify free disk space and backup readability;
  • record the active compose file, environment file, image, and SSL/proxy mode;
  • preserve runtime credentials, the previous working image, and existing recovery journals until the backup has been verified;
  • notify users if maintenance will interrupt access.

During the upgrade​

Use the repository's supported upgrade workflow. It can traverse consecutive majors, create a backup for each hop, quiesce cron, migrate schema and apps, process background jobs, and verify the runtime before continuing.

Recreation, platform upgrades, and optional sidecar refreshes are distinct operations. Follow the target instance's actual environment and topology. A Q-Chat shared-interface update, for example, needs compatible platform, Hub, and External Auth sources; a healthy old container alone does not validate the new interface. Do not replace credentials or delete journals as generic cleanup.

If schema work has started and a hop fails, preserve maintenance mode and the upgrade journal. Correct the specific failure and resume the original final target. Do not arbitrarily retarget the incomplete hop or change proxy topology.

After the upgrade​

Verify sign-in and refresh, Files, Talk, scheduled jobs, notifications, QDN gateway access, enabled custom apps, proxy headers, and backup retention. Record the exact installed versions and any temporary compatibility action.