public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "sebastian@debianfan.de" <sebastian@debianfan.de>
To: Lukas Wagner <l.wagner@proxmox.com>,
	Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Backup of all Containers and KVM
Date: Fri, 29 Sep 2023 13:43:52 +0200	[thread overview]
Message-ID: <73da3963-ac2f-36ca-6bfd-22a3a5b6723c@debianfan.de> (raw)
In-Reply-To: <54aa55a8-98f9-459d-b2fa-48ec790fd443@proxmox.com>

Thx - i know how to use the vzdump-tool - but the last backup of an 
lxc-container (500 GB) runs about 10 hours by using vzdump :-(



Am 29.09.2023 um 10:24 schrieb Lukas Wagner:
> 
> 
> On 9/29/23 09:53, sebastian@debianfan.de wrote:
>> Hi,
>>
>> if i want to get a full backup - can i copy the 100,101... folders 
>> complete to the backup server to get the data for  an emergency 
>> restore later?
>>
>> Or is it required to use the internal backup function to get Backup 
>> files from containers and KVM and copy the dump-directory to the 
>> backup server?
>>
> 
> I'd recommend using PVE's backup function, it includes everything needed
> to fully restore the VM/CT. If you need to automate that from a script,
> you can use the `vzdump` command (check `man vzdump` or [1] for
> instructions).
> You can then copy the backup files from the dump directory. You could
> also add the backup server as a storage (NFS or SMB) [2], then you can
> backup to the server directly, without having to copy the backup
> archives.
> 
> The '100, 101' folders - by which I think you mean the directories in
> /etc/pve/{qemu,lxc} only contain the configuration files for the VM/CT,
> but not the disk image. Of course, you can back them up manually and
> then dump the disk image as well, but like I said, unless you have a
> very good reason against PVE's native backup system (vzdump), I'd
> recommend using that.
> 
> It might also be worth checking out Proxmox Backup Server, which has the 
> additional benefit of offering deduplication, encryption, live-restore 
> and much more.
> 
> [1] https://pve.proxmox.com/pve-docs/vzdump.1.html
> [2] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_storage
> 



  reply	other threads:[~2023-09-29 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  7:53 sebastian
2023-09-29  8:24 ` Lukas Wagner
2023-09-29 11:43   ` sebastian [this message]
2023-09-29 11:50     ` Lukas Wagner
2023-09-29 11:50     ` Gilberto Ferreira
     [not found] ` <mailman.298.1695976073.312.pve-user@lists.proxmox.com>
2023-09-29 11:30   ` Gilberto Ferreira

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=73da3963-ac2f-36ca-6bfd-22a3a5b6723c@debianfan.de \
    --to=sebastian@debianfan.de \
    --cc=l.wagner@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal