From: Dominik Csapak <d.csapak@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/3] tape: media_catalog: add fast_catalog beside normal catalog
Date: Tue, 20 Jul 2021 09:01:40 +0200 [thread overview]
Message-ID: <362a96bd-54bb-206a-4de3-d5c162da7cc3@proxmox.com> (raw)
In-Reply-To: <509050131.1964.1626761748892@webmail.proxmox.com>
On 7/20/21 08:15, Dietmar Maurer wrote:
>
>> On 07/19/2021 4:55 PM Dominik Csapak <d.csapak@proxmox.com> wrote:
>>
>>
>> for some parts of the ui, we only need the snapshot list from the catalog,
>> and reading the whole catalog (can be multiple hundred MiB) is not
>> really necessary.
>>
>> Instead, on every commit of the catalog, write the complete content list
>> into a seperate .index file, that can be read to get only the snapshot
>> list.
>
> Commits can be quite frequent. Can we write on "close" only?
>
AFAICS from the code, during a backup to tape, we only commit on tape
end (the "close") or every 128GiB written to tape so not that often
(every ~7 minutes on LTO-8 with 300MB/s)
on tape restore though, we create a 'temporary database' which gets
commited on every archive restore
i'd suggest to either
* add an option to commit for writing the snapshot list, and only set it
on the last commit
* add some kind of 'finish' or 'close' function to the catalog, that
must be called
any favorites (or alternatives) ?
next prev parent reply other threads:[~2021-07-20 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 6:15 Dietmar Maurer
2021-07-20 7:01 ` Dominik Csapak [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 14:55 Dominik Csapak
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=362a96bd-54bb-206a-4de3-d5c162da7cc3@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=dietmar@proxmox.com \
--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