From bcbf8a5e5719cf0440fc11ffad6f5face99aa673 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcel=20M=C3=BCller?= Date: Fri, 16 Jun 2023 09:20:06 +0200 Subject: [PATCH] Add note about migrations run by background jobs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marcel Müller --- admin_manual/maintenance/upgrade.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/admin_manual/maintenance/upgrade.rst b/admin_manual/maintenance/upgrade.rst index 263183abe..aa209a933 100644 --- a/admin_manual/maintenance/upgrade.rst +++ b/admin_manual/maintenance/upgrade.rst @@ -28,6 +28,14 @@ Nextcloud must be upgraded step by step: * **You cannot skip major releases.** Please re-run the upgrade until you have reached the highest available (or applicable) release. * Example: 18.0.5 -> 18.0.11 -> 19.0.5 -> 20.0.2 +**Wait for background migrations to finish after major upgrades**. After upgrading to a new major version, some migrations are scheduled to run +as a background job. If you plan to upgrade directly to another major version (e.g. 24 -> 25 -> 26) you need to make sure these +migrations were executed before starting the next upgrade. To do so you should run the ``cron.php`` file 2-3 times, for example:: + + $ sudo -u www-data php -f /var/www/nextcloud/cron.php + +For more information about background jobs see :doc:`../configuration_server/background_jobs_configuration`. + **Upgrading is disruptive**. Your Nextcloud server will be put into maintenance mode, so your users will be locked out until the upgrade is completed. Large installations may take several hours to complete the upgrade. Nevertheless usual