<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi,<BR>
<BR>
Our current system is running DRBD-8.0.6 on 2 boards, One of the baords is active and the other board is standby.<BR>
DRBD is configured with meta-disk set as internal, port 7789, protocol C, size 9380. Excerpts attached at the end.<BR>
<BR>
To minimize outage by resetting both boards, we would like to upgrade and bring up standby board on DRBD-8.0.16 first. My attempts are not successful so far.<BR>
<BR>
Things modified to match DRBD-8.0.16:<BR>
In drbd.conf file size is modified as "size 9380K"<BR>
All other entries are kept same as in DRBD-8.0.6<BR>
<BR>
Issues:<BR>
When drbd is started on standby drbdstatus shows <BR>
0: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---<BR>
<BR>
And Primary does not detect DRBD on standby board.<BR>
0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---<BR>
<BR>
Questions:<BR>
1. Is DRBD-8.0.16 backward compatible with DRBD-8.0.6?<BR>
2. Why there is no communication between DRBD-8.0.6 and DRBD-8.0.16?<BR>
3. Can any one list all the changes one must do to upgrade DRBD version on a redundant setup (standby first and then active)?<BR>
<BR>
Excerpts from drbd.conf of DRBD8.0.6:<BR>
disk {<BR>
on-io-error detach;<BR>
size 9380;<BR>}<BR>
<BR>
on Sc1 {<BR> device /dev/drbd0;<BR> disk /dev/tffsb4;<BR> address 10.19.17.1:7789;<BR> meta-disk internal;<BR> }<BR>
on Sc2 {<BR> device /dev/drbd0;<BR> disk /dev/tffsb4;<BR> address 10.19.18.1:7789;<BR> meta-disk internal;<BR> }<BR><BR>
Please do the needful,<BR><BR>
Thanks and Regards,<BR>LAK <BR><BR><BR><BR> <br /><hr />Chin music and high voltage T20 action on MSN Sports <a href='http://sports.in.msn.com/cricket/2010t20wc/ ' target='_new'>Sign up now.</a></body>
</html>