public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximilian Hill <mhill@inett.de>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Poor client backup performance [Bug#3811]
Date: Mon, 3 Jan 2022 13:38:10 +0100	[thread overview]
Message-ID: <YdLuMhBWeB/SlUGl@inett.de> (raw)
In-Reply-To: <CA8B2BB6-470B-4081-99E4-40ABBB3CA9AE@tuxis.nl>

Hi,

we ourselves don't have this problem, because we mostly use PBS to back
up QEMU VMs, but whenever we use containers, this becomes a problem for
us as well.

For containers this could be solved using rbd/zfs diffs of snapshots and
QEMU backups would benefit as well, but this problem would stay a problem
for host backups.

It's way too easy to push Proxmox Bakup (Server) to it's limits right now.


On Thu, Dec 30, 2021 at 05:30:24PM +0100, Mark Schouten wrote:
> Hi Lubomir,
> 
> I think it’s a bit more nuanced, but indeed, the current situation is quite unusable. I’ll have to move my file-based backups back to my previous situation.
> 
> My bug has rightfully been closed as a duplicate, but maybe if you have any ideas you could share them here: https://bugzilla.proxmox.com/show_bug.cgi?id=3174 <https://bugzilla.proxmox.com/show_bug.cgi?id=3174>
> 
> I’d like to see this fixed too, and maybe with all brains combined, we actually can :)
>  
> — 
> Mark Schouten, CTO
> Tuxis B.V.
> mark@tuxis.nl
> 
> 
> 
> 
inett GmbH
>> Ihr IT Systemhaus in  Saarbrücken

Maximilian Hill


t: 0681-410993-0
e: mhill@inett.de
www.inett.de

Technische Fragen:
Support E-Mail: support@inett.de
Support Hotline: 0681-410993-42


inett GmbH | Geschäftsführung: Marco Gabriel | Amtsgericht Saarbrücken HRB 16588
> On 30 Dec 2021, at 11:49, Lubomir Apostolov <Lubomir.Apostolov@directique.com> wrote:
> > 
> > Hello, 
> > 
> > One year ago I talked about this here without success. 
> > 
> > Proxmox Backup has no differential read algorithm and no plans to do it. It handles only changes during current backup, but has to read every time all backup data. If you have 20Tb to backup every 3 hours, your storage must be able to read at at least 2Gb/s 24/7 and even more if you dare use your VMs at the same time. Complete design failure except for some dev/lab setups.
> > 
> > It could use snapshots from the underlying storage like ZFS or Ceph, but no, devs seem happy without it. A simple script for differential snapshot copy does a better job.
> > 
> > Best regards,
> > Lubomir
> > 
> > 
> > -------- Message d'origine --------
> > De : Mark Schouten <mark@tuxis.nl>
> > Date : 30/12/2021 10:07 (GMT+01:00)
> > À : pbs-devel <pbs-devel@lists.proxmox.com>
> > Objet : [pbs-devel] Poor client backup performance [Bug#3811]
> > 
> > Hi!
> > 
> > I switched a few servers to Proxmox Backup Server this week (a slow week :)), but am somewhat disappointed in the performance of the client. I created bug 3811 for it, and would like to help and assist in debugging this issue.
> > 
> > The mentioned server in the bug should backup about three times per day. Currently, the machine is working on it almost fulltime, because the backup takes more than 7 hours.
> > 
> > I think the client reads all files I every run, and I would expect stat’ing the files should be enough to determine whether a file should be re-read, but I’ve not spent a single second reading the code, so I do not have any more than suspicions.
> > 
> > As said, I’d like to help improving this situation, please let me know what you need from us.
> > 
> > https://bugzilla.proxmox.com/show_bug.cgi?id=3811 <https://bugzilla.proxmox.com/show_bug.cgi?id=3811>
> > 
> > Kind regards,
> > 
> > — 
> > Mark Schouten, CTO
> > Tuxis B.V.
> > mark@tuxis.nl <mailto:mark@tuxis.nl>_______________________________________________
> > pbs-devel mailing list
> > pbs-devel@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
> 

> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel




      parent reply	other threads:[~2022-01-03 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  8:35 Mark Schouten
2021-12-30 10:49 ` Lubomir Apostolov
2021-12-30 16:30   ` Mark Schouten
     [not found]     ` <b2257fcd-419a-4ff0-b179-a3ffd335fd77.4bf6da22-5cda-4597-b16d-3c88c4c3fb76.e8d364f1-5136-45b8-8da1-f60bc3f8a47a@emailsignatures365.codetwo.com>
2022-01-03 12:38       ` Maximilian Hill [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=YdLuMhBWeB/SlUGl@inett.de \
    --to=mhill@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal