Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello, thank you for the replies. To summarize the question even more: - Two servers are DRDB 8.0.16 and sync data, on CentOS 5. - Only the secondary will be upgraded 8.4 on CentOS 6. Can the secondary 8.4 still sync (and get its data updated) *safely* from the 8.0.16 one, using the same protocol C? (note: 8.0.16 will always be primary until it crashes or/and is later upgraded as well to 8.4) Thank you. Regards Yves On Fri, Mar 13, 2015 at 5:37 PM, Prater, James K. <jprater at draper.com> wrote: > Hello Yves, > > I would really check with or at least wait for Lars from Linbit to > respond. At first glance, I would update "B" so you can do some initial > testing. Since you may have some issues re compiling components. Then allow > the normal transactions to occur from "A" by connecting it to the primary. > The update DRDB on "A". You should not require the data to be invalidated. > We are still talking about release "8.x". It should be backwards compatible. > > James > > *From*: yves [mailto:user at kochira.com] > *Sent*: Thursday, March 12, 2015 10:45 AM > *To*: drbd-user at lists.linbit.com <drbd-user at lists.linbit.com> > *Subject*: [DRBD-user] Sync two different versions of DRBD > > Hello, > > two servers A (primary) and B (secondary), are each using DRBD 8.0.16 > via protocol C. > > Since only one can be migrated to 8.4 at a time, is it possible to > > - keep unchanged A (8.0.16) > - install 8.4 on B (similar config with protocol C) > - invalidate B data (created from 8.0.16) > - sync A -> B > > and keep this for a few days. > > Does it safely work? > > Thank you and regards, > > Yves > ------------------------------ > Notice: This email and any attachments may contain proprietary (Draper > non-public) and/or export-controlled information of Draper Laboratory. If > you are not the intended recipient of this email, please immediately notify > the sender by replying to this email and immediately destroy all copies of > this email. > ------------------------------ > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20150316/0d624b3b/attachment.htm>