Proxmox 2.3 new install with backup problems

raj

Renowned Member
Sep 17, 2011
221
4
83
www.businessparksolutions.com
Hi Team,

I have a cluster of 3 nodes all on 2.3

I noticed that after the backup, I get issues with the exchange server running on a win 2003 64, from the gui it says running but when i console to it, its powered off.

I just noticed that this morning another server was powered off, a win2003 dc and had to power it on.

This problem started after i moved to 2.3, a scratch install.

Backup type is snapshot and gzip.

backup goes to a nfs share.

Box is running.raw and running from an iscsi lun.

This morning when the exchange server booted up, checkdisk started and found a few errors that it corrected.

Am I missing anything.
Pls advise.

Cheers,

Raj
 
Hi guys I updated the system this morning by running an apt-get update and the and

apt-get dist-upgrade

then this afternoon ran a backup and again that exchange box was off when I just checked.

Cloud this be a bug pls advise.

Cheers,

Raj
 
This is from /var/log/vzdump

Mar 20 13:28:10 INFO: Starting Backup of VM 101 (qemu)
Mar 20 13:28:10 INFO: status = running
Mar 20 13:28:11 INFO: backup mode: snapshot
Mar 20 13:28:11 INFO: ionice priority: 7
Mar 20 13:28:11 INFO: creating archive '/mnt/pve/Backup/dump/vzdump-qemu-101-2013_03_20-13_28_10.vma.lzo'
Mar 20 13:28:11 INFO: started backup task '9b1b678c-f671-4138-91f3-f4975bc49262'
Mar 20 13:28:14 INFO: status: 0% (72876032/42949672960), sparse 0% (2121728), duration 3, 24/23 MB/s
Mar 20 13:28:30 INFO: status: 1% (441450496/42949672960), sparse 0% (5111808), duration 19, 23/22 MB/s
Mar 20 13:29:36 INFO: status: 2% (876085248/42949672960), sparse 0% (7680000), duration 85, 6/6 MB/s
Mar 20 13:29:55 INFO: status: 3% (1309409280/42949672960), sparse 0% (17428480), duration 104, 22/22 MB/s
Mar 20 13:31:11 INFO: status: 4% (1734344704/42949672960), sparse 0% (17801216), duration 180, 5/5 MB/s
Mar 20 13:31:34 INFO: status: 5% (2153906176/42949672960), sparse 0% (18108416), duration 203, 18/18 MB/s
Mar 20 13:32:34 INFO: status: 6% (2585591808/42949672960), sparse 0% (18800640), duration 263, 7/7 MB/s
Mar 20 13:32:54 ERROR: VM 101 not running
Mar 20 13:32:54 INFO: aborting backup job
Mar 20 13:32:54 ERROR: VM 101 not running
Mar 20 13:32:54 ERROR: Backup of VM 101 failed - VM 101 not running

That server was running as its been throwing mail all morning.

Here is also a pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
root@master:~#


Cheers,

Raj
 
Ok just checked it again and it is a BSOD.

This started from when I installed the new version of 2.3.

In order to debug that, we need a way to reproduce the bug here. Can you reproduce the bug by creating a new VM, or does it only happen with this special VM?