I would agree if the box was indeed dead. If the box is healthy
putting it back into the mix should return it to primary. Of course
assuming public and private heartbeats are back online. That's based
on the ha document from apple. when the primary comes back online the
backup should release and hand over services. It should not take a
shutdown of the backup and another restart of the primary defeating
the purpose of this type active/passive solution.
Anyway I will re check my settings.
On Nov 15, 2007, at 4:39 PM, Josh Wisenbaker <email@hidden>
On Nov 15, 2007, at 12:19 PM, Scott Comboni wrote:
Well It seems the 10.4.11 release seems to have solved a few
issues. I can now take over my Primary machine in full failover
Great!! so that is working. Releasing is my new issue. When I
reboot the Primary the Seconday sees the machine up on the Firewire
IP, releases control but the Primary machines en0: IP is not
As someone who has maintained various types of clusters over the
years I can say that automatic failback is always a bad idea. The
primary failed for a reason, services should never go back unless
you explicitly send them back when you know the box is OK.
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden