Backup of VM to NFS fails on 2.3

dafydd

Renowned Member
Apr 24, 2010
37
6
73
Cardiff, Wales
I've never really used the backup functionality in Proxmox before, as I prefer to use rsync to copy all files to a backup machine. I still do this for Linux containers.

However after upgrading to 2.3 and after some server problems I've been backing up a Windows VM to NFS storage. (every night, keeping 2 backups).

I've already had to use one backup image because the backup process itself failed and completely messed up the Windows filesystem (but I'll leave that one for now).

Last night the backup failed part way through and the VM was stopped. This time, Windows did restart correctly. The VM has been running fine for 3 years and uses a .raw format file. I've now had to stop the automatic backup as it's less than useful.

Here's the backup log:

vzdump 103 --quiet 1 --mailto <me> --mode snapshot --compress lzo --storage arthur-backup --node ivmhost1

103: Mar 14 02:00:02 INFO: Starting Backup of VM 103 (qemu)
103: Mar 14 02:00:02 INFO: status = running
103: Mar 14 02:00:03 INFO: backup mode: snapshot
103: Mar 14 02:00:03 INFO: ionice priority: 7
103: Mar 14 02:00:03 INFO: creating archive '/mnt/pve/arthur-backup/dump/vzdump-qemu-103-2013_03_14-02_00_01.vma.lzo'
103: Mar 14 02:00:03 INFO: started backup task '9cd11bc4-85b9-411b-94a4-8242cae85e37'
103: Mar 14 02:00:06 INFO: status: 0% (157679616/21474836480), sparse 0% (806912), duration 3, 52/52 MB/s
103: Mar 14 02:00:09 INFO: status: 1% (284033024/21474836480), sparse 0% (1134592), duration 6, 42/42 MB/s
103: Mar 14 02:00:12 INFO: status: 2% (440926208/21474836480), sparse 0% (3878912), duration 9, 52/51 MB/s
103: Mar 14 02:00:16 INFO: status: 3% (663093248/21474836480), sparse 0% (5021696), duration 13, 55/55 MB/s
103: Mar 14 02:00:20 INFO: status: 4% (890503168/21474836480), sparse 0% (7729152), duration 17, 56/56 MB/s
103: Mar 14 02:00:25 INFO: status: 5% (1083703296/21474836480), sparse 0% (11583488), duration 22, 38/37 MB/s
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:19 INFO: aborting backup job
103: Mar 14 02:01:19 ERROR: VM 103 not running
103: Mar 14 02:01:20 ERROR: Backup of VM 103 failed - VM 103 not running
 
Last edited:
you run latest updates? please post the output of:

Code:
pveversion -v
 
ivmhost1:/home/dafydd# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-14-pve: 2.6.32-74
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-48
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
 
looks ok, these packages works here.

tell more about your hardware, network and storage setup.
 
The VM host hardware is a Dell R410 with RAID-1 disk. It was installed with Proxmox 1.5 (May 2010) and has been upgraded over time.

It's in a cluster with one other server (same hardware/software spec).

The backup host is a server running Debian/6.0 with large SATA disks but has been in use with no problems for a few years. Both hosts are on the same 1Gb switch.

I setup NFS v4 on the backup server using nfs-kernel-server and then exported the filesystem (it has 30GB free). The .lzo dump files are around 7.4GB and there are two files at the moment (March 13 and March 12)

/data/exports ivmhost1(rw,no_root_squash,no_subtree_check,crossmnt,fsid=0)

I note that the VM host has mounted the NFS filesystem with version 3, not sure if that makes any difference.

arthur:/data/exports on /mnt/pve/arthur-backup type nfs (rw,vers=3,addr=192.168.0.20)

I've had a look at the system logs on the backup server but there's nothing interesting logged when the backup job started or failed.
 
args: -serial /dev/ttyS0
bootdisk: ide0
cores: 1
description: Windows 2003 internal server%0A
ide0: local:103/vm-103-disk-1.raw,size=20G
ide2: local:iso/Windows_2003_Server_Enterprise(nlite).iso,media=cdrom
memory: 512
name: winternal
net0: rtl8139=46:A0:AF:9F:21:38,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
 
I had all sorts of issues with NFSv4 until I upgraded the NFS server's kernel to > 3.6. (I'm running a 3.7 kernel now). I wouldn't expect to see such issues if you're mounting ver=3, but it's worth a try.
 
I don't think it's a problem with the backup medium. Others are having issues with backups of running Windows VMs using Proxmox 2.3. I've had one instance of Windows being corrupted after a crashed backup and one where the VM stopped. So i'm not running these automated backups any more.

Is there any more information I can provide?
 
I don't think it's a problem with the backup medium. Others are having issues with backups of running Windows VMs using Proxmox 2.3. I've had one instance of Windows being corrupted after a crashed backup and one where the VM stopped. So i'm not running these automated backups any more.

Is there any more information I can provide?

Well, I do see one issue with your NFS export. You aren't supposed to use fsid=0 as that has special meaning in NFSv4 (pseudo root export), and further, that special meaning is deprecated (it's now recommended to just use NFSv3 style exports). Even if you use the deprecated semantics, you're supposed to submount exports from the fsid=0 root, not use it directly. It's retardedly complicated which I expect is why it was deprecated. Unfortunately it seems that most of the information on the web concerning NFSv4 continues to espouse this method.

http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration#Common_NFS4_misunderstandings

When you say Windows was corrupted, you mean you ran a backup on a live VM and it corrupted that VM during the backup? Or restoring the VM from backup resulted in corruption?
 
Last edited:
Well, I do see one issue with your NFS export. You aren't supposed to use fsid=0 as that has special meaning in NFSv4 (pseudo root export), and further, that special meaning is deprecated (it's now recommended to just use NFSv3 style exports). Even if you use the deprecated semantics, you're supposed to submount exports from the fsid=0 root, not use it directly. It's retardedly complicated which I expect is why it was deprecated. Unfortunately it seems that most of the information on the web concerning NFSv4 continues to espouse this method.

http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration#Common_NFS4_misunderstandings

When you say Windows was corrupted, you mean you ran a backup on a live VM and it corrupted that VM during the backup? Or restoring the VM from backup resulted in corruption?

I ran into the same issue backing up to NFS, where I backed up a live VM, and after the backup completed successfully, the VM was corrupted. I had it happen on another one where the VM lost the ability to write to its data storage (ide) until rebooted.
 
Well, I do see one issue with your NFS export. You aren't supposed to use fsid=0 as that has special meaning in NFSv4 (pseudo root export), and further, that special meaning is deprecated (it's now recommended to just use NFSv3 style exports). Even if you use the deprecated semantics, you're supposed to submount exports from the fsid=0 root, not use it directly. It's retardedly complicated which I expect is why it was deprecated. Unfortunately it seems that most of the information on the web concerning NFSv4 continues to espouse this method.

http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration#Common_NFS4_misunderstandings

When you say Windows was corrupted, you mean you ran a backup on a live VM and it corrupted that VM during the backup? Or restoring the VM from backup resulted in corruption?

Hi,it's possible that the raw file is corrupt, or have "virtual" bad sectors

can you try (vm offline) "qemu-img convert -O raw -f raw vm-103-disk-1.raw temp.raw".

if some bad block exist, it should hang too.


 
Hiya,

I am also having a similar issue and I realised that this seems to happen if you select the compression level to fast 2 VMs one win 2003 64 and another win 2003 fails. But I i select the compression level to gzip (good) those 2 vms complete the backup.

Here is the backup log when it fails:

INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/Backup/dump/vzdump-qemu-101-2013_03_22-13_27_48.vma.lzo'
INFO: started backup task '82f86f44-f9bc-4c8e-a959-b418be2bbca2'
INFO: status: 0% (55377920/42949672960), sparse 0% (2142208), duration 3, 18/17 MB/s
INFO: status: 1% (456130560/42949672960), sparse 0% (5509120), duration 20, 23/23 MB/s
INFO: status: 2% (865206272/42949672960), sparse 0% (8134656), duration 101, 5/5 MB/s
INFO: status: 3% (1290665984/42949672960), sparse 0% (17051648), duration 158, 7/7 MB/s
INFO: status: 4% (1728315392/42949672960), sparse 0% (18927616), duration 224, 6/6 MB/s
INFO: status: 5% (2158166016/42949672960), sparse 0% (22749184), duration 281, 7/7 MB/s
INFO: status: 6% (2589720576/42949672960), sparse 0% (23556096), duration 349, 6/6 MB/s
INFO: status: 7% (3012493312/42949672960), sparse 0% (26382336), duration 400, 8/8 MB/s
INFO: status: 8% (3436380160/42949672960), sparse 0% (29450240), duration 454, 7/7 MB/s
INFO: status: 9% (3875471360/42949672960), sparse 0% (127868928), duration 502, 9/7 MB/s
INFO: status: 10% (4304273408/42949672960), sparse 0% (130252800), duration 595, 4/4 MB/s
INFO: status: 11% (4731437056/42949672960), sparse 0% (131031040), duration 642, 9/9 MB/s
INFO: status: 12% (5165809664/42949672960), sparse 0% (135884800), duration 692, 8/8 MB/s
INFO: status: 13% (5584650240/42949672960), sparse 0% (136548352), duration 770, 5/5 MB/s
INFO: status: 14% (6013190144/42949672960), sparse 0% (146993152), duration 841, 6/5 MB/s
INFO: status: 15% (6445531136/42949672960), sparse 0% (147652608), duration 916, 5/5 MB/s
INFO: status: 16% (6875971584/42949672960), sparse 0% (148582400), duration 977, 7/7 MB/s
INFO: status: 17% (7302021120/42949672960), sparse 0% (149118976), duration 1035, 7/7 MB/s
INFO: status: 18% (7734689792/42949672960), sparse 0% (159916032), duration 1096, 7/6 MB/s
INFO: status: 19% (8168472576/42949672960), sparse 0% (160948224), duration 1173, 5/5 MB/s
INFO: status: 20% (8595570688/42949672960), sparse 0% (163991552), duration 1230, 7/7 MB/s
INFO: status: 21% (9026994176/42949672960), sparse 0% (176762880), duration 1304, 5/5 MB/s
INFO: status: 22% (9463267328/42949672960), sparse 0% (355426304), duration 1352, 9/5 MB/s
INFO: status: 23% (9881780224/42949672960), sparse 0% (364265472), duration 1393, 10/9 MB/s
INFO: status: 24% (10334699520/42949672960), sparse 0% (367247360), duration 1450, 7/7 MB/s
INFO: status: 25% (10740236288/42949672960), sparse 0% (367718400), duration 1527, 5/5 MB/s
INFO: status: 26% (11172052992/42949672960), sparse 0% (367808512), duration 1586, 7/7 MB/s
INFO: status: 27% (11597447168/42949672960), sparse 0% (371941376), duration 1642, 7/7 MB/s
INFO: status: 28% (12034375680/42949672960), sparse 0% (379711488), duration 1731, 4/4 MB/s
INFO: status: 29% (12460621824/42949672960), sparse 0% (383131648), duration 1817, 4/4 MB/s
INFO: status: 30% (12903120896/42949672960), sparse 0% (400654336), duration 1874, 7/7 MB/s
INFO: status: 31% (13315014656/42949672960), sparse 0% (409513984), duration 1897, 17/17 MB/s
INFO: status: 32% (13751287808/42949672960), sparse 0% (412446720), duration 1970, 5/5 MB/s
INFO: status: 33% (14182449152/42949672960), sparse 0% (412999680), duration 2024, 7/7 MB/s
INFO: status: 34% (14606991360/42949672960), sparse 0% (414879744), duration 2086, 6/6 MB/s
INFO: status: 35% (15036448768/42949672960), sparse 0% (418148352), duration 2117, 13/13 MB/s
INFO: status: 36% (15475146752/42949672960), sparse 0% (419086336), duration 2154, 11/11 MB/s
INFO: status: 37% (15898640384/42949672960), sparse 0% (419827712), duration 2198, 9/9 MB/s
INFO: status: 38% (16322789376/42949672960), sparse 0% (419934208), duration 2243, 9/9 MB/s
INFO: status: 39% (16757948416/42949672960), sparse 0% (419983360), duration 2309, 6/6 MB/s
ERROR: VM 101 not running
INFO: aborting backup job
ERROR: VM 101 not running
ERROR: Backup of VM 101 failed - VM 101 not running


Hope this helps to assist.

I keep monitoring to see.

Cheers,

Raj
 
I'm having similar problem. Machine stops DURING backup. It has happened 3 times on last 10 backups, using two different NFS servers (see storage.cfg below):

Code:
INFO: starting new backup job: vzdump 8105 8106 8109 8200 8107 --quiet 1  --mode snapshot --mailto root --compress lzo --storage  Filer.122.21.backups4
INFO: Starting Backup of VM 8105 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/Filer.122.21.backups4/dump/vzdump-qemu-8105-2013_04_09-05_35_02.vma.lzo'
INFO: started backup task '7be2f087-657f-49dd-aa54-e8482868f50b'
INFO: status: 1% (143392768/10737418240), sparse 0% (2740224), duration 3, 47/46 MB/s
INFO: status: 2% (302448640/10737418240), sparse 0% (3272704), duration 6, 53/52 MB/s
INFO: status: 4% (455016448/10737418240), sparse 0% (3866624), duration 9, 50/50 MB/s
INFO: status: 5% (598671360/10737418240), sparse 0% (4161536), duration 12, 47/47 MB/s
INFO: status: 7% (752943104/10737418240), sparse 0% (4657152), duration 15, 51/51 MB/s
INFO: status: 8% (887750656/10737418240), sparse 0% (5648384), duration 38, 5/5 MB/s
INFO: status: 9% (1046478848/10737418240), sparse 0% (7856128), duration 41, 52/52 MB/s

..... ...... .. . .. . . ...................        ...........           ................. ...... .. . .. . . ...................        ...........           ............
INFO: status: 21% (2255880192/10737418240), sparse 0% (21585920), duration 100, 49/48 MB/s
INFO: status: 22% (2400845824/10737418240), sparse 0% (22458368), duration 103, 48/48 MB/s
INFO: status: 23% (2550857728/10737418240), sparse 0% (23212032), duration 106, 50/49 MB/s
INFO: status: 25% (2695495680/10737418240), sparse 0% (23924736), duration 109, 48/47 MB/s
ERROR: VM 8105 not running
INFO: aborting backup job
ERROR: VM 8105 not running
ERROR: Backup of VM 8105 failed - VM 8105 not running

Rest of machines performed backup correctly.

Checked for corruption as suggeted resulted in NO error
Code:
qemu-img convert -O raw -f raw vm-8105-disk-1.raw temp.raw



Code:
# 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-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
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
~#

Code:
# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content images,iso,vztmpl,rootdir
        maxfiles 0

nfs: Filer.122.20.backups4
        path /mnt/pve/Filer.122.20.backups4
        server 192.168.122.20
        export /mnt/vg-20/nfs/backups
        options vers=3
        content backup
        maxfiles 4

nfs: Filer.122.21.backups4
        path /mnt/pve/Filer.122.21.backups4
        server 192.168.122.21
        export /datosnfs
        options vers=3
        content backup
        maxfiles 4


VM is Windows XP
Code:
# cat /etc/pve/nodes/proxmox177/qemu-server/8105.conf
#
acpi: 1
boot: c
bootdisk: ide0
cores: 2
cpuunits: 1000
freeze: 0
ide0: local:8105/vm-8105-disk-1.raw
kvm: 1
memory: 756
name: Administra-200.105
net0: rtl8139=DE:7D:8E:ED:BF:99,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
startup: order=1,up=20,down=10
#

Any hint ??
I will switch backup type to gzip and report ....
 
Is there any hint in /var/log/syslog?
Nothing I can see. Full content of syslog :
Code:
Apr  9 05:35:01 proxmox177 /USR/SBIN/CRON[444039]: (root) CMD (vzdump 8105 8106 8109 8200 8107 --quiet 1 --mailto root --mode snapshot --compress lzo --storage Filer.122.21.backups4)
Apr  9 05:35:02 proxmox177 vzdump[444040]: <root@pam> starting task UPID:proxmox177:0006C6FC:09ABD5DB:51638C66:vzdump::root@pam:
Apr  9 05:35:02 proxmox177 vzdump[444156]: INFO: starting new backup job: vzdump 8105 8106 8109 8200 8107 --quiet 1 --mode snapshot --mailto root --compress lzo --storage Filer.122.21.backups4
Apr  9 05:35:02 proxmox177 vzdump[444156]: INFO: Starting Backup of VM 8105 (qemu)
Apr  9 05:35:03 proxmox177 qm[444175]: <root@pam> update VM 8105: -lock backup
Apr  9 05:36:04 proxmox177 pvedaemon[1450]: worker 441873 finished
Apr  9 05:36:04 proxmox177 pvedaemon[1450]: starting 1 worker(s)
Apr  9 05:36:04 proxmox177 pvedaemon[1450]: worker 444496 started
Apr  9 05:37:30 proxmox177 kernel: vmbr0: port 2(tap8105i0) entering disabled state
Apr  9 05:37:30 proxmox177 kernel: vmbr0: port 2(tap8105i0) entering disabled state
Apr  9 05:37:30 proxmox177 vzdump[444156]: VM 8105 qmp command failed - VM 8105 not running
Apr  9 05:37:30 proxmox177 vzdump[444156]: VM 8105 qmp command failed - VM 8105 not running
Apr  9 05:37:31 proxmox177 vzdump[444156]: ERROR: Backup of VM 8105 failed - VM 8105 not running
 
I have the same problem with stop/restart of VM during backup after upgrade proxmox to v.2.3.
VM 100 with Windows Server 2008 R2 64-bit - restart (with BSoD), VM 101 with FreeBSD 7.4 32-bit - shutdown.


Code:
# cat qemu-101.log
Apr 10 03:00:02 INFO: Starting Backup of VM 101 (qemu)
Apr 10 03:00:02 INFO: status = running
Apr 10 03:00:03 INFO: backup mode: snapshot
Apr 10 03:00:03 INFO: bandwidth limit: 100000 KB/s
Apr 10 03:00:03 INFO: ionice priority: 7
Apr 10 03:00:03 INFO: creating archive '/mnt/pve/ns4300n/dump/vzdump-qemu-101-2013_04_10-03_00_02.vma.lzo'
Apr 10 03:00:03 INFO: started backup task 'f610385f-4b73-40a4-99b1-82b5d09aff8d'
Apr 10 03:00:06 INFO: status: 2% (208797696/8589934592), sparse 0% (35282944), duration 3, 69/57 MB/s
Apr 10 03:00:09 INFO: status: 5% (436600832/8589934592), sparse 2% (240435200), duration 6, 75/7 MB/s
Apr 10 03:00:12 INFO: status: 7% (669384704/8589934592), sparse 5% (473219072), duration 9, 77/0 MB/s
Apr 10 03:00:15 INFO: status: 10% (867368960/8589934592), sparse 7% (670875648), duration 12, 65/0 MB/s
Apr 10 03:00:18 INFO: status: 12% (1070989312/8589934592), sparse 10% (874356736), duration 15, 67/0 MB/s
Apr 10 03:00:21 INFO: status: 13% (1193279488/8589934592), sparse 11% (995913728), duration 18, 40/0 MB/s
Apr 10 03:00:24 INFO: status: 16% (1400307712/8589934592), sparse 14% (1202941952), duration 21, 69/0 MB/s
Apr 10 03:00:27 INFO: status: 19% (1647706112/8589934592), sparse 16% (1445167104), duration 24, 82/1 MB/s
Apr 10 03:00:30 INFO: status: 21% (1850277888/8589934592), sparse 16% (1450233856), duration 27, 67/65 MB/s
Apr 10 03:00:33 INFO: status: 25% (2149449728/8589934592), sparse 16% (1452072960), duration 30, 99/99 MB/s
Apr 10 03:00:36 INFO: status: 26% (2306473984/8589934592), sparse 16% (1455091712), duration 33, 52/51 MB/s
Apr 10 03:00:39 INFO: status: 29% (2520121344/8589934592), sparse 18% (1609269248), duration 36, 71/19 MB/s
Apr 10 03:00:42 INFO: status: 30% (2577137664/8589934592), sparse 19% (1646456832), duration 39, 19/6 MB/s
Apr 10 03:01:19 INFO: status: 31% (2691563520/8589934592), sparse 19% (1703239680), duration 76, 3/1 MB/s
Apr 10 03:01:22 INFO: status: 33% (2890858496/8589934592), sparse 19% (1708363776), duration 79, 66/64 MB/s
Apr 10 03:01:25 INFO: status: 35% (3090546688/8589934592), sparse 19% (1713147904), duration 82, 66/64 MB/s
Apr 10 03:01:28 INFO: status: 38% (3291873280/8589934592), sparse 20% (1722425344), duration 85, 67/64 MB/s
Apr 10 03:01:31 INFO: status: 40% (3495428096/8589934592), sparse 20% (1727262720), duration 88, 67/66 MB/s
Apr 10 03:01:34 INFO: status: 42% (3670999040/8589934592), sparse 20% (1772363776), duration 91, 58/43 MB/s
Apr 10 03:01:37 INFO: status: 44% (3801088000/8589934592), sparse 20% (1773760512), duration 94, 43/42 MB/s
Apr 10 03:01:40 INFO: status: 45% (3866427392/8589934592), sparse 20% (1778192384), duration 97, 21/20 MB/s
Apr 10 03:02:51 INFO: status: 46% (3953131520/8589934592), sparse 20% (1779019776), duration 168, 1/1 MB/s
Apr 10 03:02:55 INFO: status: 47% (4097572864/8589934592), sparse 20% (1782321152), duration 172, 36/35 MB/s
Apr 10 03:02:58 INFO: status: 49% (4264820736/8589934592), sparse 20% (1787052032), duration 175, 55/54 MB/s
Apr 10 03:03:01 INFO: status: 51% (4383047680/8589934592), sparse 20% (1787076608), duration 178, 39/39 MB/s
Apr 10 03:03:04 INFO: status: 52% (4516413440/8589934592), sparse 20% (1790357504), duration 181, 44/43 MB/s
Apr 10 03:03:07 INFO: status: 54% (4665442304/8589934592), sparse 20% (1793597440), duration 184, 49/48 MB/s
Apr 10 03:03:10 INFO: status: 56% (4871356416/8589934592), sparse 21% (1820491776), duration 187, 68/59 MB/s
Apr 10 03:03:13 INFO: status: 58% (5024448512/8589934592), sparse 21% (1826103296), duration 190, 51/49 MB/s
Apr 10 03:03:16 INFO: status: 60% (5157945344/8589934592), sparse 21% (1826385920), duration 193, 44/44 MB/s
Apr 10 03:03:20 INFO: status: 61% (5248319488/8589934592), sparse 21% (1829777408), duration 197, 22/21 MB/s
Apr 10 03:04:48 ERROR: VM 101 not running
Apr 10 03:04:48 INFO: aborting backup job
Apr 10 03:04:48 ERROR: VM 101 not running
Apr 10 03:04:53 ERROR: Backup of VM 101 failed - VM 101 not running






Code:
# cat vzdump-qemu-100-2013_04_07-03_00_02.log
Apr 07 03:00:02 INFO: Starting Backup of VM 100 (qemu)
Apr 07 03:00:02 INFO: status = running
Apr 07 03:00:03 INFO: backup mode: snapshot
Apr 07 03:00:03 INFO: bandwidth limit: 100000 KB/s
Apr 07 03:00:03 INFO: ionice priority: 7
Apr 07 03:00:03 INFO: creating archive '/mnt/pve/ns4300n/dump/vzdump-qemu-100-2013_04_07-03_00_02.vma.lzo'
Apr 07 03:00:04 INFO: started backup task '60e7434a-1026-43e0-bdb9-a22d6fd07825'
Apr 07 03:00:07 INFO: status: 0% (219807744/161061273600), sparse 0% (97722368), duration 3, 73/40 MB/s
Apr 07 03:00:34 INFO: status: 1% (1646460928/161061273600), sparse 0% (131309568), duration 30, 52/51 MB/s
Apr 07 03:04:03 INFO: status: 2% (3265462272/161061273600), sparse 0% (149409792), duration 239, 7/7 MB/s
Apr 07 03:06:02 INFO: status: 3% (4886102016/161061273600), sparse 0% (285003776), duration 358, 13/12 MB/s
Apr 07 03:08:05 INFO: status: 4% (6478036992/161061273600), sparse 0% (296853504), duration 481, 12/12 MB/s
Apr 07 03:11:45 INFO: status: 5% (8057061376/161061273600), sparse 0% (316284928), duration 701, 7/7 MB/s
Apr 07 03:13:02 INFO: status: 6% (9727115264/161061273600), sparse 0% (1351733248), duration 778, 21/8 MB/s
Apr 07 03:13:20 INFO: status: 7% (11329601536/161061273600), sparse 1% (2954219520), duration 796, 89/0 MB/s
Apr 07 03:13:36 INFO: status: 8% (12975865856/161061273600), sparse 2% (4600483840), duration 812, 102/0 MB/s
Apr 07 03:13:51 INFO: status: 9% (14529527808/161061273600), sparse 3% (6154145792), duration 827, 103/0 MB/s
Apr 07 03:16:08 INFO: status: 10% (16167075840/161061273600), sparse 3% (6326964224), duration 964, 11/10 MB/s
Apr 07 03:18:15 INFO: status: 11% (17754030080/161061273600), sparse 3% (6333530112), duration 1091, 12/12 MB/s
Apr 07 03:20:54 INFO: status: 12% (19360317440/161061273600), sparse 3% (6352105472), duration 1250, 10/9 MB/s
Apr 07 03:23:10 INFO: status: 13% (20943601664/161061273600), sparse 3% (6360797184), duration 1386, 11/11 MB/s
Apr 07 03:25:06 INFO: status: 14% (22586785792/161061273600), sparse 3% (6365941760), duration 1502, 14/14 MB/s
Apr 07 03:27:15 INFO: status: 15% (24185339904/161061273600), sparse 3% (6365941760), duration 1631, 12/12 MB/s
Apr 07 03:27:55 INFO: status: 16% (25770000384/161061273600), sparse 3% (6365941760), duration 1671, 39/39 MB/s
Apr 07 03:29:46 INFO: status: 17% (27452375040/161061273600), sparse 4% (7711051776), duration 1782, 15/3 MB/s
Apr 07 03:30:03 INFO: status: 18% (29022158848/161061273600), sparse 5% (8993914880), duration 1799, 92/16 MB/s
Apr 07 03:30:19 INFO: status: 19% (30668423168/161061273600), sparse 6% (10640179200), duration 1815, 102/0 MB/s
Apr 07 03:30:35 INFO: status: 20% (32314687488/161061273600), sparse 7% (12286443520), duration 1831, 102/0 MB/s
Apr 07 03:30:50 INFO: status: 21% (33868349440/161061273600), sparse 8% (13840105472), duration 1846, 103/0 MB/s
Apr 07 03:31:06 INFO: status: 22% (35514613760/161061273600), sparse 9% (15486369792), duration 1862, 102/0 MB/s
Apr 07 03:31:21 INFO: status: 23% (37057986560/161061273600), sparse 10% (17029742592), duration 1877, 102/0 MB/s
Apr 07 03:31:37 INFO: status: 24% (38704250880/161061273600), sparse 11% (18676006912), duration 1893, 102/0 MB/s
Apr 07 03:31:53 INFO: status: 25% (40360804352/161061273600), sparse 12% (20332560384), duration 1909, 103/0 MB/s
Apr 07 03:32:08 INFO: status: 26% (41904177152/161061273600), sparse 13% (21875933184), duration 1924, 102/0 MB/s
Apr 07 03:32:24 INFO: status: 27% (43550441472/161061273600), sparse 14% (23522197504), duration 1940, 102/0 MB/s
Apr 07 03:32:40 INFO: status: 28% (45196705792/161061273600), sparse 15% (25168461824), duration 1956, 102/0 MB/s
Apr 07 03:32:55 INFO: status: 29% (46740078592/161061273600), sparse 16% (26711834624), duration 1971, 102/0 MB/s
Apr 07 03:33:11 INFO: status: 30% (48396632064/161061273600), sparse 17% (28368388096), duration 1987, 103/0 MB/s
Apr 07 03:33:26 INFO: status: 31% (49940004864/161061273600), sparse 18% (29911760896), duration 2002, 102/0 MB/s
Apr 07 03:33:43 INFO: status: 32% (51586269184/161061273600), sparse 19% (31558025216), duration 2019, 96/0 MB/s
Apr 07 03:33:59 INFO: status: 33% (53232533504/161061273600), sparse 20% (33204289536), duration 2035, 102/0 MB/s
Apr 07 03:34:23 INFO: status: 34% (54788096000/161061273600), sparse 20% (33688539136), duration 2059, 64/44 MB/s
Apr 07 03:37:09 INFO: status: 35% (56380489728/161061273600), sparse 20% (33821507584), duration 2225, 9/8 MB/s
Apr 07 03:38:34 INFO: status: 36% (58033045504/161061273600), sparse 21% (34167746560), duration 2310, 19/15 MB/s
Apr 07 03:40:44 INFO: status: 37% (59618164736/161061273600), sparse 21% (34317766656), duration 2440, 12/11 MB/s
Apr 07 03:43:44 INFO: status: 38% (61231726592/161061273600), sparse 21% (34317811712), duration 2620, 8/8 MB/s
Apr 07 03:46:42 INFO: status: 39% (62850662400/161061273600), sparse 21% (34317901824), duration 2798, 9/9 MB/s
Apr 07 03:49:09 INFO: status: 40% (64457211904/161061273600), sparse 21% (34318368768), duration 2945, 10/10 MB/s
Apr 07 03:53:05 INFO: status: 41% (66069594112/161061273600), sparse 21% (34319790080), duration 3181, 6/6 MB/s
Apr 07 03:55:57 INFO: status: 42% (67655565312/161061273600), sparse 21% (34320855040), duration 3353, 9/9 MB/s
Apr 07 03:58:13 INFO: status: 43% (69259624448/161061273600), sparse 21% (34321485824), duration 3489, 11/11 MB/s
Apr 07 04:02:21 INFO: status: 44% (70875086848/161061273600), sparse 21% (34322235392), duration 3737, 6/6 MB/s
Apr 07 04:04:01 INFO: status: 45% (72486748160/161061273600), sparse 21% (34326994944), duration 3837, 16/16 MB/s
Apr 07 04:08:31 INFO: status: 46% (74117414912/161061273600), sparse 21% (34328002560), duration 4107, 6/6 MB/s
Apr 07 04:11:51 INFO: status: 47% (75699716096/161061273600), sparse 21% (34328174592), duration 4307, 7/7 MB/s
Apr 07 04:14:12 INFO: status: 48% (77321732096/161061273600), sparse 21% (34328616960), duration 4448, 11/11 MB/s
Apr 07 04:16:59 INFO: status: 49% (78946631680/161061273600), sparse 21% (34329862144), duration 4615, 9/9 MB/s
Apr 07 04:21:47 INFO: status: 50% (80545382400/161061273600), sparse 21% (34330488832), duration 4903, 5/5 MB/s
Apr 07 04:24:56 INFO: status: 51% (82152914944/161061273600), sparse 21% (34331185152), duration 5092, 8/8 MB/s
Apr 07 04:27:16 INFO: status: 52% (83775979520/161061273600), sparse 21% (34331185152), duration 5232, 11/11 MB/s
Apr 07 04:31:06 INFO: status: 53% (85375778816/161061273600), sparse 21% (34331398144), duration 5462, 6/6 MB/s
Apr 07 04:32:58 INFO: status: 54% (86973808640/161061273600), sparse 21% (34348101632), duration 5574, 14/14 MB/s
Apr 07 04:36:04 INFO: status: 55% (88605261824/161061273600), sparse 21% (34363383808), duration 5760, 8/8 MB/s
Apr 07 04:39:56 INFO: status: 56% (90210893824/161061273600), sparse 21% (34378813440), duration 5992, 6/6 MB/s
Apr 07 04:42:12 INFO: status: 57% (91819802624/161061273600), sparse 21% (34379358208), duration 6128, 11/11 MB/s
Apr 07 04:44:42 INFO: status: 58% (93426155520/161061273600), sparse 21% (34379481088), duration 6278, 10/10 MB/s
Apr 07 04:48:47 INFO: status: 59% (95037227008/161061273600), sparse 21% (34379481088), duration 6523, 6/6 MB/s
Apr 07 04:51:22 INFO: status: 60% (96654852096/161061273600), sparse 21% (34379513856), duration 6678, 10/10 MB/s
Apr 07 04:55:22 INFO: status: 61% (98262974464/161061273600), sparse 21% (34379554816), duration 6918, 6/6 MB/s
Apr 07 04:58:53 INFO: status: 62% (99859890176/161061273600), sparse 21% (34379669504), duration 7129, 7/7 MB/s
Apr 07 05:01:34 INFO: status: 63% (101489377280/161061273600), sparse 21% (34379702272), duration 7290, 10/10 MB/s
Apr 07 05:04:00 INFO: status: 64% (103085834240/161061273600), sparse 21% (34379825152), duration 7436, 10/10 MB/s
Apr 07 05:07:19 INFO: status: 65% (104708571136/161061273600), sparse 21% (34379948032), duration 7635, 8/8 MB/s
Apr 07 05:09:21 INFO: status: 66% (106303258624/161061273600), sparse 21% (34380038144), duration 7757, 13/13 MB/s
Apr 07 05:13:15 INFO: status: 67% (107950768128/161061273600), sparse 21% (34380111872), duration 7991, 7/7 MB/s
Apr 07 05:15:51 INFO: status: 68% (109566361600/161061273600), sparse 21% (34380173312), duration 8147, 10/10 MB/s
Apr 07 05:18:27 INFO: status: 69% (111148597248/161061273600), sparse 21% (34380222464), duration 8303, 10/10 MB/s
Apr 07 05:21:11 INFO: status: 70% (112763076608/161061273600), sparse 21% (34380308480), duration 8467, 9/9 MB/s
Apr 07 05:23:33 INFO: status: 71% (114391056384/161061273600), sparse 21% (34380390400), duration 8609, 11/11 MB/s
Apr 07 05:26:00 INFO: status: 72% (115980763136/161061273600), sparse 21% (34380460032), duration 8756, 10/10 MB/s
Apr 07 05:28:55 INFO: status: 73% (117607890944/161061273600), sparse 21% (34380521472), duration 8931, 9/9 MB/s
Apr 07 05:31:20 INFO: status: 74% (119211098112/161061273600), sparse 21% (34380578816), duration 9076, 11/11 MB/s
Apr 07 05:33:49 INFO: status: 75% (120820137984/161061273600), sparse 21% (34381594624), duration 9225, 10/10 MB/s
Apr 07 05:37:39 INFO: status: 76% (122408599552/161061273600), sparse 21% (34381705216), duration 9455, 6/6 MB/s
Apr 07 05:39:18 INFO: status: 77% (124038610944/161061273600), sparse 21% (34381705216), duration 9554, 16/16 MB/s
Apr 07 05:43:54 INFO: status: 78% (125636313088/161061273600), sparse 21% (34381733888), duration 9830, 5/5 MB/s
Apr 07 05:46:29 INFO: status: 79% (127256625152/161061273600), sparse 21% (34381877248), duration 9985, 10/10 MB/s
Apr 07 05:50:16 INFO: status: 80% (128870580224/161061273600), sparse 21% (34381963264), duration 10212, 7/7 MB/s
Apr 07 05:52:06 INFO: status: 81% (130467954688/161061273600), sparse 21% (34381963264), duration 10322, 14/14 MB/s
Apr 07 05:56:23 INFO: status: 82% (132093902848/161061273600), sparse 21% (34381963264), duration 10579, 6/6 MB/s
Apr 07 05:58:50 INFO: status: 83% (133714673664/161061273600), sparse 21% (34381963264), duration 10726, 11/11 MB/s
Apr 07 06:01:49 INFO: status: 84% (135293894656/161061273600), sparse 21% (34381963264), duration 10905, 8/8 MB/s
Apr 07 06:04:52 INFO: status: 85% (136912830464/161061273600), sparse 21% (34382045184), duration 11088, 8/8 MB/s
Apr 07 06:06:55 INFO: status: 86% (138526851072/161061273600), sparse 21% (34382094336), duration 11211, 13/13 MB/s
Apr 07 06:11:31 INFO: status: 87% (140155486208/161061273600), sparse 21% (34382143488), duration 11487, 5/5 MB/s
Apr 07 06:13:58 INFO: status: 88% (141749846016/161061273600), sparse 21% (34382184448), duration 11634, 10/10 MB/s
Apr 07 06:17:03 INFO: status: 89% (143365111808/161061273600), sparse 21% (34382225408), duration 11819, 8/8 MB/s
Apr 07 06:18:33 INFO: status: 90% (144987455488/161061273600), sparse 21% (34382266368), duration 11909, 18/18 MB/s
Apr 07 06:20:43 INFO: status: 91% (146594660352/161061273600), sparse 21% (34382303232), duration 12039, 12/12 MB/s
Apr 07 06:25:06 INFO: status: 92% (148203896832/161061273600), sparse 21% (34382336000), duration 12302, 6/6 MB/s
Apr 07 06:28:03 INFO: status: 93% (149820211200/161061273600), sparse 21% (34382356480), duration 12479, 9/9 MB/s
Apr 07 06:29:26 INFO: status: 94% (151398383616/161061273600), sparse 21% (34891046912), duration 12562, 19/12 MB/s
Apr 07 06:29:50 INFO: status: 95% (153029312512/161061273600), sparse 22% (36521947136), duration 12586, 67/0 MB/s
Apr 07 06:31:10 INFO: status: 96% (154720600064/161061273600), sparse 23% (37871472640), duration 12666, 21/4 MB/s
Apr 07 06:31:25 INFO: status: 97% (156263972864/161061273600), sparse 24% (39414845440), duration 12681, 102/0 MB/s
Apr 07 06:31:41 INFO: status: 98% (157910237184/161061273600), sparse 25% (41061109760), duration 12697, 102/0 MB/s
Apr 07 06:31:56 INFO: status: 99% (159453609984/161061273600), sparse 26% (42604482560), duration 12712, 102/0 MB/s
Apr 07 06:32:12 INFO: status: 100% (161061273600/161061273600), sparse 27% (44212142080), duration 12728, 100/0 MB/s
Apr 07 06:32:12 INFO: transferred 161061 MB in 12728 seconds (12 MB/s)
Apr 07 06:32:12 INFO: archive file size: 81.85GB
Apr 07 06:32:12 INFO: delete old backup '/mnt/pve/ns4300n/dump/vzdump-qemu-100-2013_04_05-23_00_03.vma.lzo'
Apr 07 06:33:28 INFO: Finished Backup of VM 100 (03:33:26)


In logfile - all OK, but VM restart with BSoD




My configuration:
Code:
# 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-16-pve: 2.6.32-82
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-14-pve: 2.6.32-74
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


Code:
# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content images,iso,vztmpl,rootdir




nfs: ns4300n
        path /mnt/pve/ns4300n
        server 192.168.xxx.xxx
        export /VOLUME1/PUBLIC
        content backup
        maxfiles 1


VM 100 with Windows Server 2008 R2 64-bit (create after upgrade proxmox to v.2.3)
Code:
# cat /etc/pve/nodes/proxmox/qemu-server/100.conf
balloon: 2048
boot: c
bootdisk: virtio0
cores: 6
ide2: local:iso/virtio-win-0.1-52.iso,media=cdrom,size=57126K
memory: 6144
name: xxx
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0
onboot: 1
ostype: win7
sockets: 1
virtio0: local:100/vm-100-disk-1.raw,size=150G


VM 101 with FreeBSD 7.4 32-bit (create before upgrade proxmox to v.2.3)
Code:
# cat /etc/pve/nodes/proxmox/qemu-server/101.conf
args: -option-rom 8xx_64.rom,bootindex=1
boot: c
bootdisk: scsi0
cores: 1
cpu: qemu32
ide2: none,media=cdrom
memory: 1024
name: xxx
net0: e1000=xx:xx:xx:xx:xx:xx,bridge=vmbr0
onboot: 1
ostype: other
scsi0: local:101/vm-101-disk-1.vmdk
sockets: 1


I change backup compression from LZO to GZIP and wait tomorrow's logs.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!