[DRBD-user] Initial sync, just want to confirm the process (and not go down in a blaze of glory)

adamn at eyemedia.com.au adamn at eyemedia.com.au
Fri Aug 13 01:39:37 CEST 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

Hmm sorry Dan, but this has left me a little confused.
As I said in my first post, storage00 is LIVE and has around 4TB of data 
on it, I have a dedicated gigabit NIC for drbd, (the machine has 6 network 
cards in it, 4 for MPIO iSCSI, 1 for managment/heartbeat, 1 for DRBD)
I have already setup storage01 and have issued drbdadm create-md meta and 
drbdadm create-md data on the secondary machine, I haven't started drbd on 
it as it needs to be rebooted first, hence why I'm now a little cautious 
on the reboot of the machine.

Adam Niedzwiedzki

"Dan Barker" <dbarker at visioncomm.net>
<drbd-user at lists.linbit.com>
12/08/2010 10:31 PM
Re: [DRBD-user] Initial sync,   just want to confirm the process (and not 
go down in a blaze of   glory)
Sent by:
drbd-user-bounces at lists.linbit.com

> <snip>
> Now I need to reboot here, (due to the LVM module), now my gut is 
> saying it should all be ok, but of course drbd is going to fire up 
> on reboot, what is my process from here? 
> Will it be ok for the reboot, see as this will be the first time 
> drbd starts on the secondary and connects to the primary?

Nothing bad will happen. Until/If you create the metadata on storage01, 
will ignore the disk resource. From there, you are just replacing a disk, 
in the doc:

nal-metadata. When you attach the resource, the sync will start _and_ it
will start in the direction you desire.

You may want to create a tiny (few hundred M) resource and go through the
steps on it for your own comfort. I set up my entire drbd configuration on 
couple of virtual machines before I lit mine for real - and I use them 
to answer the "what if xxx happens" questions.

Add the definitions to both configuration files. Do the create-md, attach,
connect, mount, mkfs on storage00 and put some data on it. When you do the
create-md on storage01, the sync will automatically start and whatever
you've put on it using storage00 will copy over. Verify by taking down the
resource on storage01 and mounting the device locally.

You have the entire wire allowed for sync. This will impact live 
If the devices are all idle, fine. If the primary is expecting to get
anything done while the sync takes place, then throttle that back a bit
(actually, a lot). You can temporarily override the syncher speed in an
emergency situation, but for normal use maybe 35M would make more sense.
Remember, drbd will be running fine during the sync, even if dual-primary!
Leave some room for drbd non-sync use of the wire.

Command that speeds up sync but doesn't flummox the config files:
   drbdsetup /dev/drbd<minor> syncer -r 110M

Dan in Atlanta

drbd-user mailing list
drbd-user at lists.linbit.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100813/3482c0a3/attachment.htm>

More information about the drbd-user mailing list