Recent content by dan

Hello Dietmar, thanks for your reply. Actually it is getting worse over time. This is a log from the end of september: 100: Sep 29 03:00:01 INFO: Starting Backup of VM 100 (openvz)100: Sep 29 03:00:01 INFO: CTID 100 exist mounted running 100: Sep 29 03:00:01 INFO: status = running 100: Sep 29...

Hi, I have discovered some strange behaviour of the backup process. The backup of VM 100 is very fast (23MiB/s) but VM 101 takes like forever (530KiB/s). Why is there such a great difference in the backup speed? 100: Oct 20 03:00:01 INFO: Starting Backup of VM 100 (openvz) 100: Oct 20 03:00:01...

I have the same problem. Did you find any solution yet?

I just tried to upgrade to the latest version of proxmox from 2.0 stable and getting an error: What is going on? Why can't the new kernel not be installed? Thanks a lot for any help.

Good to know. Thanks a lot.

Re: Backup fail Thanks so much for your replies. With this great tutorial I've managed to reduce the size of my backup partition to make some room for the snapshots. So I guess the free space must be at least the size of your biggest VM?

Hi e100, thanks for your reply. pvscan PV /dev/md1 VG vg0 lvm2 [1.36 TiB / 0 free] Total: 1 [1.36 TiB] / in use: 1 [1.36 TiB] / in no VG: 0 [0 ] Why does the volume group vg0 needs free space? Why isn't Proxmox using the /backup partition?

Snapshot backups will fail if volume group has no free space Hi, when I try to make backups of my VMs I'll always get this error: INFO: starting new backup job: vzdump 102 --remove 0 --mode snapshot --compress gzip --storage backup --node host INFO: Starting Backup of VM 102 (openvz) INFO...

suspending works but I would rather like to use the snapshot mode... Is this a bug or a miss configuration on my part?

I had to change the ip in my.cfg to 127.0.0.2 to make mysql start again. But I don't like this workaround.

Thanks for your reply. I'm getting the same error:

I've tried to start the backup process of a VM manually but getting the following error message: If I check the free space on the host machine, there seems to be sufficient space left. The backup space its mounted on /backup. What I'm doing wrong? Thanks for any help.

Hi, I've just upgraded to Version 2.0-18/16283a5a. After restarting my VM Apache and MySQL won't come up. So I checked /etc/network/interfaces and saw that the loopback address was automatically set to 127.0.0.2. Why is that? How can I change it back to 127.0.0.1? Thanks a lot.

Hi Dietmar, thanks a lot. Changing /etc/hostname to "pve" did it. Is this intended? Beta 2 did not have any problems with a custom hostname. Anyway, it is working fine now.

Hi Dietmar, thanks a lot for your support. Can I send you the account data, that you can check for yourself? If yes, where can I send it to? The hosts and hostname seems to be right though: #/etc/hosts 127.0.0.1 localhost <ip address> pve # # IPv6 ::1 ip6-localhost ip6-loopback fe00::0...