From: Maximilian Hill <mhill@inett.de>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Cc: Marco Gabriel - inett GmbH <mgabriel@inett.de>
Subject: Re: [pbs-devel] Status of Garbage Collection marks in memory (not atime based)
Date: Fri, 9 Apr 2021 12:57:45 +0200 [thread overview]
Message-ID: <YHAzKR0NF/hOJtUr@inett.de> (raw)
In-Reply-To: <1293660294.1724.1617956034080@webmail.proxmox.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On Fri, Apr 09, 2021 at 10:13:54AM +0200, Dietmar Maurer wrote:
> > We use a CephFS as datastore in our test environment and this is rather slow because of the metadata updates. The in-memory based approach could possibly make a huge difference for CephFS based datastores.
>
> Besides, Proxmox Backup is designed to work with local storage.
> Using any Network based storage create a big amount of additional network
> traffic, and makes no real sense to me. You want(should) backup your Cepfs data
> to Proxmox Backup, not the other way around.
>
Well, if you are already running seperate ceph cluster with erasure coded
pools for other backups, that's not that bad of an idea.
But it shouldn't be the same cluster as the hot production storage,
thats right.
GC jobs cause a lot of writes in the metadata pool.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-09 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 8:13 Dietmar Maurer
[not found] ` <d16a9279-ec9e-4f8e-905c-2744b4455083.4bf6da22-5cda-4597-b16d-3c88c4c3fb76.9e105e32-a0ed-438f-8146-0b54ba60255f@emailsignatures365.codetwo.com>
2021-04-09 9:17 ` Marco Gabriel
2021-04-09 10:57 ` Maximilian Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-09 11:07 Dietmar Maurer
2021-04-09 8:08 Dietmar Maurer
2021-04-08 12:14 Marco Gabriel - inett GmbH
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=YHAzKR0NF/hOJtUr@inett.de \
--to=mhill@inett.de \
--cc=mgabriel@inett.de \
--cc=pbs-devel@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