Search results

I agree with this suggestion. I just went and set --quotaugidlimit to something so vz quotas would work in Plesk.

It may be, but it is an issue that pops up only when beta2's qemu-server starts up kvm with its unique blend of command line options. When beta1's qemu-server starts kvm with its style of kvm command line options, it works fine. It's strange and I can't pinpoint which command line option could...

I hate to argue, but actually I think mine is a different issue than this one you've described. 1) I am running the latest kernel and kvm userland available for the Proxmox VE dist and it is running fine and happy. Only qemu-server changes to fix or break it. 1) I can take the exact same...

I got wrong permissions at first because /var/log/* was omitted from the backup. The directory for postgres's logs is a subdirectory underneath /var/log/ which needs its permissions manually fixed when you first (re)create it so the postgres user can write to the directory. IMHO, I think the...

I used "host.domain.com" in the hostname field and "domain.com" in the DNS search domain field. I find my FreeBSD and Linux machines tend to like it better when the system hostname is set to "host.domain.com" rather than just "host". FreeBSD's sysinstall has always for the last 14 years set...

If the Proxmox guys take an interest in fixing this, perhaps a nice shortcut in figuring out and fixing this problem with beta2's qemu-server might be for me to provide my Win2k .qcow2 (and /etc/qemu-server/XXX.conf) for testing, though it is 6 gigs gzipped.

I just updated from Proxmox VE beta1 to beta2 using the apt-get dist-upgrade method. Everything was fine except my Win2k Server KVM. The FreeBSD 6.3/i386 KVM was perfectly fine and happy, it was just the Win2k server KVM that blew up: So I tried and tried various things to get it running again...

Some admin should change the title of this thread to "vzdump omits /var/log" so it's a little less alarming.

Small error in the initial setup bits for the zenoss template: Postfix sets $myhostname and $mydestination in main.cf to "host.domain.com.domain.com." (with period)

All right, I guess this is on purpose, so it's expected that I do not have anything from /var/log/* From /usr/bin/vzdump: find_add_exclude ('-files', '/var/log/.+'); Postgres started up once I fixed its log permissions and so did apache and the application inside the VZ container seems to work.

Ok, wait a minute, I restarted the restored CTID and postgres came up and I seem to have my data. I confirmed all the same stuff from /var/lib/vz/private/[goodctid] seemed to be there in /var/lib/vz/private/[restoredctid] /var/log/* inside the VZ container seems to be the only thing missing...

To test my vzdump-generated backups I took my latest backup from a couple of hours ago and restored it to a new CTID. I shut down the good working CTID and started up the restored CTID (so I didn't have an IP conflict) and things were missing from the restored copy. /var/log/postgresql was...

You're right, you'll be needing a step to copy whichever qcow2 files you need from /var/lib/vz/images to $ddir/kvm/$dname1 or wherever appropriate for you. Hopefully you can figure out how to write your own simple basic script to lvcreate, mount, copy and/or 7zip or gzip, umount and lvremove...

You probably need to create /backupsnapshot/images also. Do each step of this manually yourself and check the result after each command. If the results aren't as expected, you've found the step that is failing.

Nothing obviously wrong that I can see from a quick glance, it might help to run it manually and see which step fails on you. Your lvcreate line for your snapshot might be too big, try 1g instead of 2g. With the defaults in Proxmox PVE I wasn't able to do a very large LVM snapshot, I had to...

You should, it seems to work well.

Our backup script currently uses the vzdump script with --snapshot to backup VZ containers and then we have another script we wrote to make an LVM snapshot and back up the .qcow2 files from the snapshot. After all that is prepared in a directory on the local server, it's shipped off to the...

# cat /sys/block/sda/queue/scheduler noop anticipatory [deadline] cfq The CFQ scheduler worked incredibly poorly for me and so did the anticipatory scheduler. Which scheduler one uses shouldn't be directly related to LVM snapshots running out of space though...

I don't quite know how 500m worth of changes could be accumulating in under an hour, but apparently that was the case, yes. For at least 3 or 4 nights in a row after ~50 minutes the vzdump would fail out with nasty critical filesystem errors every single time. I upped the snapshot size from...

FYI, I had to edit /usr/bin/vzdump to change $lvcreate --size 500m to $lvcreate --size 2000m. My vzdump was failing multiple days in a row on my Plesk jail. It has about 60 domains in it and about 30G used, nothing really out of the ordinary. 500m just wasn't enough and it failed and started...