What is your clustering software and what is the configuration? Also post your DRBD configuration and the output from cat /proc/drbd during each stage of your testing which reproduces the issue.
Maybe post some kernel logs too would be helpful. Simply switching pri/sec on DRBD won't cause a node to go outdated, unless you split brain the environment. David On 5/20/12 9:25 AM, Net Warrior wrote: > Hi there list! > > I've got a doubt regariding DRBD usage, at the moment I'm trying to > implement a HA systems with two nodes, is a easy and basic setup > Two servers, running oracle and LVM. > > I configured once resource lest's say /dev/rootvg/myoracle-device on > both, this is working fine, I can perform a manual failover as follow > > drdbadm secondary node1 > umount /dev/drbd1 > > drdbadm primary node2 > mount /dev/drbd1 > > This works fine and I have both serer sincronized, my problem or doubt > is, when the other node fails,lets say, I power it off, the node2 takes > primary > role, I do it manually, but I have the information Outdated and I loose > lots of information and I have to wait till node1 comes up to syncronize > with it. > > So, does DRBD work like that? I thought DRBD was syncronizing in > backround to the other node to have both nodes with the same > information, PLEASE, > correct me if I'm wrong, cuz maybe this solution in not well implemented > configured or I missunderstood what'd DRBD is for. > > > Thanks for your time and support > Best regards > > > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
