Search results

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ So, I've done some testing on RAID1 backed ssd on a production system. It seems to indicate that without a writeback cache the restore performance is significantly slower (50%). RAID1 SSD Write Back sdb...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ Tom, wether using gz or lzo this is entirely cpu related. I understand lzo uses less cpu - there is no cpu limitation here, this is a disk write performance limitation. Using gz in fact should assure a...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ Yeah very true, forgot about your network but in my case backups are generally compressed 2-300% and so the source can still be only 100MB/s and restore could in theory occur at 2-300MB/s. Have you done a...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ Re chrome - I dunno, I get this: "Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data." IE is OK and so is firefox (and I'm not the only one...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ There is no raid controller in use except for the installation, this is an i5, 16GB test box and I'm writing direct to sata connected hard disks to eliminate any raid performance impacts. CPU BOGOMIPS...

Wow yeah that fixed it. This was just a default setting for my account mind you, so this might be a very widespread problem. For anybody else, I found it in 'Forum Actions' -> 'Thread Display Options'

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ oh I just did a test with ext2; Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sdc 0.00 2.00 0.00 413.00 0.00 5702.40...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ There is nothing running on the drives. Since clearly there is a problem with the setup and I imagine in development devs at least once ran a restore and it went at some sort of acceptable speed I tested on...

I get this: HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfil the request. When trying to view my own thread. It did this when I first posted a thread and whenever I return to the thread - - - Updated - - - This one is...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ restore vma archive: zcat /mnt/ntfs/dump/vzdump-qemu-102-2013_05_09-22_21_32.vma.gz|vma extract -v -r /var/tmp/vzdumptmp3288.fifo - /var/tmp/vzdumptmp3288 CFG: size: 557 name: qemu-server.conf DEV: dev_id=1...

Re: Super slow vma backup restore - about 1.5MB/s with drives that will copy at 90MB/ I'm restoring a backup. On the same hardware restore used to be slow with the old LVM snapshot backups but much faster than this (15-20MB/s). It's not ten times slower at least. I'm showing disk stats...

As the subject. Reading from disk at 3-700KB/s, destination maxed out at 1.5MB/s. When doing a straight copy it will do 90MB/s happily with same source and destination drives. This is really, really broken. Not sure what the point of a backup is if it will take three days to restore. - - -...

Yeah it kinda does help - my VM id is 106, I looked in /var/lib/vz/root/106 (which was there) and it was completely empty. This is the log of the creation. Creating container private area (/var/lib/vz/template/cache/centos-6-standard_6.3-1_amd64.tar.gz) Performing postcreate actions CT...

Nobody? They are both the 6.3-1 image, one was downloaded straight from the proxmox interface. I'm not really sure how CT's should work but I'd expect to see the CT in console at least go to a login screen... I've also done the full update via command line after posting this, no change

I've tried both 32 and 64 bit images, the 32 bit I even downloaded using the web interface. It says 'Starting udev: [ OK ]' and then hangs with the square at the next line :( Nothing special about this setup, just a plain disc install with local raid

Can I just +1 how much I want this in the current version - I've just tested this and its covered most of my backup woes - backups that were going 40-60mb/s with lzo are now full backup destination speed (110 mb/s) - this now makes the backups run faster than without compression, awesome. All...

Your restores are slower than mine - what is the usual file copy speed from your source? Have you looked in processes to see if there are two lzop processes working? This is what I've seen, and I've read lzop isn't multithreaded so I don't know what this extra process is doing but I expect its...

Oh also - and maybe this is just a FYI for the devs but it's worth mentioning - I had a vmdk in one server that was preallocated. The drive worked fine, however the backup didn't backup the actual vmdk data file - only the reference/config vmdk file. If anyone else is doing this be careful -...

I've only ever used proxmox 2.2 using a 2.2 install disk. This is a 2.2 backup. I've done the upgrade, will test it again. Here is the log of a large (380GB) server restore - only the very last file (35gb) recovered at a reasonable speed of 80MB/s - the others (except the one that was...

Oh, and also there is an error in the log - I saw it before but thought it was a once off, perhaps it's not... "tar: write error" extracting archive '/mnt/tmp/dump/vzdump-qemu-101-2013_01_09-13_23_02.tar.lzo' extracting 'qemu-server.conf' from archive extracting 'vm-disk-ide0.vmdk' from archive...