Lost directories after LXC vzdump backup/restore

M

Michael 2

New Member
May 13, 2014
4
0
1
I am experiencing a strange problem on a newly install Proxmox 4.1:

  • Created fresh LXC containers from the Debian 8 Template
  • Installed software such as Nginx via Debian
  • Create a backup of these containers via Proxmox backup function
  • Restored the backup
  • /var/log/nginx (and all other directories below /var/log) is missing, service can not start
  • Apparently all other files are in place after restore

This happens reproducible if I restore the directories and do another backup/restore cycle.


Code: 
# pveversion  -v
proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
 
I just did some more research and found at that vzdump excludes /var/log/ by default.

Apparently the directories should be recreated automatically by the logger, which is not happening in my containers. Will look into it further, but apparently not a problem of vzdump. Either a problem of the Debian 8 template or my specific setup.
 
Note that disabling the stdexcludes via vzdump.conf was broken in pve-manager <= 4.1-22 (Bug#926) - disabling them via the CLI ("vzdump .... -stdexcludes 0") works on every version.
 
You must log in or register to reply here.
Top Bottom