<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
i've also ran into this problem with NFS Storage. On other systems
the nfs share as backup volume works fine, only on one pve cluster
is does not work.<br>
<br>
i've build a workaround script, which just checks if the backup
gets a lock timeout. if this occours, backup is tried again for
max 3 times. not really a good solution, but this works for me. <br>
<br>
i don't think that there is a problem with nfs, cause on other
systems the nfs share for backup is doin fine.<br>
<br>
greetz,<br>
patrick<br>
<br>
On 18.11.2013 14:05, David Thompson wrote:<br>
</div>
<blockquote
cite="mid:9EBA146F-87F3-49A3-8928-587E8781ACF3@digitaltransitions.ca"
type="cite">
<pre wrap="">Hi everyone,
I have an issue with a intel modular server with 5 nodes. Whenever the nodes run a backup, some of them fail and often the VM’s become locked. These VM’s are all QEMU based virtual servers and not openvz as they are Windows servers.
Often everyday, I need to restart the cluster after something like this appears in the backup logs by going to one of the nodes that is red and restarting the PVECluster, which I believe is the correct way to do this, so please correct my if I’m wrong.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INFO: starting new backup job: vzdump 103 101 --quiet 1 --mailto snip@snip --mode snapshot --compress lzo --storage nfsData --node node2
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: unable to open file '/etc/pve/nodes/node2/qemu-server/101.conf.tmp.666400' - Software caused connection abort
INFO: update VM 101: -lock backup
ERROR: Backup of VM 101 failed - command 'qm set 101 --lock backup' failed: exit code 107
INFO: Starting Backup of VM 103 (qemu)
ERROR: Backup of VM 103 failed - unable to find configuration file for VM 103 - no such machine
INFO: Backup job finished with errors
TASK ERROR: job errors
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INFO: starting new backup job: vzdump 106 --quiet 1 --mailto snip@snip --mode snapshot --compress lzo --storage nfsData --node node4
INFO: Starting Backup of VM 106 (qemu)
INFO: status = running
INFO: unable to open file '/etc/pve/nodes/node4/qemu-server/106.conf.tmp.641046' - File exists
INFO: update VM 106: -lock backup
ERROR: Backup of VM 106 failed - command 'qm set 106 --lock backup' failed: exit code 17
INFO: Backup job finished with errors
TASK ERROR: job errors
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The backups all go to an NFS share mounted on on a private network over gig ethernet.
Any ideas as to why this is happening? The backups are all staggered from the hosts to back up to the share
Thanks for any insight.
_____________________________
David Thompson
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pve-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pve-user@pve.proxmox.com">pve-user@pve.proxmox.com</a>
<a class="moz-txt-link-freetext" href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user</a>
</pre>
</blockquote>
<br>
</body>
</html>