From: "Alain Péan" <alain.pean@c2n.upsaclay.fr>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] (no subject)
Date: Tue, 24 Aug 2021 17:36:04 +0200 [thread overview]
Message-ID: <81c194c7-1d5f-1178-2200-51f80d093eb1@c2n.upsaclay.fr> (raw)
In-Reply-To: <CALt2oz5N_Wmp5K4JUxuC3cmVayEEfErVHPuM7sU8BU7TM_HOXQ@mail.gmail.com>
Le 24/08/2021 à 17:13, Leandro Roggerone a écrit :
> Hello , Martin.
> Im still in pve 6.04.
> I was looking at the document you pointed out (Upgrade from 6.x to 7.0)
> It is frustrating to see that upgrading is a very difficult process.
> My cluster contains 2 servers.
> Both are in production , at 50 - 60 % storage and memory capacity so it is
> not easy for me to create backups and move VMs.
>
> I will study how to proceed with this update from pve 6 to 7.
> Perhaps:
> Adding a third new box already running version 7.
> Adding a networking storage ? need to check out wich one.
>
> Meanwhile , until I can go to pve 7 , I think I should upgrate to latest
> pve 6 and disable automatic upgrades ...
> Do you think it is ok ?
Hello Leandro,
If you are under Proxmox 6.4, you cannot move "accidentaly", by software
upgrades, to 7.0. Because 6.x is based on Debian 10, and 7.x on Debian
11, so you have to change the repository to point to the newer release.
What I do personnaly is to test the upgrade on a test cluster, to see
how it works. I have an old server on which I setup a nested proxmox ve
cluster with three small VMs. I test the upgrade process on this nested
cluster, before applying it to production cluster.
For your produxtion cluster, you should have backups of your VMs (for
example on an NFS storage). It would be indeed a good thing to have à
third host to have a minimum cluster with quorum.
Good luck !
Alain
--
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255
next prev parent reply other threads:[~2021-08-24 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:37 Leandro Roggerone
[not found] ` <mailman.458.1629211453.329.pve-user@lists.proxmox.com>
2021-08-18 13:19 ` Leandro Roggerone
[not found] ` <e5a1f5ef-ab9b-9283-cd90-6aba6acc35ba@holub.co.at>
2021-08-24 15:13 ` Leandro Roggerone
2021-08-24 15:36 ` Alain Péan [this message]
[not found] ` <1aca635b-412d-c199-2382-629b16457939@holub.co.at>
2021-08-25 12:11 ` Leandro Roggerone
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 23:11 Christian Karg
[not found] <CAGehcqHmTqfjBRwt61hWjjA1CQm8inajfS0=EOqCPrAdmGUheA@mail.gmail.com>
2023-07-24 8:58 ` Aaron Lauterer
2021-02-25 20:18 Aaron Wood
2021-02-26 11:17 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81c194c7-1d5f-1178-2200-51f80d093eb1@c2n.upsaclay.fr \
--to=alain.pean@c2n.upsaclay.fr \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox