From: nada <nada@verdnatura.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Excluding individual vdisks from PVE backups?
Date: Mon, 08 Nov 2021 13:33:14 +0100 [thread overview]
Message-ID: <2bdf9f309bb88dfba0012b1bbae5386d@verdnatura.es> (raw)
In-Reply-To: <cd3ed25a-0013-5894-f673-71f871e94573@dkfz-heidelberg.de>
hi Frank
you can exclude CT/QM or some path see details at man
# man vzdump
example
via webGUI
cluster > backup > edit > selection > ... exclude some VM ...
via CLI
0 2 * * 6 root vzdump --exclude 104 --mode snapshot --quiet 1
--maxfiles 1 --storage backup --compress lzo --mailnotification always
--mailto admin@some.where
best regards
Nada
On 2021-11-08 13:07, Frank Thommen wrote:
> Dear all,
>
> we are doing daily backups of every VM in our PVE cluster to the
> internal Ceph storage (snapshot mode, ZSTD compression). However one
> of the VMs takes six to seven hours for the backup, which is
> unbearable and also interferes with other backup processes. The delay
> is probably due to a 50% filled 500G vdisk attached to the VM. Is
> there a way to exclude this specific vdisk from the PVE backup
> schedule, while still retaining the rest of the VM in the backup?
>
> We don't have PBS in place and will not have it in the near future for
> different reasons. So PBS would not be an option for us.
>
> Cheers, Frank
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-11-08 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 12:07 Frank Thommen
2021-11-08 12:33 ` nada [this message]
2021-11-08 13:25 ` Frank Thommen
[not found] ` <mailman.328.1636374166.15957.pve-user@lists.proxmox.com>
2021-11-08 13:22 ` Frank Thommen
2021-11-09 18:47 ` Frank Thommen
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=2bdf9f309bb88dfba0012b1bbae5386d@verdnatura.es \
--to=nada@verdnatura.es \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.