<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<br>Truck replication page: http://www.drbd.org/users-guide/users-guide.html <br>For dump /restore part: http://www.drbd.org/users-guide/s-resizing.html <br><br>What I am trying to achieve:<br>~~~~~~~~~~~~~~~~~~<br>I have 2 node setup (primary/secondary), each node have ~4TB disk, and rest of the hardware configuration is exactly the same. I want this setup so that in a fail over scenario where secondary can be promoted to primary. I am using Truck replication because I want to avoid initial sync time, which in our case takes more than 12hrs.<br><br>> > takes place. Any idea what could be causing this,<br>> You ;)<br>Glad if this is the case :)<br><br>Basically, steps that I mentioned earlier were for secondary node only. <br><br>> > drbdadm detach res<br>> why?<br>Because if resource is attached we cannot restore metadata (metadata dump from primary) .<br><br>> > ${drbdmeta_cmd/dump-md/restore-md} /var/testmeta<br>> <br>> why?<br>Basically it is delivering "drbdmeta 1 v08 /dev/sdb3 internal restore-md /var/testmeta" command to restore meta on this secondary node (sorry for including extra bash commands). So the idea is that when both nodes connect they are UpToDate/UpToDate.<br><br>Let me know if there is something wrong with this approach.<br><br><br>Thanks much,<br>Jay<br><br><br>> Date: Tue, 10 Nov 2009 16:10:44 +0100<br>> From: lars.ellenberg@linbit.com<br>> To: drbd-user@lists.linbit.com<br>> Subject: Re: [DRBD-user] Truck replication<br>> <br>> On Mon, Nov 09, 2009 at 10:26:07PM +0000, jay b wrote:<br>> > <br>> > <br>> > Hi All:<br>> > <br>> > I am hitting a strange behavior during truck replication (so far it<br>> > has occurred to one machine out of 10). I have two machines node1 and<br>> > node2, and I am restoring metadata on node2. Whenever I do the<br>> > following (as mentioned on truck replication page) resynchronization<br>> > takes place. Any idea what could be causing this,<br>> <br>> You ;)<br>> <br>> > any clues to debug such issues? <br>> > <br>> > drbdsetup 1 new-current-uuid --clear-bitmap<br>> <br>> fine.<br>> <br>> > drbdadm detach res<br>> <br>> why?<br>> <br>> > drbdmeta_cmd=$(drbdadm -d dump-md res)<br>> <br>> why?<br>> <br>> > drbdadm detach res <br>> <br>> why?<br>> <br>> > ${drbdmeta_cmd/dump-md/restore-md} /var/testmeta<br>> <br>> why?<br>> <br>> <br>> May I ask<br>> * what are you trying to achieve?<br>> * which "truck replication page" are you referring to?<br>> <br>> -- <br>> : Lars Ellenberg<br>> : LINBIT | Your Way to High Availability<br>> : DRBD/HA support and consulting http://www.linbit.com<br>> <br>> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>> __<br>> please don't Cc me, but send to list -- I'm subscribed<br>> _______________________________________________<br>> drbd-user mailing list<br>> drbd-user@lists.linbit.com<br>> http://lists.linbit.com/mailman/listinfo/drbd-user<br> <br /><hr />Windows Live: Make it easier for your friends to see <a href='http://go.microsoft.com/?linkid=9691811' target='_new'>what you’re up to on Facebook.</a></body>
</html>