From: Francesco Morosinotto <jlord87@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: are btrfs snapshot helpful for backing up kvm qcow2 vm?
Date: Thu, 06 Nov 2014 16:02:22 +0100 [thread overview]
Message-ID: <545B8D7E.6060606@gmail.com> (raw)
Hi guys,
I need to improve the backup strategy of my vms; At the moment I backup the machines once a week by stopping them, making a snapshot, exporting the xml descriptor file and backing up these files.
I would prefer a daily online backup solution that allows me to take a snapshot with a minimum downtime.
That's why I was planning to switch from etx4 to btrfs;
my project will be to pause the vm, dump the memory and the xml descriptor file, make a snapshot of the subvolume storing the qcow2 file and after that resuming the machine.
does this project makes any sense? What about performance? Am I going to experience bad performance having qcow2 over btrfs?
I read on some old (two years) posts that btrfs was having bad fragmentation when dealing with qcow2 files, is this still happening?
Thank you
Francesco
next reply other threads:[~2014-11-06 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:02 Francesco Morosinotto [this message]
2014-11-06 19:57 ` are btrfs snapshot helpful for backing up kvm qcow2 vm? Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545B8D7E.6060606@gmail.com \
--to=jlord87@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.