Online VM backups using vzdump using --snapshot? Not working - VM goes down

lonegroover · Feb 11, 2012

Hi,

I'm using Proxmox VE 1.8.

What I want to do is organise regular VM image backups using vzdump, without taking down the VM to be backed up. The VM disk images are maintained as LVMs in shared storage, so for example in the following case the root disk is drbdvg1:vm-102-disk-1

So I tried:

Code:

vzdump --snapshot --stdexcludes --dumpdir /var/lib/vz/dump_test 102

This completed successfully, and creates a tar file and a log file in the specified directory. My understanding was that the --snapshot option would allow the VM to continue running while the backup takes place.

Unfortunately, within seconds of starting vzdump, the Proxmox showed the VM in question as stopped, and I had to restart it manually after vzdump completed.

What am I doing wrong? Is there a way to get it to continue running undisturbed while a backup is taken?

Thanks for any advice.

e100 · Feb 11, 2012

Can you post the logs from the backup? They likely contain clues as to why this happened.

lonegroover · Feb 12, 2012

Thanks for the reply. This is /var/log/vzdump/qemu-102.log:

Code:

Feb 11 10:47:01 INFO: Starting Backup of VM 102 (qemu)
Feb 11 10:47:02 INFO: running
Feb 11 10:47:02 INFO: status = running
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Finding all volume groups
Feb 11 10:47:02 INFO:     Finding volume group "pve"
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg0"
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Using volume group(s) on command line
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg1"
Feb 11 10:47:02 INFO:     12 logical volume(s) in volume group "drbdvg1" already active
Feb 11 10:47:02 INFO:     12 existing logical volume(s) in volume group "drbdvg1" monitored
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Activated logical volumes in volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Finding all logical volumes
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO: backup mode: snapshot
Feb 11 10:47:02 INFO: ionice priority: 7
Feb 11 10:47:02 INFO: suspend vm to make snapshot
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Finding all volume groups
Feb 11 10:47:02 INFO:     Finding volume group "pve"
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg0"
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Using volume group(s) on command line
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg1"
Feb 11 10:47:02 INFO:     12 logical volume(s) in volume group "drbdvg1" already active
Feb 11 10:47:02 INFO:     12 existing logical volume(s) in volume group "drbdvg1" monitored
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Activated logical volumes in volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Finding all logical volumes
Feb 11 10:47:02 INFO:     Wiping internal VG cache
Feb 11 10:47:02 INFO:     Logging initialised at Sat Feb 11 10:47:02 2012
Feb 11 10:47:02 INFO:     Set umask to 0077
Feb 11 10:47:02 INFO:     Setting chunksize to 8 sectors.
Feb 11 10:47:02 INFO:     Setting logging type to disk
Feb 11 10:47:02 INFO:     Finding volume group "drbdvg1"
Feb 11 10:47:02 INFO:     Archiving volume group "drbdvg1" metadata (seqno 47).
Feb 11 10:47:02 INFO:     Creating logical volume vzsnap-pves1-0
Feb 11 10:47:02 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 48).
Feb 11 10:47:03 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:03 INFO:     Creating drbdvg1-vzsnap--pves1--0
Feb 11 10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--0 table
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--0 (254:28)
Feb 11 10:47:03 INFO:     Clearing start of logical volume "vzsnap-pves1-0"
Feb 11 10:47:03 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:03 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:03 INFO:     Creating drbdvg1-vm--102--disk--1-real
Feb 11 10:47:03 INFO:     Loading drbdvg1-vm--102--disk--1-real table
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--1-real (254:29)
Feb 11 10:47:03 INFO:     Loading drbdvg1-vm--102--disk--1 table
Feb 11 10:47:03 INFO:     Creating drbdvg1-vzsnap--pves1--0-cow
Feb 11 10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--0-cow table
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--0-cow (254:30)
Feb 11 10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--0 table
Feb 11 10:47:03 INFO:     Suspending drbdvg1-vm--102--disk--1 (254:3) with filesystem sync with device flush
Feb 11 10:47:03 INFO:     Suspending drbdvg1-vm--102--disk--1-real (254:29) with filesystem sync with device flush
Feb 11 10:47:03 INFO:     Found volume group "drbdvg1"
Feb 11 10:47:03 INFO:     Loading drbdvg1-vm--102--disk--1-real table
Feb 11 10:47:03 INFO:     Suppressed drbdvg1-vm--102--disk--1-real identical table reload.
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--1-real (254:29)
Feb 11 10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--0-cow table
Feb 11 10:47:03 INFO:     Suppressed drbdvg1-vzsnap--pves1--0-cow identical table reload.
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--0 (254:28)
Feb 11 10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--1 (254:3)
Feb 11 10:47:03 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 49).
Feb 11 10:47:03 INFO:     Wiping internal VG cache

lonegroover · Feb 12, 2012

(continued .. have snipped off the date to get the size of the text down)

Code:

10:47:03 INFO:   Logical volume "vzsnap-pves1-0" created
10:47:03 INFO:     Logging initialised at Sat Feb 11 10:47:03 2012
10:47:03 INFO:     Set umask to 0077
10:47:03 INFO:     Setting chunksize to 8 sectors.
10:47:03 INFO:     Setting logging type to disk
10:47:03 INFO:     Finding volume group "drbdvg1"
10:47:03 INFO:     Archiving volume group "drbdvg1" metadata (seqno 49).
10:47:03 INFO:     Creating logical volume vzsnap-pves1-1
10:47:03 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 50).
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Creating drbdvg1-vzsnap--pves1--1
10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--1 table
10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--1 (254:31)
10:47:03 INFO:     Clearing start of logical volume "vzsnap-pves1-1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Creating drbdvg1-vm--102--disk--2-real
10:47:03 INFO:     Loading drbdvg1-vm--102--disk--2-real table
10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--2-real (254:32)
10:47:03 INFO:     Loading drbdvg1-vm--102--disk--2 table
10:47:03 INFO:     Creating drbdvg1-vzsnap--pves1--1-cow
10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--1-cow table
10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--1-cow (254:33)
10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--1 table
10:47:03 INFO:     Suspending drbdvg1-vm--102--disk--2 (254:27) with filesystem sync with device flush
10:47:03 INFO:     Suspending drbdvg1-vm--102--disk--2-real (254:32) with filesystem sync with device flush
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Loading drbdvg1-vm--102--disk--2-real table
10:47:03 INFO:     Suppressed drbdvg1-vm--102--disk--2-real identical table reload.
10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--2-real (254:32)
10:47:03 INFO:     Loading drbdvg1-vzsnap--pves1--1-cow table
10:47:03 INFO:     Suppressed drbdvg1-vzsnap--pves1--1-cow identical table reload.
10:47:03 INFO:     Resuming drbdvg1-vzsnap--pves1--1 (254:31)
10:47:03 INFO:     Resuming drbdvg1-vm--102--disk--2 (254:27)
10:47:03 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 51).
10:47:03 INFO:     Wiping internal VG cache
10:47:03 INFO:   Logical volume "vzsnap-pves1-1" created
10:47:03 INFO: resume vm
10:47:03 INFO:     Logging initialised at Sat Feb 11 10:47:03 2012
10:47:03 INFO:     Set umask to 0077
10:47:03 INFO:     Finding all volume groups
10:47:03 INFO:     Finding volume group "pve"
10:47:03 INFO:     Finding volume group "drbdvg1"
10:47:03 INFO:     Finding volume group "drbdvg0"
10:47:03 INFO:     Wiping internal VG cache
10:47:03 INFO:     Logging initialised at Sat Feb 11 10:47:03 2012
10:47:03 INFO:     Set umask to 0077
10:47:03 INFO:     Using volume group(s) on command line
10:47:03 INFO:     Finding volume group "drbdvg1"
10:47:03 INFO:     12 logical volume(s) in volume group "drbdvg1" already active
10:47:03 INFO:     14 existing logical volume(s) in volume group "drbdvg1" monitored
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Found volume group "drbdvg1"
10:47:03 INFO:     Activated logical volumes in volume group "drbdvg1"
10:47:03 INFO:     Wiping internal VG cache
10:47:03 INFO:     Logging initialised at Sat Feb 11 10:47:03 2012
10:47:03 INFO:     Set umask to 0077
10:47:03 INFO:     Finding all logical volumes
10:47:03 INFO:     Wiping internal VG cache
10:47:03 INFO: vm is online again after 1 seconds
10:47:03 INFO: creating archive '/var/lib/vz/alpha.dump.running/vzdump-qemu-102-2012_02_11-10_47_01.tar'
10:47:03 INFO: adding '/var/lib/vz/alpha.dump.running/vzdump-qemu-102-2012_02_11-10_47_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
10:47:03 INFO: adding '/dev/drbdvg1/vzsnap-pves1-0' to archive ('vm-disk-ide0.raw')
10:56:05 INFO: adding '/dev/drbdvg1/vzsnap-pves1-1' to archive ('vm-disk-ide1.raw')
11:01:35 INFO: Total bytes written: 13050525696 (14.27 MiB/s)
11:01:35 INFO: archive file size: 12.15GB
11:01:36 INFO:     Logging initialised at Sat Feb 11 11:01:36 2012
11:01:36 INFO:     Set umask to 0077
11:01:36 INFO:     Finding all volume groups
11:01:36 INFO:     Finding volume group "pve"
11:01:36 INFO:     Finding volume group "drbdvg1"
11:01:36 INFO:     Finding volume group "drbdvg0"
11:01:36 INFO:     Wiping internal VG cache
11:01:36 INFO:     Logging initialised at Sat Feb 11 11:01:36 2012
11:01:36 INFO:     Set umask to 0077
11:01:36 INFO:     Using volume group(s) on command line
11:01:36 INFO:     Finding volume group "drbdvg1"
11:01:36 INFO:     12 logical volume(s) in volume group "drbdvg1" already active
11:01:36 INFO:     14 existing logical volume(s) in volume group "drbdvg1" monitored
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Activated logical volumes in volume group "drbdvg1"
11:01:36 INFO:     Wiping internal VG cache
11:01:36 INFO:     Logging initialised at Sat Feb 11 11:01:36 2012
11:01:36 INFO:     Set umask to 0077
11:01:36 INFO:     Finding all logical volumes
11:01:36 INFO:     Wiping internal VG cache
11:01:36 INFO:     Logging initialised at Sat Feb 11 11:01:36 2012
11:01:36 INFO:     Set umask to 0077
11:01:36 INFO:     Using logical volume(s) on command line
11:01:36 INFO:     Archiving volume group "drbdvg1" metadata (seqno 51).
11:01:36 INFO:     Found volume group "drbdvg1"
11:01:36 INFO:     Removing drbdvg1-vzsnap--pves1--0 (254:28)
11:01:36 INFO:     Removing drbdvg1-vzsnap--pves1--0-cow (254:30)
11:01:37 INFO:     Found volume group "drbdvg1"
11:01:37 INFO:     Removing snapshot vzsnap-pves1-0
11:01:37 INFO:     Releasing logical volume "vzsnap-pves1-0"
11:01:37 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 52).
11:01:37 INFO:     Found volume group "drbdvg1"
11:01:37 INFO:     Found volume group "drbdvg1"
11:01:37 INFO:     Suspending drbdvg1-vm--102--disk--1 (254:3) with device flush
11:01:37 INFO:     Suspending drbdvg1-vm--102--disk--1-real (254:29) with device flush
11:01:37 INFO:     Found volume group "drbdvg1"
11:01:37 INFO:     Resuming drbdvg1-vm--102--disk--1-real (254:29)
11:01:37 INFO:     Loading drbdvg1-vm--102--disk--1 table
11:01:37 INFO:     Resuming drbdvg1-vm--102--disk--1 (254:3)
11:01:37 INFO:     Removing drbdvg1-vm--102--disk--1-real (254:29)
11:01:37 INFO:     Wiping internal VG cache
11:01:37 INFO:   Logical volume "vzsnap-pves1-0" successfully removed
11:01:37 INFO:     Logging initialised at Sat Feb 11 11:01:37 2012
11:01:37 INFO:     Set umask to 0077
11:01:37 INFO:     Using logical volume(s) on command line
11:01:37 INFO:     Archiving volume group "drbdvg1" metadata (seqno 52).
11:01:37 INFO:     Found volume group "drbdvg1"
11:01:37 INFO:     Removing drbdvg1-vzsnap--pves1--1 (254:31)
11:01:37 INFO:     Removing drbdvg1-vzsnap--pves1--1-cow (254:33)
11:01:38 INFO:     Found volume group "drbdvg1"
11:01:38 INFO:     Removing snapshot vzsnap-pves1-1
11:01:38 INFO:     Releasing logical volume "vzsnap-pves1-1"
11:01:38 INFO:     Creating volume group backup "/etc/lvm/backup/drbdvg1" (seqno 53).
11:01:38 INFO:     Found volume group "drbdvg1"
11:01:38 INFO:     Found volume group "drbdvg1"
11:01:38 INFO:     Suspending drbdvg1-vm--102--disk--2 (254:27) with device flush
11:01:38 INFO:     Suspending drbdvg1-vm--102--disk--2-real (254:32) with device flush
11:01:38 INFO:     Found volume group "drbdvg1"
11:01:38 INFO:     Resuming drbdvg1-vm--102--disk--2-real (254:32)
11:01:38 INFO:     Loading drbdvg1-vm--102--disk--2 table
11:01:38 INFO:     Resuming drbdvg1-vm--102--disk--2 (254:27)
11:01:38 INFO:     Removing drbdvg1-vm--102--disk--2-real (254:32)
11:01:38 INFO:   device-mapper: remove ioctl failed: Device or resource busy
11:01:38 INFO:   Unable to deactivate drbdvg1-vm--102--disk--2-real (254:32)
11:01:38 INFO:     Wiping internal VG cache
11:01:38 INFO:   Logical volume "vzsnap-pves1-1" successfully removed
11:01:38 INFO: Finished Backup of VM 102 (00:14:37)

dietmar · Feb 13, 2012

And after that the VM is stopped? If so, is there any hint in /var/log/syslog?

lonegroover · Feb 13, 2012

dietmar said:
And after that the VM is stopped? If so, is there any hint in /var/log/syslog?

The VM stops within a few seconds of starting vzdump.

This is a snippet from the VM's /var/log/messages:

Code:

Feb 11 10:32:31 alpha smartd[2862]: Device: /dev/hdc, opened
Feb 11 10:32:31 alpha kernel: hdc: drive_cmd: status=0x41 { DriveReady Error }
Feb 11 10:32:31 alpha smartd[2862]: Device: /dev/hdc, not ATA, no IDENTIFY DEVICE Structure
Feb 11 10:32:31 alpha kernel: hdc: drive_cmd: error=0x04 { AbortedCommand }
Feb 11 10:32:31 alpha smartd[2862]: Monitoring 2 ATA and 0 SCSI devices
Feb 11 10:32:31 alpha kernel: ide: failed opcode was: 0xec
Feb 11 10:32:31 alpha smartd[2869]: smartd has fork()ed into background mode. New PID=2869.
Feb 11 11:04:48 alpha syslogd 1.4.1: restart.
Feb 11 11:04:48 alpha kernel: klogd 1.4.1, log source = /proc/kmsg started.
Feb 11 11:04:48 alpha kernel: Linux version 2.6.18-238.12.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Tue May 31 13:22:04 EDT 2011
Feb 11 11:04:48 alpha kernel: Command line: ro root=/dev/VolGroup00/LogVol00

And on the physical node:

Code:

Feb 11 06:30:03 pves1 nagios3: Auto-save of retention data completed successfully.
Feb 11 07:30:03 pves1 nagios3: Auto-save of retention data completed successfully.
Feb 11 08:30:03 pves1 nagios3: Auto-save of retention data completed successfully.
Feb 11 09:30:03 pves1 nagios3: Auto-save of retention data completed successfully.
Feb 11 10:13:24 pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state
Feb 11 10:13:24 pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state
Feb 11 10:30:03 pves1 nagios3: Auto-save of retention data completed successfully.
Feb 11 10:30:47 pves1 kernel: device tap102i0d0 entered promiscuous mode
Feb 11 10:30:47 pves1 kernel: vmbr0: port 4(tap102i0d0) entering forwarding state
Feb 11 10:47:04 pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state
Feb 11 10:47:04 pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state
Feb 11 11:01:38 pves1 kernel: device-mapper: ioctl: unable to remove open device drbdvg1-vm--102--disk--2-real
Feb 11 11:03:47 pves1 kernel: device tap102i0d0 entered promiscuous mode
Feb 11 11:03:47 pves1 kernel: vmbr0: port 4(tap102i0d0) entering forwarding state
Feb 11 11:30:03 pves1 nagios3: Auto-save of retention data completed successfully.

.. I ran vzdump at 10:47.

e100 · Feb 14, 2012

When vzdump starts it pauses the VM, creates the snapshots, then resumes the VM.
The first set of logs you posted shows that it did all of these things, I also see no signs of anything going wrong in those logs.

The last set of logs you posted are interesting:

Code:

[B]10:47:04 [/B]pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state Feb 11 10:47:04 pves1 kernel: vmbr0: port 4(tap102i0d0) entering disabled state

So it seems like the VM is crashing when it is resumed:

Code:

[B]10:47:02[/B] INFO: suspend vm to make snapshot
10:47:03 INFO: resume vm
[B]10:47:03 [/B]INFO: vm is online again after 1 seconds

Not sure why it is crashing.....
Do you have the latest updates for Proxmox?

lonegroover · Feb 14, 2012

Thanks for taking a look. I doubt that we have the latest updates. Is it as simple as an apt-get update and apt-get upgrade? If it's likely to necessitate a reboot I'll have to hold off for a while unfortunately.

A supplementary question - until I can get this working, is it worth trying something like:

Code:

dd if=/dev/mapper/drbdvg1-vm--114--disk--1 | (cd $BACKUPDIR; dd of=vm-114.img)

.. at a quiet time?

e100 · Feb 15, 2012

That dd backup would only work well if the VM was stopped first.

Recommend way to upgrade:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.9

It is possible that the problem you are having is fixed already and you just need to upgrade.
If you are far behind you might get a new kernel and that would require an update.

Search

Search

Online VM backups using vzdump using --snapshot? Not working - VM goes down

lonegroover

Guest

e100

Famous Member

lonegroover

Guest

lonegroover

Guest

dietmar

Proxmox Staff Member

lonegroover

Guest

e100

Famous Member

lonegroover

Guest

e100

Famous Member

We value your privacy