willi.fehler at t-online
May 20, 2012, 5:54 AM
Views: 463
Permalink
|
Hi all,
I would like to upgrade my cluster to DRBD-8.4.1. Currently my cluster
is using DRBD-8.3.12 on CentOS-6.2.
I've already read the Linbit Guide for upgrading DRBD
http://www.drbd.org/users-guide/s-upgrading-drbd.html.
I'm using DRBD packages from the ELRepo repository.
#
kmod-drbd83-8.3.12-2.el6.elrepo.x86_64
drbd83-utils-8.3.12-1.el6.elrepo.x86_64
#
/etc/drbd.conf
# You can find an example in /usr/share/doc/drbd.../drbd.conf.example
include "drbd.d/global_common.conf";
include "drbd.d/*.res";
resource r0 {
on server1.local {
address 10.10.10.1:7788;
device /dev/drbd0;
disk /dev/vg00/lv02;
meta-disk internal;
}
on server2.local {
address 10.10.10.2:7788;
device /dev/drbd0;
disk /dev/vg00/lv02;
meta-disk internal;
}
}
resource r1 {
on server1.local {
address 10.10.10.1:7789;
device /dev/drbd1;
disk /dev/vg00/lv03;
meta-disk internal;
}
on server2.local {
address 10.10.10.2:7789;
device /dev/drbd1;
disk /dev/vg00/lv03;
meta-disk internal;
}
}
#
/etc/drbd.d/global_common.conf
global {
usage-count yes;
# minor-count dialog-refresh disable-ip-verification
}
common {
protocol C;
handlers {
pri-on-incon-degr
"/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
pri-lost-after-sb
"/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger
; halt -f";
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
split-brain "/usr/lib/drbd/notify-split-brain.sh root";
# out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root";
# before-resync-target
"/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k";
# after-resync-target
/usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}
startup {
# wfc-timeout degr-wfc-timeout outdated-wfc-timeout
wait-after-sb
# wfc-timeout 0;
# degr-wfc-timeout 120;
}
disk {
# on-io-error fencing use-bmbv no-disk-barrier
no-disk-flushes
# no-disk-drain no-md-flushes max-bio-bvecs
on-io-error detach;
no-disk-flushes;
no-md-flushes;
no-disk-barrier;
fencing resource-only;
}
net {
# sndbuf-size rcvbuf-size timeout connect-int ping-int
ping-timeout max-buffers
# max-epoch-size ko-count allow-two-primaries
cram-hmac-alg shared-secret
# after-sb-0pri after-sb-1pri after-sb-2pri
data-integrity-alg no-tcp-cork
max-buffers 8000;
max-epoch-size 8000;
unplug-watermark 128;
sndbuf-size 0;
rcvbuf-size 0;
ko-count 6;
}
syncer {
# rate after al-extents use-rle cpu-mask verify-alg
csums-alg
rate 30M;
c-plan-ahead 10;
c-fill-target 4M;
c-max-rate 70M;
c-min-rate 4M;
al-extents 1009;
}
}
The ELRepo repository is proving DRBD packages for 8.4. Can I just
uninstall DRBD on the secondary node, than install DRBD-8.4 and than do
a failover and upgrade the primary node? Will my configuration work?
(/etc/drbd.conf, /etc/drbd.d/global_common.conf)
===================================================== N/S Matched: drbd
======================================================
drbd83-utils.x86_64 : Management utilities for DRBD %{version}
drbd84-utils.x86_64 : Management utilities for DRBD
drbdlinks.noarch : A program for managing links into a DRBD shared partition
kmod-drbd83.x86_64 : drbd83 kernel module(s)
kmod-drbd84.x86_64 : drbd84 kernel module(s)
Thank you so much & Regards - Willi
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
|
DRBD-8.4
