Upgrade from 2 to 3 - Revision history

A.lauterer: /* General */ fix link

2023-10-24T08:58:52Z

General: fix link

← Older revision		Revision as of 08:58, 24 October 2023
Line 149:		Line 149:
	Thus, ensure that you read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Debian Bookworm], for example the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#changes-to-packages-that-set-the-system-clock transition from classic NTP to NTPsec]		Thus, ensure that you read the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html upgrade specific issues for Debian Bookworm], for example the [https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#changes-to-packages-that-set-the-system-clock transition from classic NTP to NTPsec]

	Please also check the known issue list from the Proxmox Backup Server 3.0 changelog: https://pbs.proxmox.com/wiki/Roadmap#3.0-known-issues		Please also check the known issue list from the Proxmox Backup Server 3.0 changelog: https://pbs.proxmox.com/wiki/index.php/Roadmap#3.0-known-issues

	== Older Hardware and New 6.2 Kernel ==		== Older Hardware and New 6.2 Kernel ==

Tlamprecht: /* Upgrade the System */

2023-08-24T09:22:48Z

Upgrade the System

← Older revision		Revision as of 09:22, 24 August 2023
Line 101:		Line 101:
	apt dist-upgrade		apt dist-upgrade

	During the above step, you will be asked to approve changes to configuration files, where the default config has been updated by their respective package.		During the above step, you will be asked to approve changes to configuration files and some service restarts, where the default config has been updated by their respective package.

			For questions about service restarts (like <code>Restart services during package upgrades without asking?</code>) use the default if unsure, as the reboot after the upgrade will restart all services cleanly anyway.
⚫	It's suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup.

		⚫	For questions about (default) configuration changes, it's suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup.

	Common configuration files with changes, and the recommended choices are:		Common configuration files with changes, and the recommended choices are:

Tlamprecht: /* Older Hardware and New 6.2 Kernel */

2023-08-24T09:16:57Z

Older Hardware and New 6.2 Kernel

← Older revision		Revision as of 09:16, 24 August 2023
Line 152:		Line 152:

	Compatibility of old hardware (released >= 10 years ago) is not as thoroughly tested as more recent hardware.		Compatibility of old hardware (released >= 10 years ago) is not as thoroughly tested as more recent hardware.
	For old hardware we highly recommend testing compatibility of Proxmox VE 8 with identical (or at least similar) hardware before upgrading any production machines.		For old hardware we highly recommend testing compatibility of Proxmox Backup Server 3 with identical (or at least similar) hardware before upgrading any production machines.

	We will expand this section with potential pitfalls and workarounds once they arise.		We will expand this section with potential pitfalls and workarounds once they arise.

Tlamprecht: /* Systemd-Boot (for ZFS on Root and UEFI Systems Only) */

2023-08-24T09:14:56Z

Systemd-Boot (for ZFS on Root and UEFI Systems Only)

← Older revision		Revision as of 09:14, 24 August 2023
Line 174:		Line 174:
	== Systemd-Boot (for ZFS on Root and UEFI Systems Only) ==		== Systemd-Boot (for ZFS on Root and UEFI Systems Only) ==

	Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>~~pve7to8~~</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.		Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pbs2to3</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.

	The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox Backup Server 2.4 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox Backup Server installer.		The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox Backup Server 2.4 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox Backup Server installer.

Tlamprecht: /* Update Debian Base Repositories to Bookworm */

2023-08-24T09:14:28Z

Update Debian Base Repositories to Bookworm

← Older revision		Revision as of 09:14, 24 August 2023
Line 69:		Line 69:
	sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list		sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list

	Ensure that there are no remaining Debian Bullseye specific repositories left~~, if~~ ~~you~~ can ~~use~~ ~~the~~ <code>#</code> symbol at the start of the respective line to comment ~~these~~ ~~repositories~~ out.		Ensure that there are no remaining Debian Bullseye specific repositories left. You can place a <code>#</code> symbol at the start of the respective line to comment such a repository out, disabling it.
	Check all files in the </code>/etc/apt/sources.list.d/~~pve~~-enterprise.list</code> and <code>/etc/apt/sources.list</code> ~~and see [[Package_Repositories]] for the correct Proxmox VE 8 / Debian Bookworm repositories~~.		Check all files in the </code>/etc/apt/sources.list.d/</code> folder (like <code>pbs-enterprise.list</code>) and also the top-level <code>/etc/apt/sources.list</code> file.
			See [https://pbs.proxmox.com/docs/installation.html#debian-package-repositories Package Repositories] section in the reference docs for the correct Proxmox Backup Server 3 / Debian Bookworm repositories.

	==== Add the Proxmox Backup Server 3 Package Repository ====		==== Add the Proxmox Backup Server 3 Package Repository ====

Tlamprecht: /* Systemd-Boot (for ZFS on Root and UEFI Systems Only) */

2023-06-29T10:27:27Z

Systemd-Boot (for ZFS on Root and UEFI Systems Only)

← Older revision		Revision as of 10:27, 29 June 2023
Line 175:		Line 175:
	Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pve7to8</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.		Systems booting via UEFI from a ZFS on root setup should install the <code>systemd-boot</code> package after the upgrade. You will get a Warning from the <code>pve7to8</code> script after the upgrade if your system is affected - in all other cases you can safely ignore this point.

	The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox VE 7.4 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox VE installer.		The <code>systemd-boot</code> was split out from the <code>systemd</code> package for Debian Bookworm based releases. It won't get installed automatically upon upgrade from Proxmox Backup Server 2.4 as it can cause trouble on systems not booting from UEFI with ZFS on root setup by the Proxmox Backup Server installer.

	Systems which have ZFS on root and boot in UEFI mode will need to manually install it if they need to initialize a new ESP (see the output of <code>proxmox-boot-tool status</code> and the [https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_determine_bootloader_used relevant documentation]).		Systems which have ZFS on root and boot in UEFI mode will need to manually install it if they need to initialize a new ESP (see the output of <code>proxmox-boot-tool status</code> and the [https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_determine_bootloader_used relevant documentation]).

Tlamprecht: /* Upgrade the System */

2023-06-29T08:48:55Z

Upgrade the System

← Older revision		Revision as of 08:48, 29 June 2023
Line 105:		Line 105:

	Common configuration files with changes, and the recommended choices are:		Common configuration files with changes, and the recommended choices are:
	* <code>/etc/issue</code> -> Proxmox VE will auto-generate this file on boot, and it has only cosmetic effects on the login console.		* <code>/etc/issue</code> -> Proxmox Backup Server will auto-generate this file on boot, and it has only cosmetic effects on the login console.
	*: Using the default "No" (keep your currently-installed version) is safe here.		*: Using the default "No" (keep your currently-installed version) is safe here.

	* <code>/etc/lvm/lvm.conf</code> -> Changes relevant for Proxmox VE will be updated, and a newer config version might be useful.
	*: If you did not make extra changes yourself and are unsure it's suggested to choose "Yes" (install the package maintainer's version) here.
	* <code>/etc/ssh/sshd_config</code> -> If you have not changed this file manually, the only differences should be a replacement of <code>ChallengeResponseAuthentication no</code> with <code>KbdInteractiveAuthentication no</code> and some irrelevant changes in comments (lines starting with <code>#</code>).		* <code>/etc/ssh/sshd_config</code> -> If you have not changed this file manually, the only differences should be a replacement of <code>ChallengeResponseAuthentication no</code> with <code>KbdInteractiveAuthentication no</code> and some irrelevant changes in comments (lines starting with <code>#</code>).
	*: If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated <code>ChallengeResponseAuthentication</code> option. If there are other changes, we suggest to inspect them closely and decide accordingly.		*: If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated <code>ChallengeResponseAuthentication</code> option. If there are other changes, we suggest to inspect them closely and decide accordingly.

	* <code>/etc/default/grub</code> -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option.		* <code>/etc/default/grub</code> -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option.
	*: It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with <code>#</code>) are not relevant.		*: It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with <code>#</code>) are not relevant.

Tlamprecht: /* Following the Proxmox Backup Server upgrade */

2023-06-29T08:21:38Z

Following the Proxmox Backup Server upgrade

← Older revision		Revision as of 08:21, 29 June 2023
Line 123:		Line 123:

	== Following the Proxmox Backup Server upgrade ==		== Following the Proxmox Backup Server upgrade ==

			Empty the browser cache and/or force-reload (<kbd>CTRL</kbd> + <kbd>SHIFT</kbd> + <kbd>R</kbd>, or for MacOS <kbd>⌘</kbd> + <kbd>Alt</kbd> + <kbd>R</kbd>) the Web UI.

			=== Check Status of Services ===

	Check that the statuses of the main services are <code>active (running)</code>		Check that the statuses of the main services are <code>active (running)</code>

Martin: Proxmox Backup Server 3.0 release

2023-06-28T09:07:01Z

Proxmox Backup Server 3.0 release

Show changes

Tlamprecht: reserve

2023-06-26T13:39:21Z

reserve

New page