Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Re: [DRBD-user] Preventing initial full sync on new installLars: Is this true with all protocol versions (i.e. A, B, C)? And is this true on earlier versions of drbd (i.e. prior to 8.x)? Ron Blechman | Distinguished Member of Technical Staff | Avaya | 307 Middletown Lincroft Road | Room 3K-305 | Lincroft, NJ 07738 | Voice 732.852.2310 | Fax 732.852.1375 | rblechman at avaya.com ----- Original Message ----- From: Lars Ellenberg To: drbd-user at lists.linbit.com Sent: Saturday, November 24, 2007 1:31 PM Subject: Re: [DRBD-user] Preventing initial full sync on new install On Thu, Nov 22, 2007 at 06:00:32PM +0100, Christophe Boyanique wrote: > > Hello, > > I will have to convert a cluster from external bay sharing to DRBD > duplication and the main concern of the client is to reduce the outage > as services are in production. > > The documentation states: > > You choose which node shall become Primary for the first time (the one > with the good data, if you have some), then you do drbdadm -- > --overwrite-data-of-peer primary all. The result is a full > synchronization of the underlying devices (we call this the initial full > sync). > The device is usable right away, so if you have no file system already, > you should create one now. > > > My question is; will the device be usable right away during the initial > full sync or will it be blocked ? as you quoted above, and as Stefan Seifert pointed out, the device _is_ usable right away. > If the device is not accessible; what is the purpose of this full sync what is the purpose of the initial sync of a raid1 device? > as, anyway, the device will be formated right away after the full sync ? if you have existing data, you'd not want to format it away. > Is there a way to avoid this initial full sync or to reduce the duration ? yes. but you should not. especially in your case, what I'd do is: unplug that external bay from one of the nodes. attach some new storage to that node. configure drbd with external meta data to use the existing data on the node that still sees it, make it primary there, and start your services. then start drbd on the node with the newly attached storage, and let it sync up. now, understand and configure heartbeat. -- : commercial DRBD/HA support and consulting: sales at linbit.com : : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client. _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20071126/1f0393cf/attachment.htm>