From: Luke Thompson <luke.t@tncrew.com.au>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Proxmox VE 7.0 released!
Date: Wed, 7 Jul 2021 10:22:17 +1000 [thread overview]
Message-ID: <37d76c34-e0a4-2fdc-8531-3b640c61e3be@tncrew.com.au> (raw)
In-Reply-To: <76ffd314-d6ea-391e-326f-eabefd44ebfd@gmail.com>
Re: the co-installation of PVE and PBS, that reads to me the same way
that you've described.
PBS can be installed alongside PVE, so I'd say if your nodes have both
installed then you're restricted from upgrading to PVE 7.0 until PBS 2.0
is released (and upgraded firstly).
Cheers,
Luke T.
On 7/7/21 9:50 am, Lindsay Mathieson wrote:
> On 6/07/2021 9:47 pm, Martin Maurer wrote:
>> It's our pleasure to announce the stable version 7.0 of Proxmox
>> Virtual Environment. It's based on the great Debian 11 "Bullseye" and
>> comes with a 5.11 kernel, QEMU 6.0, LXC 4.0, OpenZFS 2.0.4. and
>> countless enhancements and bugfixes.
>
> From the inplace upgrade notes
>
>> Co-installed Proxmox Backup Server: you must wait until Proxmox
>> Backup Server 2.0 is released!
>
> What does that mean? PBS installed on the same hardware as a proxmox
> node?
>
prev parent reply other threads:[~2021-07-07 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:47 Martin Maurer
2021-07-06 20:50 ` Alain péan
2021-07-07 0:30 ` Luke Thompson
2021-07-06 23:50 ` Lindsay Mathieson
2021-07-07 0:22 ` Luke Thompson [this message]
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=37d76c34-e0a4-2fdc-8531-3b640c61e3be@tncrew.com.au \
--to=luke.t@tncrew.com.au \
--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