[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] migration and snapshots.


  • To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: J Nb <j_nwb@xxxxxxxxx>
  • Date: Wed, 30 Dec 2009 10:54:47 -0800 (PST)
  • Delivery-date: Wed, 30 Dec 2009 10:59:19 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=C5wfnQ/YknODrI2bre5cpg1vayHYJuh901hCV1oudgG6BCcqbLNHF8iQL9R7V1UTjTSZbn4uSR6i0ShLqKhDS6dYaP9vW81WLEVB3XRTuyNfqAKAIFEvtBQNDy+faZYS+O+e+53y4gXXzaAg5aRJHvWztPdCLKCrxKFex32lHRs=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

What would be a good storage topology for allowing for migration as well as 
support snapshots (for backup)

Would love to hear recommendations as well as details on setup that people are 
using. (I am assuming that this is possible.)

Here is my current understanding..

LVM -- Snapshots but not shared.
CLVM -- shared but no snapshots. (yet)
NFS/GFS -- Shared FS but no snapshots 


qcow2 files and VHD file supports snapshots... but VHD is not yet available in 
Xen or KVM.

qcow2 : are people using this in production ? Any limitations.. any success 
stories ?

qcow2 takes snapshots within the disk it self... how can I get the snapshot out 
for backup ?

-nb



      


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.