Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
You do not need to create new metadata, according to this guide:
http://www.drbd.org/users-guide/s-upgrading-drbd.html
Mit freundlichen Grüßen / Best Regards
Robert Köppl
Customer Support & Projects
Teamleader IT Support
KNAPP Systemintegration GmbH
Waltenbachstraße 9
8700 Leoben, Austria
Phone: +43 3842 805-322
Fax: +43 3842 82930-500
robert.koeppl at knapp.com
www.KNAPP.com
Commercial register number: FN 138870x
Commercial register court: Leoben
The information in this e-mail (including any attachment) is confidential
and intended to be for the use of the addressee(s) only. If you have
received the e-mail by mistake, any disclosure, copy, distribution or use
of the contents of the e-mail is prohibited, and you must delete the e-mail
from your system. As e-mail can be changed electronically KNAPP assumes no
responsibility for any alteration to this e-mail or its attachments. KNAPP
has taken every reasonable precaution to ensure that any attachment to this
e-mail has been swept for virus. However, KNAPP does not accept any
liability for damage sustained as a result of such attachment being virus
infected and strongly recommend that you carry out your own virus check
before opening any attachment.
vijay patel
<catchvjay at hotmai
l.com> An
"Robert.Koeppl at knapp.com"
29.10.2013 16:02 <robert.koeppl at knapp.com>,
"drbd-user at lists.linbit.com"
<drbd-user at lists.linbit.com>,
Kopie
Thema
RE: Antwort: Re: [DRBD-user] DRBD
8.3.13 Sync getting stalled with
RHEL 6
Thanks Bob for your reply. While upgrading drbd (removing 8.3.13 and
installing 8.4.2) when I recreate meta data (drbdadm create-md) will it
affect data on the disk?
> Subject: Antwort: Re: [DRBD-user] DRBD 8.3.13 Sync getting stalled with
RHEL 6
> To: drbd-user at lists.linbit.com
> CC: catchvjay at hotmail.com
> From: Robert.Koeppl at knapp.com
> Date: Fri, 25 Oct 2013 10:32:08 +0200
>
> If you can live with a short downtime the path is rather simple:
> Stop your cluster software on the secondary, upgrade there bit leave
> DRBD/clustersoftware stopped.
> Stop your cluster on the primary node
> Update DRBD
> Start your cluster up again on primary node.
> After the primary is fully up again you have two options:
> 1. start your cluster software on the secondary and let it take care of
> starting DRBD/sync
> 2. more paranoid:
> 2.a disconnect ddrbd on primary: drbdadm disconnect all
> 2.b load drbd module on secondary: modprobe drbd
> 2.c bring up resources on secondary node: drbdadm up all
> 2.d invalidate data on secondary: drbdadm invalidate all
> 2.e connect primary again: drbdadm connect all
> This will trigger a resync. after it is done, stop drbd and start your
> cluster manager on the secondary node
> Mit freundlichen Grüßen / Best Regards
>
> Robert Köppl
>
> Customer Support & Projects
> Teamleader IT Support
>
> KNAPP Systemintegration GmbH
> Waltenbachstraße 9
> 8700 Leoben, Austria
> Phone: +43 3842 805-322
> Fax: +43 3842 82930-500
> robert.koeppl at knapp.com
> www.KNAPP.com
>
> Commercial register number: FN 138870x
> Commercial register court: Leoben
>
> The information in this e-mail (including any attachment) is confidential
> and intended to be for the use of the addressee(s) only. If you have
> received the e-mail by mistake, any disclosure, copy, distribution or use
> of the contents of the e-mail is prohibited, and you must delete the
e-mail
> from your system. As e-mail can be changed electronically KNAPP assumes
no
> responsibility for any alteration to this e-mail or its attachments.
KNAPP
> has taken every reasonable precaution to ensure that any attachment to
this
> e-mail has been swept for virus. However, KNAPP does not accept any
> liability for damage sustained as a result of such attachment being virus
> infected and strongly recommend that you carry out your own virus check
> before opening any attachment.
>