From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] BackupServer Feature Request - Compression display
Date: Mon, 13 Jul 2020 11:10:40 +1000 [thread overview]
Message-ID: <4e38b093-6a1f-1a04-1ebb-dfa6014f3196@gmail.com> (raw)
In-Reply-To: <568120523.549.1594571306775@webmail.proxmox.com>
On 13/07/2020 2:28 am, Dietmar Maurer wrote:
> We do incremental backup using dirty bitmaps. Gathering
> those informations for all reused chunks would slow down
> the whole backup process, so I am quite unsure if we
> want to do that ...
Maybe I'm missing your point, but I wasn't meaning the incremental
display of read/write during backup (though I had noticed that changed),
but just the end result of how much data is stored.
There is no easy way to tell how much space a backup is taking on the
backup server?
--
Lindsay
next prev parent reply other threads:[~2020-07-13 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 8:53 Lindsay Mathieson
2020-07-12 16:28 ` Dietmar Maurer
2020-07-13 1:10 ` Lindsay Mathieson [this message]
2020-07-13 5:59 ` Dietmar Maurer
2020-07-13 23:21 ` Lindsay Mathieson
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=4e38b093-6a1f-1a04-1ebb-dfa6014f3196@gmail.com \
--to=lindsay.mathieson@gmail.com \
--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