.. /* * This file is part of the SavaPage project . * Copyright (c) 2026 Datraverse B.V. * Author: Rijk Ravestein. * * SPDX-FileCopyrightText: (c) 2020 Datraverse B.V. * SPDX-License-Identifier: CC-BY-SA-4.0 * * For more information, please contact Datraverse B.V. at this * address: info@datraverse.com */ .. _app-migrating: .. figure:: ../images/manual/savapage-logo-no-text-100px.png :width: 75px Migrating to a New Server ========================= .. admonition:: |ADMONITION_TABLE_OF_CONTENTS| - :numref:`{number}. {name} ` - :numref:`{number}. {name} ` - :numref:`{number}. {name} ` - :numref:`{number}. {name} ` - :numref:`{number}. {name} ` - :numref:`{number}. {name} ` Migrating to a new server is a major task. Administrators should block out at a minimum two hours, and should select a time where downtime will be of minimum disruption to end-users. This section describes how to migrate |PRODUCT_NAME| to a new system so that all data is moved to the new system. To ensure a smooth migration it is strongly recommended that the versions of |PRODUCT_NAME| on both the old and new servers are the same. The easiest way to achieve this is to upgrade the old server to the latest version, and then install the latest version on the new server. *Please read the sections below in full before conducting your migration.* .. _app-migrating-upgrade-old-server: Upgrade Old Server ------------------ Upgrade the old server to the latest version: 1. Download the latest available version available via the |PRODUCT_NAME| |RST_SAVAPAGE_WEBSITE|. .. RST_HTML_NEWLINE 2. Install the upgrade by following the steps in |RST_LINK_APPENDIX_UPGRADING|. .. RST_HTML_NEWLINE 3. After the upgrade is complete, check that everything is working as expected.