One small addition: if someone has an idea how to keep the load down even when clone within the gluster storage domain, any suggestions are welcome and we would test that
From: <users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>> on behalf of Soeren Malchow Date: Wednesday 20 May 2015 00:19 To: "users@ovirt.org<mailto:users@ovirt.org>" Subject: [ovirt-users] Backup through export and clone Dear all, I am no python developer (basically no developer at all) but i struggled with the backup for a while but finally i have a script almost OK for the backup. Due to the fact that the “snapshot -> export” feature is coming as it seems in 3.6 we still need to clone and then export. This script is threaded to do backups of 3 Vms concurrently, however, in our setup ( compute server with 3 separate gluster machines) parallel backups of 3 VMS create very heavy load on the gluster storage servers, and i would like to do the “clone snapshot” to a separate intermediate storage already, can anybody help me with that ? (somewhere around line 70) The cloning can hopefully go away in September with 3.6 but until then we still need that. Any other improvements are more than welcome – please keep in mind i am not a developer and I only tried my very best to write a decent script. Also: do we have a place (git repo or so) where we can put this script for everybody ? I am pretty sure there is more than one person out there looking for something like that (at least i hope :-) ) Regards Soeren
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
