problem with backup

ds(ds)

Active Member
Sep 11, 2011
60
0
26
sorry for bad english....
i have Proxmox 2.2-24 (no raid) and nfs-storage (openfiler)

Proxmox have 2 virtual systems:
vm-100-disk-1.raw (40GB)
vm-101-disk-1.qcow2 (90GB)

On Friday I run backup manually (vm-100) through the [backup now]->[snapshot-lzo]. Archive was made successfully for 1 hour 15 minutes.
I set [backup job] in Friday 2 systems.
But on Monday, all of them were shuted down. I had nothing to do just to start it manually. There was no problem with 101, but 100 doesn't ran. It was blocked by the backup.
I have to unlock it and run in normal mode.
In the openfiler folder was the image, but the size of the file was only 5GB instead of 10GB. Also there was a folder *.tmp and no log file was exist.
in Web-gui backup error: unexpected status

INFO: starting new backup job: vzdump 100 101 - quiet 1 - mode snapshot - compress lzo - storage

nfs_storage
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/ mnt/pve/nfs_storage/dump/vzdump-qemu-100-2013_03_08-20_00_02.tar.lzo'
INFO: adding '/ mnt/pve/nfs_storage/dump/vzdump-qemu-100-2013_03_08-20_00_02.tmp/qemu-server.conf'

to archive ('qemu-server.conf')
INFO: adding '/ mnt/vzsnap0/images/100/vm-100-disk-1.raw' to archive ('vm-disk-ide0.raw')

What's the problem?
 
thanks.......
strange situation...

root@proxmox:~# pvesm status
storage 'nfs_storage' is not online
local dir 1 357387084 60497884 296889200 17.43%
nfs_storage nfs 0 0 0 0 100.00%
root@proxmox:~# ping 192.168.0.45
PING 192.168.0.45 (192.168.0.45) 56(84) bytes of data.
64 bytes from 192.168.0.45: icmp_req=1 ttl=64 time=0.113 ms
.....
64 bytes from 192.168.0.45: icmp_req=14 ttl=64 time=0.123 ms
^C
--- 192.168.0.45 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 12999ms
rtt min/avg/max/mdev = 0.113/0.136/0.181/0.017 ms
root@proxmox:~# pvesm status
local dir 1 357387084 60497884 296889200 17.43%
nfs_storage nfs 1 201552896 16673792 174640896 9.22%

problems in storage....
 
thanks.......
strange situation...

root@proxmox:~# pvesm status
storage 'nfs_storage' is not online
local dir 1 357387084 60497884 296889200 17.43%
nfs_storage nfs 0 0 0 0 100.00%
root@proxmox:~# ping 192.168.0.45
PING 192.168.0.45 (192.168.0.45) 56(84) bytes of data.
64 bytes from 192.168.0.45: icmp_req=1 ttl=64 time=0.113 ms
.....
64 bytes from 192.168.0.45: icmp_req=14 ttl=64 time=0.123 ms
^C
--- 192.168.0.45 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 12999ms
rtt min/avg/max/mdev = 0.113/0.136/0.181/0.017 ms
root@proxmox:~# pvesm status
local dir 1 357387084 60497884 296889200 17.43%
nfs_storage nfs 1 201552896 16673792 174640896 9.22%

problems in storage....

nfs storage check is done with the command "/usr/bin/rpcinfo -p ipaddressofnfs"

with a timeout of 2 sec.

Can you try this command manually and send result ?
 
/usr/bin/rpcinfo -p 192.168.0.45
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 971 status
100024 1 tcp 974 status
100011 1 udp 647 rquotad
100011 2 udp 647 rquotad
100011 1 tcp 650 rquotad
100011 2 tcp 650 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 49555 nlockmgr
100021 3 udp 49555 nlockmgr
100021 4 udp 49555 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 51603 nlockmgr
100021 3 tcp 51603 nlockmgr
100021 4 tcp 51603 nlockmgr
100005 1 udp 661 mountd
100005 1 tcp 664 mountd
100005 2 udp 661 mountd
100005 2 tcp 664 mountd
100005 3 udp 661 mountd
100005 3 tcp 664 mountd
 
/usr/bin/rpcinfo -p 192.168.0.45
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 971 status
100024 1 tcp 974 status
100011 1 udp 647 rquotad
100011 2 udp 647 rquotad
100011 1 tcp 650 rquotad
100011 2 tcp 650 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 49555 nlockmgr
100021 3 udp 49555 nlockmgr
100021 4 udp 49555 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 51603 nlockmgr
100021 3 tcp 51603 nlockmgr
100021 4 tcp 51603 nlockmgr
100005 1 udp 661 mountd
100005 1 tcp 664 mountd
100005 2 udp 661 mountd
100005 2 tcp 664 mountd
100005 3 udp 661 mountd
100005 3 tcp 664 mountd

So it's works, but is it fast (< 2s)?

can you try:

"time /usr/bin/rpcinfo -p 192.168.0.45"
 
time /usr/bin/rpcinfo -p 192.168.0.45
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 971 status
100024 1 tcp 974 status
100011 1 udp 647 rquotad
100011 2 udp 647 rquotad
100011 1 tcp 650 rquotad
100011 2 tcp 650 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 49555 nlockmgr
100021 3 udp 49555 nlockmgr
100021 4 udp 49555 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 51603 nlockmgr
100021 3 tcp 51603 nlockmgr
100021 4 tcp 51603 nlockmgr
100005 1 udp 661 mountd
100005 1 tcp 664 mountd
100005 2 udp 661 mountd
100005 2 tcp 664 mountd
100005 3 udp 661 mountd
100005 3 tcp 664 mountd

real 0m0.002s
user 0m0.000s
sys 0m0.001s
 

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!