Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> -----Original Message----- > From: Felix Frank [mailto:ff at mpexnet.de] > Sent: Monday, July 25, 2011 12:36 AM > > Hi, > > On 07/23/2011 05:55 AM, Robinson, Eric wrote: > > Is anyone up late on a Saturday night who can tell me if > there are any > > caveats or gotchas I should be aware of when upgrading from > drbd 8.3.2 > > to 8.3.8? > > I think it speaks for the admin crowd that we didn't ;) > > > I have two RHEL 5.5 servers running drbd 8.3.2 built from source. > > > > My plan is to: > > > > shut down high availability services on the secondary server > > shut down drbd on the secondary server > > build the new drbd and kmod-drbd > > start the new drbd > > start high availability services > > trigger a failover (secondary now becomes primary) > > repeat the same process on the old primary > > This should work fine. > > > Are there any incompatibilities between 8.3.2 and 8.3.8 > that might get > > in the way? Does it matter whether I am using internal or external > > metadata? (I think I am using internal, but how do I tell for sure?) > > drbdadm dump > > No, it doesn't really matter wrt. your update. > > Cheers, > Felix > Thanks, Felix. Actually, I figured nobody answered my questions because there were dumb. Classic RTFM stuff. If I had perused the DRBD user guide, I would have seen that all versions of 8.x are protocol compatible and that rolling upgrades are possible. Also, if I had simply read my drbd.conf file, I would have seen that internal metadata is specififed. My bad. --Eric Disclaimer - July 25, 2011 This email and any files transmitted with it are confidential and intended solely for Felix Frank,drbd-user at lists.linbit.com. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/