Search results

Page title matches

• Host-bios-upgrade
  2 KB (346 words) - 21:38, 11 January 2018
• Upgrade from 3.x to 4.x
  #REDIRECT [[Upgrade from 3.x to 4.x (Debian wheezy to jessie)]]
  63 bytes (10 words) - 20:02, 30 April 2016
• Upgrade from 5.x to 6.0
  Proxmox VE 6.x introduces several new major features. Carefully plan the upgrade, make and verify backups before beginning, and test extensively. Depending ...ote:''' A valid and tested backup is ''always'' needed before starting the upgrade process. Test the backup beforehand in a test lab setup.
  13 KB (2,130 words) - 08:15, 21 January 2022
• Upgrade from 6.x to 7.0
  Proxmox VE 7.x introduces several new major features. You should plan the upgrade carefully, make and verify backups before beginning, and test extensively. ...e:''' A valid and tested backup is ''always'' required before starting the upgrade process. Test the backup beforehand in a test lab setup.
  22 KB (3,416 words) - 12:46, 2 June 2023
• Upgrade from 7 to 8
  Proxmox VE 8.x introduces several new major features. You should plan the upgrade carefully, make and verify backups before beginning, and test extensively. ...e:''' A valid and tested backup is ''always'' required before starting the upgrade process. Test the backup beforehand in a test lab setup.
  23 KB (3,608 words) - 08:41, 23 October 2023
• Upgrade from 1.9 to 2.0
  *In-place upgrade via upgrade script In-place upgrade from 1.9 to 2.0 is a demanding task, but we provide an upgrade script to simplify this. You can use the script to update a 1.9 default ins
  4 KB (714 words) - 08:18, 21 January 2022
• Upgrade from 2.3 to 3.0
  *In-place upgrade via script (recommended) == In-place upgrade via script ==
  5 KB (848 words) - 08:18, 21 January 2022
• Upgrade from 4.x to 5.0
  ...everal manual steps are required, including some downtime. NEVER start the upgrade process without a valid backup and without testing the same in a test lab s ...og, or any other third party packages, you need to make sure that you also upgrade these package to Debian Stretch.
  7 KB (1,150 words) - 08:14, 21 January 2022
• Upgrade from 3.x to 4.0
  ...everal manual steps are required, including some downtime. NEVER start the upgrade process without a valid backup and without testing the same in a test lab s ...RBD or any other third party packages, you need to make sure that you also upgrade these package to Debian Jessie.
  10 KB (1,573 words) - 08:15, 21 January 2022
• Upgrade from 4.0 to 4.1 using the ISO image
  #REDIRECT [[Upgrade a 4.x Installation using a newr ISO image]]
  63 bytes (10 words) - 11:31, 4 November 2016
• Upgrade a 4.x Installation using a newer ISO image
  ...ubscription or you have enabled the "pve-no-subscription" repositories the upgrade process should be as easy as upgrading packages, i.e. apt-get update && apt-get dist-upgrade
  3 KB (431 words) - 11:32, 4 November 2016
• Upgrade from 3.x to 4.x (Debian wheezy to jessie)
  #REDIRECT [[Upgrade from 3.x to 4.0]]
  37 bytes (5 words) - 14:26, 28 May 2016
• Upgrade a 4.x Installation using a newr ISO image
  #REDIRECT [[Upgrade a 4.x Installation using a newer ISO image]]
  64 bytes (10 words) - 11:32, 4 November 2016

Page text matches

• Upgrade from 3.x to 4.x (Debian wheezy to jessie)
  #REDIRECT [[Upgrade from 3.x to 4.0]]
  37 bytes (5 words) - 14:26, 28 May 2016
• Upgrade from 4.0 to 4.1 using the ISO image
  #REDIRECT [[Upgrade a 4.x Installation using a newr ISO image]]
  63 bytes (10 words) - 11:31, 4 November 2016
• Upgrade a 4.x Installation using a newr ISO image
  #REDIRECT [[Upgrade a 4.x Installation using a newer ISO image]]
  64 bytes (10 words) - 11:32, 4 November 2016
• Upgrade from 3.x to 4.x
  #REDIRECT [[Upgrade from 3.x to 4.x (Debian wheezy to jessie)]]
  63 bytes (10 words) - 20:02, 30 April 2016
• Upgrade a 4.x Installation using a newer ISO image
  ...ubscription or you have enabled the "pve-no-subscription" repositories the upgrade process should be as easy as upgrading packages, i.e. apt-get update && apt-get dist-upgrade
  3 KB (431 words) - 11:32, 4 November 2016
• Upgrade from 1.9 to 2.0
  *In-place upgrade via upgrade script In-place upgrade from 1.9 to 2.0 is a demanding task, but we provide an upgrade script to simplify this. You can use the script to update a 1.9 default ins
  4 KB (714 words) - 08:18, 21 January 2022
• Ceph Jewel to Luminous
  This HOWTO explains the upgrade from Ceph Jewel to Luminous (12.2.0 or higher) on Proxmox VE 4.x in prepara ...st Ceph version supported in pveceph in PVE 4.x is Ceph Jewel (10.2.x). An upgrade to Ceph Luminous (12.2.x) is only possible temporarily as first step of upg
  4 KB (672 words) - 14:22, 31 May 2023
• Pvebash
  ...d and EOL releases like Proxmox VE 3.4 we recommend to [[:Category:Upgrade|Upgrade]] as soon as possible! |warn}}
  1 KB (226 words) - 14:21, 31 May 2023
• Ceph Hammer to Jewel
  This HOWTO explains the upgrade from Ceph Hammer to Jewel (10.2.5 or higher). == Upgrade ==
  5 KB (784 words) - 14:21, 31 May 2023
• Upgrade from 2.3 to 3.0
  *In-place upgrade via script (recommended) == In-place upgrade via script ==
  5 KB (848 words) - 08:18, 21 January 2022
• Server certificate verification failed when updating
  * In July 2017, after waiting one year to let people on the PVE 4.x branch upgrade, we changed the SSL certificate on enterprise.proxmox.com to use a let's en Hence people running old versions who did not upgrade in the one year time slot expect a StartCom signed SSL certificate, and get
  1 KB (196 words) - 09:09, 18 July 2017
• Upgrade from 4.x to 5.0
  ...everal manual steps are required, including some downtime. NEVER start the upgrade process without a valid backup and without testing the same in a test lab s ...og, or any other third party packages, you need to make sure that you also upgrade these package to Debian Stretch.
  7 KB (1,150 words) - 08:14, 21 January 2022
• Ceph Pacific to Quincy
  This article explains how to upgrade Ceph from Pacific to Quincy (17.2.0 or higher) on Proxmox VE 7.2 and newer ...e-osd-release'' flag is not set to the appropriate release after a cluster upgrade.
  7 KB (1,127 words) - 13:01, 28 August 2023
• Ceph Octopus to Pacific
  This article explains how to upgrade Ceph from Octopus to Pacific (16.2.4 or higher) on Proxmox VE 7.x. *: If not, please see the [[Ceph Nautilus to Octopus]] upgrade guide.
  9 KB (1,571 words) - 14:22, 31 May 2023
• Ceph Quincy to Reef
  This article explains how to upgrade Ceph from Quincy (17.2+) to Reef (18.2+) on Proxmox VE 8. ...e-osd-release'' flag is not set to the appropriate release after a cluster upgrade.
  7 KB (1,190 words) - 08:51, 4 January 2024
• System Software Updates
  # apt-get dist-upgrade
  698 bytes (96 words) - 17:25, 13 February 2020
• FAQ
  How can I upgrade Proxmox VE to the next point release? apt full-upgrade
  6 KB (924 words) - 14:11, 23 November 2023
• Quick installation
  * For upgrading 6.x to 7.0, see [[Upgrade from 6.x to 7.0|Upgrade from Proxmox VE 6.x to 7.x]] * For upgrading 5.x to 6.0, see [[Upgrade from 5.x to 6.0]]
  4 KB (617 words) - 17:57, 3 February 2022
• Main Page
  You can also upgrade existing Proxmox VE installations to the next major release: * [[Upgrade from 7 to 8|Upgrade from Proxmox VE 7 to 8]]
  5 KB (696 words) - 17:10, 13 February 2024
• Upgrade from 5.x to 6.0
  Proxmox VE 6.x introduces several new major features. Carefully plan the upgrade, make and verify backups before beginning, and test extensively. Depending ...ote:''' A valid and tested backup is ''always'' needed before starting the upgrade process. Test the backup beforehand in a test lab setup.
  13 KB (2,130 words) - 08:15, 21 January 2022