I know absolutely nothing about mirroring systems with autostart etc.
My initial thoughts were as follows: 1. provide accurate duplication of the entire primary machine to the secondary one which is running off a temporary ip address. 2. provide a 3rd monitoring server to keep an eye on both machines to notify me of any failures of either and to automatically execute the proper copy scripts on the 2nd one in event of failure of 1st one to change all ip addresses to turn 2nd one into 1st one with same ips and start all sleeping services and vserver guests on 2nd one. and then auto-log into our router to clear the arp cache so the standard ips activated on 2nd machine are visible immediately without waiting the 3 hrs for cache clearing. i was just thinking after i wrote this that i could keep all 4 nics pre-configured with the same ip addresses and keep the 3 public ones in a down state using only the private localnet nic and then only have to copy a net config that included the pvt address of the 1st machine as well as current 2nd one to keep access uninterrupted. the 2nd machine must take over everything including identity of the 1st machine since the host runs certain applications we use network wide in addition to all the vservers. it would seem to me , without research yet as i am only gathering 'structure' info outlines, that this heartbeat system as described would be a bit simplistic for this? or is it capable of doing everything needed to the 2nd machine in event of 1st machine failure? is there a reference to guide me more in this when i am ready to do it ( a few months from now) ? -- Chuck _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
