public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Carsten Härle" <Carsten.Haerle@straightec.de>
To: <pve-devel@lists.proxmox.com>
Subject: [pve-devel] Improve container backup speed dramatically (factor 100-1000)
Date: Thu, 19 Nov 2020 20:29:26 +0100	[thread overview]
Message-ID: <57EF5F8B433A6742AD548ABECE78FE48539302@hal9001.straightec.lokal> (raw)

Container backup is very slow compared to VM backup. I have a 500 GB container (sftp server) with minimal changing files, but even the incremental bakcups take 2 hours with heavy disk activity. Almost nothing is transfered to the backup server. It seems that it it reads the whole container everytime, without any optimization. Before I did backup with zfs send it there it took only a couple of seconds or minutes for every didfferencal backup. 
 
See discussion here: https://forum.proxmox.com/threads/no-differantial-container-backup-with-big-containers.75676/#post-338868 <https://forum.proxmox.com/threads/no-differantial-container-backup-with-big-containers.75676/#post-338868> 
 
PBS is not storage agnostic but uses underlying snapshot feature according to the documentation: For container, the underlying snapshot feature of the file system ARE used, it already uses ZFS feature. 
https://pve.proxmox.com/wiki/Backup_and_Restore <https://pve.proxmox.com/wiki/Backup_and_Restore> 
 
For zfs file systems the set of changed file between snapshots can easy be displayed with "zfs diff", so PBS should use this feature to speed up large container backups dramatically. In my case it would be faktor about factor 1000! Alternatively the snapshots data can be accessed via the hidden .zfs directories, so PBS has knows which files changed and has access to the old and the new data.

 

https://bugzilla.proxmox.com/show_bug.cgi?id=3138

 



             reply	other threads:[~2020-11-19 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 19:29 Carsten Härle [this message]
2020-11-20  4:59 ` Dietmar Maurer
2020-11-20  7:18   ` Carsten Härle
2020-11-20  8:27     ` Dominik Csapak
2020-11-20  8:29       ` 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=57EF5F8B433A6742AD548ABECE78FE48539302@hal9001.straightec.lokal \
    --to=carsten.haerle@straightec.de \
    --cc=pve-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