Hello Guys,
I think my question is more Win releated but I couldn’t find any hint that leads me on the right direction. I hope that one of you have an idea that brings me on track.
I’ve setup a Proxmox Cluster( 3 nodes) and try to backup my VMs to a Win 2012 NFS service. The cluster has three bondend interfaces.
Bond0 has vmbr0 assigned to it and vmbr0 has the the IP 172.18.0.3/22. It is for cluster communication and VMs traffic
Bond1 has vmbr1 assigned to it and is for backup traffic. The ip of vmbr1 is 192.168.151.3/24
The same setup is configured on the other nodes (Off course with different ip addresses)
The bonding is configured on the switches also.
On the other side there is a windows 2012 server with two nics and nfs service installed. The first nic is dedicated for normal network traffic and has the ip 172.18.0.51/22.
The second nic is for the nfs cluster backup and has the ip 192.168.151.1/24
The win server exports the directory ‘backp-vms’
On the cluster there is defined an shared nfs storage named ‘backup-vms’ connected explicitly to the IP (192.168.151.1) of the windows server.
I’ve double checked the successful mounts on the cluster nodes
Whenever I start a backup the backup is running very slow. Sometimes backup is finished after a long time, sometimes it stops with an error message like ‘lzop - broken pipes’
During the backup I see a lot messages like the following ones in syslog:
The most of the messages are disappearing after a while, the backup continues, sometimes it finishes sometimes it stops with ‘Broke pipe’.
I’ve checked the mounts on the windows server with ’showmounts –a’. But I am not really happy with its output.
It seems to me, that the backup dir is mounted from every IP of the proxmox clusters. How can this be?
I assume that this could be the root of the problem. Maybe I misunderstand the result but I think the IPs ‘172.18.0.x’ should not be mounted from the cluster nodes. I was awaiting that only the IPs 192.168.151.x are connected.
I’ve no clue what’s going wrong.
I think my question is more Win releated but I couldn’t find any hint that leads me on the right direction. I hope that one of you have an idea that brings me on track.
I’ve setup a Proxmox Cluster( 3 nodes) and try to backup my VMs to a Win 2012 NFS service. The cluster has three bondend interfaces.
Code:
pveversion --verboseproxmox-ve-2.6.32: 3.2-136 (running kernel: 2.6.32-32-pve)
pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-34
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-9
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Bond0 has vmbr0 assigned to it and vmbr0 has the the IP 172.18.0.3/22. It is for cluster communication and VMs traffic
Bond1 has vmbr1 assigned to it and is for backup traffic. The ip of vmbr1 is 192.168.151.3/24
The same setup is configured on the other nodes (Off course with different ip addresses)
The bonding is configured on the switches also.
On the other side there is a windows 2012 server with two nics and nfs service installed. The first nic is dedicated for normal network traffic and has the ip 172.18.0.51/22.
The second nic is for the nfs cluster backup and has the ip 192.168.151.1/24
The win server exports the directory ‘backp-vms’
On the cluster there is defined an shared nfs storage named ‘backup-vms’ connected explicitly to the IP (192.168.151.1) of the windows server.
I’ve double checked the successful mounts on the cluster nodes
Whenever I start a backup the backup is running very slow. Sometimes backup is finished after a long time, sometimes it stops with an error message like ‘lzop - broken pipes’
During the backup I see a lot messages like the following ones in syslog:
Code:
[LIST]
[*]zdump[6952]: ERROR: Backup of VM 100 failed - vma_queue_write: write error - Broken pipe
[*]task lzop:7665 blocked for more than 120 seconds.
[*]kernel: ct0 nfs: server 192.168.151.1 not responding, timed out
[*]WARNING: command 'df -P -B 1 /mnt/pve/backup-vms' failed: got timeout
[*]WARNING: command 'df -P -B 1 /mnt/pve/backup-vms' failed: got timeout
[/LIST]
I’ve checked the mounts on the windows server with ’showmounts –a’. But I am not really happy with its output.
Code:
showmounts -a
Alle Bereitstellungspunkte auf DMC-BACKUP1-NI:
172.18.0.2 : /backup-vms
172.18.0.3 : /backup-vms
172.18.0.4 : /backup-vms
192.168.151.2 : /backup-vms
192.168.151.3 : /backup-vms
192.168.151.4 : /backup-vms
It seems to me, that the backup dir is mounted from every IP of the proxmox clusters. How can this be?
I assume that this could be the root of the problem. Maybe I misunderstand the result but I think the IPs ‘172.18.0.x’ should not be mounted from the cluster nodes. I was awaiting that only the IPs 192.168.151.x are connected.
I’ve no clue what’s going wrong.