|Main Archive Page > Month Archives > drbd-user archives|
On Thu, Mar 11, 2010 at 12:48 PM, Cameron Smith
> On Thu, Mar 11, 2010 at 10:25 AM, Brian R. Hellman
> <firstname.lastname@example.org> wrote:
>> Cameron Smith wrote:
>>> I am preparing for my first deployment of DRBD and have a few
>>> My initial setup is two servers. One is a functioning server and
>>> be the primary and the second is currently not used and will be my
>>> The DRBD instructions say:
>>> "After you have installed DRBD, you must set aside a roughly
>>> identically sized storage area on both cluster nodes. This will
>>> the lower-level device for your DRBD resource."
>>> What is this storage area for?
>> This is where the data you want replicated will go. So if you have
>> /dev/sdb as the block device you want to replicate, you will need a
>> block device of the same size on your secondary to replicate to.
>>> How big does it need to be?
>> However big you want it :)
>>> Is this just where DRBD keeps it's own data to function or is this
>>> where the actual replicated source data needs to be and where the
>>> destination will go?
>>> drbd-user mailing list
>> LINBIT - Your Way to High Availability
>> 7959 SW Cirrus Dr.
>> Beaverton, OR 97008
>> drbd-user mailing list
> Thanks Brian!
> So I don't need to do anything on the primary and I can use the
> existing device where the data lives now as the lower-level location?
> I know about the internal meta data at the end and allowing for it.
> So for my secondary can I do the same with that? It has an existing OS
> and different files in /etc than the primary and I want to make it
> identical to the primary so in case of the primary failing the
> secondary would become a live system identical to the primary.
> How do I achieve this?
> How do I remove the files from the secondary and populate the
> secondary with matching data from the primary?
Also is /dev/mapper/VolGroup01-LogVol00 the appropriate
drbd-user mailing list