So the slave will catch up afterwards. Excellent. Thanks
On Tue, Sep 24, 2013 at 5:19 PM, Dan Barker <[email protected]> wrote: > Wow! Those are some old versions!**** > > ** ** > > Just “drbdadm disconnect all” on the Primary node before the maintenance > and “drbdadm connect all” afterwards. All else is magic!**** > > ** ** > > Dan**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Gabriel Sosa > *Sent:* Tuesday, September 24, 2013 11:08 AM > *To:* [email protected] > *Subject:* [DRBD-user] Fwd: how to place secondary node in maintenance > mode**** > > ** ** > > We have a pretty standard setup**** > > MASTER <---> SLAVE (STANDBY) > **** > > ** ** > > both nodes are in sync without much issue now but during this week our DC > will perform some maintenance tasks that might incur in some connectivity > issues between both nodes.**** > > How can put the slave node in maintenance (or any other mode) in order to > avoid any split brain situation?**** > > I've been reading [1] and [2] but I can't find a clear answer to this.**** > > should I just take down the service on the SLAVE node performing a > *service drbd stop* or instead disable the resource using *drbdadm down > resourcename***** > > ** ** > > versions:**** > > MASTER -> version: 8.0.16 (api:86/proto:86)**** > > SLAVE -> version: 8.3.15 (api:88/proto:86-97)**** > > Thanks**** > > > [1] http://www.drbd.org/users-guide/ch-admin.html > [2] http://www.geekpeek.net/drbd-management-command-usage/**** > > ** ** > > > -- > Gabriel Sosa > Sometimes the questions are complicated and the answers are simple. -- Dr. > Seuss ** ** > > _______________________________________________ > drbd-user mailing list > [email protected] > http://lists.linbit.com/mailman/listinfo/drbd-user > > -- Gabriel Sosa Sometimes the questions are complicated and the answers are simple. -- Dr. Seuss
_______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
