vzdump problem

H

hec

Renowned Member
Jan 8, 2009
278
18
83
Wien
www.vector-its.at
I setup a new Proxmox server. Now i tried to do a vzdump but i got following error:

Code: 
[FONT=monospace]zdump --quiet --node 1 --snapshot --compress --storage Backup --maxfiles 1 --mailto server@hec-tech.net 105[/FONT]
105: Oct 18 16:03:01 INFO: Starting Backup of VM 105 (openvz)105: Oct 18 16:03:01 INFO: CTID 105 exist mounted running105: Oct 18 16:03:01 INFO: status = CTID 105 exist mounted running105: Oct 18 16:03:01 INFO: mode failure - unable to dump into snapshot (use option --dumpdir)105: Oct 18 16:03:01 INFO: trying 'suspend' mode instead105: Oct 18 16:03:01 INFO: backup mode: suspend105: Oct 18 16:03:01 INFO: ionice priority: 7105: Oct 18 16:03:01 INFO: starting first sync /var/lib/vz/private/105/ to /var/lib/vz/backup/vzdump-openvz-105-2011_10_18-16_03_01.tmp105: Oct 18 16:03:09 INFO: Number of files: 31256105: Oct 18 16:03:09 INFO: Number of files transferred: 24406105: Oct 18 16:03:09 INFO: Total file size: 803153774 bytes105: Oct 18 16:03:09 INFO: Total transferred file size: 799404806 bytes105: Oct 18 16:03:09 INFO: Literal data: 799404806 bytes105: Oct 18 16:03:09 INFO: Matched data: 0 bytes105: Oct 18 16:03:09 INFO: File list size: 754411105: Oct 18 16:03:09 INFO: File list generation time: 0.001 seconds105: Oct 18 16:03:09 INFO: File list transfer time: 0.000 seconds105: Oct 18 16:03:09 INFO: Total bytes sent: 801327507105: Oct 18 16:03:09 INFO: Total bytes received: 502509105: Oct 18 16:03:09 INFO: sent 801327507 bytes  received 502509 bytes  94332943.06 bytes/sec105: Oct 18 16:03:09 INFO: total size is 803153774  speedup is 1.00105: Oct 18 16:03:09 INFO: first sync finished (8 seconds)105: Oct 18 16:03:09 INFO: suspend vm105: Oct 18 16:03:09 INFO: Setting up checkpoint...105: Oct 18 16:03:09 INFO: 	suspend...105: Oct 18 16:03:09 INFO: Can not suspend container: Device or resource busy105: Oct 18 16:03:09 INFO: Error: task 105092/354(ntpd) uses posix timers105: Oct 18 16:03:09 INFO: Checkpointing failed [FONT=monospace]105: [COLOR=#ff0000]Oct 18 16:03:11 ERROR: Backup of VM 105 failed - command 'vzctl --skiplock chkpnt 105 --suspend' failed with exit code 16[/COLOR][/FONT]

Code: 
pve-manager: 1.9-24 (pve-manager/1.9/6542)running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

Code: 
/dev/mapper/pve-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz1 type ext3 (rw)
/dev/mapper/data-openvz on /var/lib/vz type ext4 (rw)
/dev/cciss/c0d0p1 on /boot type ext3 (rw)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
10.6.88.10:/backup/hecvz on /mnt/pve/Backup_Cop type nfs (rw,addr=10.6.88.10)

Code: 
pmx-00:~# pvdisplay 
  --- Physical volume ---
  PV Name               /dev/block/104:16
  VG Name               data
  PV Size               1.82 TB / not usable 3.21 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              476918
  Free PE               67318
  Allocated PE          409600
  PV UUID               z5c7Ai-amd6-mO3Z-lNBA-lE3m-2QQF-s6sxx0
   
  --- Physical volume ---
  PV Name               /dev/block/104:2
  VG Name               pve
  PV Size               67.83 GB / not usable 2.57 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              17364
  Free PE               1023
  Allocated PE          16341
  PV UUID               qdX4f8-UIOl-bvqs-EBvj-ALVy-a6oa-EoRoxz

Code: 
pmx-00:~# pvdisplay 
  --- Physical volume ---
  PV Name               /dev/block/104:16
  VG Name               data
  PV Size               1.82 TB / not usable 3.21 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              476918
  Free PE               67318
  Allocated PE          409600
  PV UUID               z5c7Ai-amd6-mO3Z-lNBA-lE3m-2QQF-s6sxx0
   
  --- Physical volume ---
  PV Name               /dev/block/104:2
  VG Name               pve
  PV Size               67.83 GB / not usable 2.57 MB
  Allocatable           yes 
  PE Size (KByte)       4096
  Total PE              17364
  Free PE               1023
  Allocated PE          16341
  PV UUID               qdX4f8-UIOl-bvqs-EBvj-ALVy-a6oa-EoRoxz
   
pmx-00:~# 
pmx-00:~# 
pmx-00:~# 
pmx-00:~# lvdisplay 
  --- Logical volume ---
  LV Name                /dev/data/openvz
  VG Name                data
  LV UUID                EqXn8A-hLWh-KHxV-mzZn-ffGT-pNs0-teMv3x
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.56 TB
  Current LE             409600
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3
   
  --- Logical volume ---
  LV Name                /dev/pve/swap
  VG Name                pve
  LV UUID                ySjd83-z4bf-Jd3g-ceNj-DSJ6-lhEs-PFPNyp
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                8.50 GB
  Current LE             2176
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
   
  --- Logical volume ---
  LV Name                /dev/pve/root
  VG Name                pve
  LV UUID                xZ3wod-Ehot-j35K-NpKf-AmVh-lzr0-DkLajC
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                17.00 GB
  Current LE             4352
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1
   
  --- Logical volume ---
  LV Name                /dev/pve/data
  VG Name                pve
  LV UUID                qO0b08-2yxT-1dxG-sFtf-sWmJ-Qia1-RQ6n84
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                38.33 GB
  Current LE             9813
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

Any ideas how to solve this problem? The functions of snapshot is a must!
 
"unable to dump into snapshot"

I assume your backup target is under /var/lib/vz ?
 
for small test just create a dir on the / filesystem - but make sure you have enough space and you do not fill it up with backups.
 
yes, you cannot save the snapshot data into same volume - by doing this you create a loop with no end ..

but anyways, it makes no sense to store backup on the same server, use NFS share or similar to store your backups remotely.
 
You must log in or register to reply here.
Top Bottom