yes, vzdump has a default exclude list (as described in "man vzdump").
Backup in LXC with Proxmox 4.1
- Thread starter charlesm1888
- Start date
-
- Tags
- backup fails lxc
yes, vzdump has a default exclude list (as described in "man vzdump").
WTF Proxmox never used to do that, this has caused me alot of problems a warning would have been nice ... Its ok now that i found out a bit late and potentially catastrophic.
I am sure Proxmox has included this seriously not cool default setting for a reason? but as far as i am concerned incomplete backups are broken backups. Also when i did my latest enterprise repo update Proxmox wanted remove the stdexcludes: 0 line from my /etc/vzdump.conf not nice
I am sure Proxmox has included this seriously not cool default setting for a reason? but as far as i am concerned incomplete backups are broken backups. Also when i did my latest enterprise repo update Proxmox wanted remove the stdexcludes: 0 line from my /etc/vzdump.conf not nice
Ok sorry i did not realize that, could have sworn that my OpenVZ containers always got backed up correctly with all files as default. Also would like to apologize for my last post after a reread i realize i was quite frustrated and did not mean to come across quite so angry Sorry
It seems that a lot of users are confused/surprised by this option - there is a tracking bug for changing or removing the stdexcludes option at https://bugzilla.proxmox.com/show_bug.cgi?id=1005
Hi,
A quick and simple question: after applying the latest updates to pve-manager, do we still need to modify /etc/vzdump.conf with "stdexcludes: 0"? Or not?
Thanks.
EDIT: Ok, nevermind. I just tried creating a backup, and I can confirm that:
- Applying all updates as of today to pve-manager, brought me to version 4.2-17.
- No changes to /etc/vzdump.conf
- An lxc backup in mode "stop" created a backup with the folder /var/log/ with all content.
So all is well, at least for me!
Thanks!
A quick and simple question: after applying the latest updates to pve-manager, do we still need to modify /etc/vzdump.conf with "stdexcludes: 0"? Or not?
Thanks.
EDIT: Ok, nevermind. I just tried creating a backup, and I can confirm that:
- Applying all updates as of today to pve-manager, brought me to version 4.2-17.
- No changes to /etc/vzdump.conf
- An lxc backup in mode "stop" created a backup with the folder /var/log/ with all content.
So all is well, at least for me!
Thanks!
Last edited: