Upgrade from 1.1 to 2.x - Revision history

L.Leahu-Vladucu: Consistently mention apt instead of apt-get for newer releases

2026-06-08T06:36:12Z

Consistently mention apt instead of apt-get for newer releases

← Older revision		Revision as of 06:36, 8 June 2026
Line 17:		Line 17:
	* <code>archive.debian.org</code> instead of <code>*.debian.org</code>		* <code>archive.debian.org</code> instead of <code>*.debian.org</code>
	* <code>archive.proxmox.com</code> instead of <code>*.proxmox.com</code>		* <code>archive.proxmox.com</code> instead of <code>*.proxmox.com</code>
	* In case certificate errors occur while running <code>apt~~-get~~ update</code>, use HTTP instead of HTTPS for the repositories.		* In case certificate errors occur while running <code>apt update</code>, use HTTP instead of HTTPS for the repositories.

L.Leahu-Vladucu: Update links to contain information regarding archive CDNs

2026-05-22T13:55:34Z

Update links to contain information regarding archive CDNs

← Older revision		Revision as of 13:55, 22 May 2026
Line 13:		Line 13:

	Do not carry out the upgrade via the web-interface (GUI) console, as this will get interrupted during the upgrade.		Do not carry out the upgrade via the web-interface (GUI) console, as this will get interrupted during the upgrade.

			Old releases must use [https://forum.proxmox.com/threads/new-archive-cdn-for-end-of-life-eol-releases.178957/ the archive CDN for Proxmox] and [https://www.debian.org/distrib/archive for Debian], so make sure that all repositories in <code>/etc/apt/sources.list</code> and <code>/etc/apt/sources.list.d/*.list</code> use:
			* <code>archive.debian.org</code> instead of <code>*.debian.org</code>
			* <code>archive.proxmox.com</code> instead of <code>*.proxmox.com</code>
			* In case certificate errors occur while running <code>apt-get update</code>, use HTTP instead of HTTPS for the repositories.


	* Upgrade to the latest version of Proxmox Backup Server 1.1:		* Upgrade to the latest version of Proxmox Backup Server 1.1:
Line 56:		Line 62:

	Make sure to also edit all the extra files you added in /etc/apt/sources.list.d/ to Bullseye accordingly.		Make sure to also edit all the extra files you added in /etc/apt/sources.list.d/ to Bullseye accordingly.

			In case [https://forum.proxmox.com/threads/new-archive-cdn-for-end-of-life-eol-releases.178957/ the archive CDN for Proxmox] and [https://www.debian.org/distrib/archive for Debian] have been used, please switch back to the normal [https://pve.proxmox.com/wiki/Package_Repositories Package Repositories].

	Finally, update the repositories' package index:		Finally, update the repositories' package index:

Tlamprecht at 05:50, 14 June 2023

2023-06-14T05:50:10Z

← Older revision		Revision as of 05:50, 14 June 2023
Line 98:		Line 98:
	As a Debian based Distribution, Proxmox Backup Server is affected by most issues and changes affecting Debian.		As a Debian based Distribution, Proxmox Backup Server is affected by most issues and changes affecting Debian.
	Thus, make sure to read the [https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html Upgrade specific issues for bullseye]		Thus, make sure to read the [https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html Upgrade specific issues for bullseye]

			[[Category: Upgrade]]

Dwhyte: /* Install alongside Proxmox VE */

2021-07-13T12:03:11Z

Install alongside Proxmox VE

← Older revision		Revision as of 12:03, 13 July 2021
Line 29:		Line 29:
	In-place upgrades are carried out via APT. Familiarity with APT is required to proceed with this upgrade mechanism.		In-place upgrades are carried out via APT. Familiarity with APT is required to proceed with this upgrade mechanism.

	=== ~~Install~~ alongside Proxmox VE ===		=== Installed alongside Proxmox VE ===

	For systems with Proxmox VE and Proxmox Backup Server installed together, you should also read the [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 Proxmox VE upgrade from 6.x to 7.0 how-to] carefully.		For systems with Proxmox VE and Proxmox Backup Server installed together, you should also read the [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 Proxmox VE upgrade from 6.x to 7.0 how-to] carefully.

Dwhyte: /* Co-Installed with Proxmox VE */

2021-07-13T12:02:37Z

Co-Installed with Proxmox VE

← Older revision		Revision as of 12:02, 13 July 2021
Line 29:		Line 29:
	In-place upgrades are carried out via APT. Familiarity with APT is required to proceed with this upgrade mechanism.		In-place upgrades are carried out via APT. Familiarity with APT is required to proceed with this upgrade mechanism.

	=== ~~Co-Installed~~ ~~with~~ Proxmox VE ===		=== Install alongside Proxmox VE ===

	For ~~co-installed~~ Proxmox VE and Proxmox Backup Server ~~setups~~ you should also ~~closely~~ read the [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 Proxmox VE upgrade from 6.x to 7.0 how-to].		For systems with Proxmox VE and Proxmox Backup Server installed together, you should also read the [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 Proxmox VE upgrade from 6.x to 7.0 how-to] carefully.

	You can upgrade both in one go by syncing the ~~step~~ ~~when~~ the APT ~~repository~~ ~~get~~ changed.		You can upgrade both in one go, by syncing the steps in which the APT repositories are changed.

	== Actions step-by-step ==		== Actions step-by-step ==

Tlamprecht: /* In-place Upgrade */

2021-07-13T11:19:12Z

In-place Upgrade

← Older revision		Revision as of 11:19, 13 July 2021
Line 27:		Line 27:
	df -h /		df -h /

	In-place upgrades are carried out via APT. ~~'''~~Familiarity with APT is required to proceed with this upgrade mechanism. ~~'''~~		In-place upgrades are carried out via APT. Familiarity with APT is required to proceed with this upgrade mechanism.

			=== Co-Installed with Proxmox VE ===

			For co-installed Proxmox VE and Proxmox Backup Server setups you should also closely read the [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 Proxmox VE upgrade from 6.x to 7.0 how-to].

			You can upgrade both in one go by syncing the step when the APT repository get changed.

	== Actions step-by-step ==		== Actions step-by-step ==

S.ivanov: /* Upgrade the system */

2021-07-13T09:53:56Z

Upgrade the system

← Older revision		Revision as of 09:53, 13 July 2021
Line 65:		Line 65:
	=== Upgrade the system ===		=== Upgrade the system ===

	Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the dist-upgrade can be finished in 5 minutes. While the packages are being upgraded certain operations and requests to the API might fail (~~e.g.~~ logging in as system user in the <code>pam</code> realm)		Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the dist-upgrade can be finished in 5 minutes. While the packages are being upgraded certain operations and requests to the API might fail (for example logging in as system user in the <code>pam</code> realm)

	To get the initial set of upgraded packages, run:		To get the initial set of upgraded packages, run:

S.ivanov: /* Upgrade the system */

2021-07-13T09:53:35Z

Upgrade the system

← Older revision		Revision as of 09:53, 13 July 2021
Line 65:		Line 65:
	=== Upgrade the system ===		=== Upgrade the system ===

	Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the dist-upgrade can be finished in 5 minutes.		Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the dist-upgrade can be finished in 5 minutes. While the packages are being upgraded certain operations and requests to the API might fail (e.g. logging in as system user in the <code>pam</code> realm)

	To get the initial set of upgraded packages, run:		To get the initial set of upgraded packages, run:

S.ivanov: /* Stop services before upgrade */

2021-07-13T09:52:22Z

Stop services before upgrade

← Older revision		Revision as of 09:52, 13 July 2021
Line 58:		Line 58:

	This is only necessary if you use tape backup, as the lock file's path has been changed. Alternatively, you can also ensure that no tape-related backup or restore jobs are running during the upgrade.		This is only necessary if you use tape backup, as the lock file's path has been changed. Alternatively, you can also ensure that no tape-related backup or restore jobs are running during the upgrade.

			Note that stopping the services will abort all running tasks (backup, restore, garbage-collect, etc.), so make sure none is active.

	systemctl stop proxmox-backup-proxy.service proxmox-backup.service		systemctl stop proxmox-backup-proxy.service proxmox-backup.service

Martin: /* Preconditions */

2021-07-13T09:21:43Z

Preconditions

← Older revision		Revision as of 09:21, 13 July 2021
Line 22:		Line 22:

	* Make a backup of <code>/etc/proxmox-backup</code> to ensure that in the worst case, any relevant configuration can be recovered:		* Make a backup of <code>/etc/proxmox-backup</code> to ensure that in the worst case, any relevant configuration can be recovered:
	tar czf "pbs1-etc-backup-$(date -I).tar.gz" -C /etc proxmox-backup		tar czf "pbs1-etc-backup-$(date -I).tar.gz" -C "/etc" "proxmox-backup"

	* Ensure that you have at least 4 GiB free disk space on the root mount point:		* Ensure that you have at least 4 GiB free disk space on the root mount point: