Search results

Problem solved! Thanks

After an uptime > 600 i had to restart a guest. But now i cant boot the VM Error starting worker failed: unable to parse worker upid 'UPID:proxmox:00095558:106951258:53EC9BDC:vncproxy:105:root@pam:' (500) Any Idea?

Hi! I've seen your using an Synology DS1815+ in HA Mode. How many VM's are running on this Cluster? Is the performance good enough for an produktion environment?

Hi! I know the difference between CIFS and NFS. With 3.0 my backup was written to an nfs share. Since 3.1 vzdump performance ist very bad so i tried to make backups to an cifs share which was not better.

Hi Dietmar! Is there anything which has changed in NFS Settings since Proxmox 3.0?

Sorry! My fault. But why is NFS Performance so bad, since upgrading to 3.1?

Hi Dietmar! I don't think so. The share "proxbackup" is mounted as /media/proxbackup In storage for testing it's labeld as sbackup This should be the free space on the share /media/proxbackup

Hi! Since i've upgraded from 3.0 to 3.1 NFS Performance ist horrible. Before: 102: Nov 06 02:35:59 INFO: Starting Backup of VM 102 (qemu) 102: Nov 06 02:35:59 INFO: status = running 102: Nov 06 02:35:59 INFO: exclude disk 'virtio1' (backup=no) 102: Nov 06 02:35:59 INFO: backup mode: snapshot...