Search results

I get error GSpice-WARNING **: Socket I/O timed out Any ideas?

The VM locks up (only the one been backed up) and the back up crashes, I have to kill the VZDump process. The NFS server is hosted in the same datacenter as the host, I they are both on the same subnet. They are liked via 1gig link. Not sure if this is the correct way to really have offsite...

What does that option disable? (may be a stupid question, been a long day :P ) *edit http://en.wikipedia.org/wiki/Swappiness Is it safe to set to 0?

In Proxmox 2.3 they implemented a new backup method for KVM which allows snapshots without using LVM. Quote from the Introduction section: Starting with V2.3, a new KVM live backup technology is introduced to Proxmox VE. The old backup system for KVM guests was using LVM snapshots which was...

Yes no change :(

Using KVM so no need of lvm.

6, but my understanding is that Prox goes though them one at a time though, may just stick to local storage and rsync the other backups across :P

Intel Xeon E5-1650 64GB Ram x2 Soft Raid Intel SSD DC S3500 (Most VM's are on) x2 TOSHIBA DT01ACA200 2TB (Backups) LZO compression with snapshot

Anyway to limit this per backup job?

We have this aswell, We use both local storage and NFS storage. Backing up to local slows the VM's down but not hugly, backing up to NFS causes the vms to hang until backup has finished. We are using Prox 3.1

Hello, we are having a issue with backing up to an NFS storage, when ever the backups start it tends to cause the servers to become unresponsive until the back up has finished. Is this normal? (cant see it been normal) Thanks