This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] question to DRBD users/experts

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] question to DRBD users/experts
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Tue, 24 Aug 2010 16:07:39 -0400
Delivery-date: Tue, 24 Aug 2010 13:10:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
We're looking at using xen on SLES11SP1 servers in production at remote
sites. We've been testing ocfs2 over dual primary drbd as one of the
storage choices. It runs great, and is certainly more cost affective
than putting SANs at our sites. 

Our big concern is split brain and how to handle that when it happens.
If you have a large, shared storage over drbd with VMs running on either
host, how do you handle a split brain situation from a recovery

One idea we had is to run multiple ocfs2/drbd's, one for each VM, and we
can pick and choose which way to recover in a split brain. That seems
like it makes it a lot more complex and not sure how successful it would
even be. 

Are others using drbd in production? 
What has been your experience?

Any suggestions are appreciated. Our company standard is SLES, so we
have to use tools in that distro. 


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>