From: Graeme Seaton <lists@graemes.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Templates starting on backup
Date: Mon, 5 Oct 2020 17:49:44 +0100 [thread overview]
Message-ID: <de003b76-6b5e-86f3-6ba0-ff5f791ad0d0@graemes.com> (raw)
In-Reply-To: <fa4f0c2b-fbbc-3b76-6dae-8b9a956d0ff1@proxmox.com>
The reason I moved them was that my sense of taste didn't like having
the templates intermingled with the running hosts in the server view ;-)
Having all of the templates stored on a single host also provides a very
simplistic way of making sure the running VM's are backed up as quickly
as possible without being delayed by templates on the same server.
Being on a single host means that the templates are backed up on a
single separate 'thread'. I could probably achieve something similar by
placing all of the templates in a very high id range.
No biggie - just thought I'd feed back about the failures.
Regards,
Graeme
On 05/10/2020 15:40, Thomas Lamprecht wrote:
> On 05.10.20 16:21, Graeme Seaton wrote:
>> On 05/10/2020 14:42, Thomas Lamprecht wrote:
>>> What HW differences are talking here?
>> In one case CPU type/Numa/hugepages. In others vmbr's.
> Why not just leave it at the "OK" hosts, if you're using HA you could
> add it to a group restricted to those hosts it is compatible with.
>
> We may reduce the configuration of a template started fort backup a bit,
> though.
>
> cheers,
> Thomas
>
>
prev parent reply other threads:[~2020-10-05 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:15 Graeme Seaton
2020-10-05 13:42 ` Thomas Lamprecht
2020-10-05 14:21 ` Graeme Seaton
2020-10-05 14:40 ` Thomas Lamprecht
2020-10-05 16:49 ` Graeme Seaton [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=de003b76-6b5e-86f3-6ba0-ff5f791ad0d0@graemes.com \
--to=lists@graemes.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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