Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jan 18, 2011 at 07:58:49AM +0100, Felix Frank wrote: > On 01/18/2011 12:45 AM, Cameron Smith wrote: > >Well looking further online it seems the two versions are compatible! > >Can anybody here confirm that please? > > > >Now my main two questions are: > > > >1) Will having different size partitions between nodes cause an issue? > >(my meta-data is on a separate partition and not set as internal) > > Yes, that's a problem. Your initial SyncTarget must be the same size at least as big is supposed to be enough. > as your original DRBD. You can then resize that partition by > whatever means necessary, then resize the DRBD itself. Note that the > last step should not be performed before you have resized both your > nodes' partitions. > > >2) After bringing up my resource on the new node do I then run: > > > >*|drbdadm -- --overwrite-data-of-peer primary/|resource|/|* > > > >ON THE OLD PRIMARY NODE? This is where the data is live and the /data partition is mounted. > > > >I want to make sure I don't kill my live site and it's data!!! :) > > Seeing as your old node is already primary, you will more likely > want to connect --discard-my-data on the other one. But your general > idea is sound. If that new node was "just created" (... create-md ...), then there is no need for any of that. But just to feel better, it may help knowing that DRBD will refuse to become synctarget if it is currently primary, so if you want something to not become synctarget, it is usually good enough to just keep it primary. Besides, for all things cluster upgrade, you could (probably: should) just do a "dry run" in some VMs at least, if you don't have an actual test cluster. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed