Backup with vzdump omits /var/log

[KillianS]

Hello,

I've found that backup feature omits my /var/log folder.
But it's not mentionned anywhere, and i can't figure how to avoid this behavior.

Backup log is:

INFO: starting new backup job: vzdump 123 --remove 0 --storage dump-storage --mode snapshot --compress lzo --node main

Like you can see, no --stdexcludes option.

I'm running Proxmox Virtual Environment 4.2-2/725d76f0.

Any help would be appreciated
Thanks for reading

 

[tom]

check documentation. and it seems you run an old version?

please update to latest and try again.

 

[KillianS]

Sorry, i've forgot to mention version : Proxmox Virtual Environment 4.2-2/725d76f0

And i have checked documentation, both https://pve.proxmox.com/wiki/Manual:_vzdump and https://pve.proxmox.com/wiki/VZDump are pointless here.

---
After some forum search i've found this 2008 topic https://forum.proxmox.com/threads/vzdump-omits-var-log.655/ but it doesn't help neither

 

[tom]

Sorry, i've forgot to mention version : Proxmox Virtual Environment 4.2-2/725d76f0

Very old. Please upgrade and test again.

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2

 

[KillianS]

Finally i found solution, just put

stdexcludes: 0

in /etc/vzdump.conf

This stdexcludes option should be set off by default. Or at least should be explicited in command line log displayed by the manager during backup.

Useful information about vzdump config missing from https://pve.proxmox.com/wiki/VZDump can be found in https://pve.proxmox.com/wiki/Backup_and_Restore

 

[tom]

Instead of hunting the old and already fixed bugs, please use latest version. The solution is using latest version here.

The wiki article already got the link to the new reference docs and yes, the wiki needs a bit more cleanup (ins work in progress).

 

[KillianS]

I use the latest version i've found here https://www.proxmox.com/en/downloads

 

[shantanu]

@KillianS , I think @tom means you will need to "upgrade" your packages.

@tom , besides editing the config file directly, is there a command-line method to edit the config file?
(Something like the "qm set" equivalent).

Thanks and Regards,
Shantanu

 

[tom]

I use the latest version i've found here https://www.proxmox.com/en/downloads

Please follow the howto:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2

 

[Datenfalke]

I have a freshly installed 4.2 and get the same problem when creating a backup for an LXC container. After restore vital folders are missing in /var/log/ resulting in offline services like apache or mysql.

After putting "stdexcludes: 0" into "/etc/vzdump.conf" the problem is solved.

I think the backup process should not be allowed to change the data which is being backuped. You should be able to be sure that you get everything back as it was while creating the backup.

 

[tom]

I have a freshly installed 4.2 ...

That is the reason why I tell all again that you should upgrade your system to latest version - a fresh ISO install never have latest packages.

Please read again the thread and PLEASE, upgrade your 4.2 to latest before you post again.
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2

the bug report to this is here:
https://bugzilla.proxmox.com/show_bug.cgi?id=1005

latest changelog:
http://download.proxmox.com/debian/...ion/binary-amd64/pve-manager_4.2-18.changelog

 

[Datenfalke]

Perhaps need to reboot to get new packages working...

Update: After reboot the package versions stay lower than it is shown in the howto.
Perhaps because of a missing subscription and missing enterprise repo?

# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

However, using "stdexcludes: 0" in "/etc/vzdump.conf" solves the problem for non subscription users.

 

[fabian]

Perhaps need to reboot to get new packages working...

Update: After reboot the package versions stay lower than it is shown in the howto.
Perhaps because of a missing subscription and missing enterprise repo?

However, using "stdexcludes: 0" in "/etc/vzdump.conf" solves the problem for non subscription users.

that has nothing to do with no-subscription vs enterprise users, but with not following instructions. please read http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2 and the referenced http://pve.proxmox.com/wiki/Package_Repositories carefully, then you will be able to install updates and not be bothered with bugs that have been fixed for a long time.

 

[Datenfalke]

Here is what your link wants me to do:

• Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI:
  -> dont have a subscription key, you say I do not need it
  
  
• Check your sources.list file, should look like this:
  -> looks the same except I am using ftp.de.debian
  
  
• The enterprise repository:
  -> You said I do not need it
  
  
• Update your repository and packages:
  -> done
  
  
• Now upgrade the packages:
  -> done
  
  
• Reboot to activate the new Kernel:
  -> done
  
  
• run 'pveversion -v' and compare your output:
  -> done, not the same or bigger versions

# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

What have I missed regarding http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2 ?

 

[fabian]

if you don't have a subscription key, but enable the enterprise repository like the page tells you to, you will get an error message when running "apt-get update":

If you get any errors, your sources.list (or your network) has a problem. Before you upgrade your system, you should stop all your running VM´s and LXC containers.

I specifically pointed you to the repositories wiki page, which is also linked in the update instructions:

If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see Package repositories

there you will find how to configure the pve-no-subscription repository:

Proxmox VE No-Subscription Repository
As the name suggests, you do not need a subscription key to access this repository. It can be used for testing and non-production use. Its not recommended to run on production servers, as these packages are not always heavily tested and validated.

We recommend to configure this repository in /etc/apt/sources.list.

File /etc/apt/sources.list

deb http://ftp.debian.org/debian jessie main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian jessie pve-no-subscription

# security updates
deb http://security.debian.org jessie/updates main contrib

if you correctly setup your APT sources according to these howtos, you should get no error message when running "apt-get update", and a subsequent "apt-get dist-upgrade" will upgrade your system to the current package versions.

not following the setup instructions and/or ignoring error messages are never a good idea, but especially not regarding something as crucial as keeping a system up to date...

 

[Datenfalke]

Sorry, I have read that it is not a good idea to activate the "Proxmox VE No-Subscription Repository" on production systems:

Its not recommended to run on production servers, as these packages are not always heavily tested and validated.

 

[tom]

Sorry, I have read that it is not a good idea to activate the "Proxmox VE No-Subscription Repository" on production systems:

Its not recommended to run on production servers, as these packages are not always heavily tested and validated.

either go for a subscription key or use the pve-no-subscription repo.

or course, the subscription key is the preferred way.

 

[Datenfalke]

Ok, thank you for your advice.

 

[KillianS]

Ok, thank you for your advice.

Please let me know if it solved the problem, and if the update doesn't break something else. It freaks me out

 

[Datenfalke]

I will wait with upgrade until tonight