Ok, I found a way to only use ssh.
I can create the lun with a small perl script (5lines of code) on the proxmox
server side.
Question :
I would like to avoid to put this script on nexenta box.
Is it possible to send script content through ssh and execute it with perl ?
(maybe some pipe
you need to mount the snapshot, then backup the VM image instead.
Oh, ignore me, your test is also valid.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Guest was debian wheezy, the OS disk was not used for testing and marked as
no backup.
The 2nd disk used for testing backups was 32GB, virtio cache=none I filled
that
disk with data from /dev/urandom before performing any backup tests
You said LVM backup take only 58 secs?
32000MB/58sec =
I have not tested writes yet and doubt I will have time to get to that this
week.
To show drawbacks of LVM snapshots, you can use something like:
# dd if=/dev/urandom of=tmp.raw bs=1M
inside the VM during backup.
LVM snapshot will most likely run full, and is very slow:
# time vmtar
I have identified one use-case where KVM Live Backup causes a significant
decrease in IO read performance.
Start a KVM Live Backup
Inside the VM immediately run:
dd if=/dev/disk_being_backed_up of=/dev/null bs=1M count=8192
Repeated same test but used LVM snapshot and vmtar:
lvcreate
Thanks.
I found another way, just need to escape strings correctly.
I'll try to send a patch for tomorrow
- Mail original -
De: Stefan Priebe - Profihost AG s.pri...@profihost.ag
À: Alexandre DERUMIER aderum...@odiso.com, Dietmar Maurer
diet...@proxmox.com, Michael Rasmussen
I am unable to reproduce that - for me LVM and Live backup are about the same
speed.
Can you see the effect if you dump backup output directly to /dev/null?
# /usr/lib/qemu-server/vmtar '/etc/pve/qemu-server/108.conf' 'qemu-server.conf'
'/dev/vmdisks/test-snapshot' 'vm-disk'/dev/null
#
Hello,
We've noticed a bug in the Proxmox API - it is possible to create a
storage with a dot . in it, but once created, it is not possible to
set ACLs on it.
Please find a patch to correct this problem.
Thank you in advance.
Jort
--
Jort Bloem
Technical Engineer - Auckland
Business
We've noticed a bug in the Proxmox API - it is possible to create a storage
with a
dot . in it, but once created, it is not possible to set ACLs on it.
Please find a patch to correct this problem.
Thanks for the report. I applied a similar patch here:
Hi, this is because with new backup,
each new write in the vm during the backup, is copied to backup storage and to
the vm.
So, if you have a slow storage, the write to the vm is a the same speed than
the backup storage.
This occur only once by block, be doing a full rewrite of the vm disk is
Ok,I'll try to look at it next week.
(we can remove my qemu-img-convert-skipcreate-option.patch, now in qemu
git :)
http://git.qemu.org/?p=qemu.git;a=commit;h=b2e10493c71160d88bb823cae9a
92e806a79b9d6
)
I'll begin to work on simple patches
I plan to start working on that now - do you
Hi, this is because with new backup,
each new write in the vm during the backup, is copied to backup storage and to
the vm.
The tests form Eric only do reads (there is no single write involved).
___
pve-devel mailing list
pve-devel@pve.proxmox.com
The tests form Eric only do reads (there is no single write involved).
Oh, I miss that.
I think it should be a qemu problem, as only difference is that
with lvm snapshot backup,
backup reads are done directly from disk
and with qemu backup
reads are done through qemu
Maybe qemu has more
The tests form Eric only do reads (there is no single write involved).
Oh, I miss that.
I think it should be a qemu problem, as only difference is that
with lvm snapshot backup,
backup reads are done directly from disk
and with qemu backup
reads are done through qemu
Maybe qemu has more
The tests form Eric only do reads (there is no single write involved).
Oh, I miss that.
I think it should be a qemu problem, as only difference is that
with lvm snapshot backup,
backup reads are done directly from disk
and with qemu backup
reads are done through qemu
Maybe
15 matches
Mail list logo
