At 10:21 AM 2/26/03, you wrote:
For most data an rsync like solution would work just fine. The problem with that is with files that are constantly being written to and changed like database files. Partial data writes during an rsync can corrupt the mirrors. Of course this is true of any thing but rsync would be slower having to periodically scan the drive for any files that have changed and may not sync files that currently open, locked and being written to. Using a lower level of sync could allow the data to be changed simultaneously on many systems without delay.

I have follow this thread for a while and I think we are missing some obvious solutions here. Either that or I have just over looked them.


You need to break the hardware system from the data in your mirroring.

The data could be written to an external raid array with multiple interfaces. The raid array handles the information redundancy requirements and can be accessed by at least 2 machines.

The machines run the exact same software which could be rsync'd to keep the same or could share system files from the raid array. One machine monitors the other machine using a heartbeat monitor as suggested by Maurice. (The second machine assumes the first machine's IP.)

If one machine fails the other takes over and still has access to the same files. If a drive fails, your raid array doesn't
go down.


For full redundancy you would want a raid array with redundant power and controllers.

regards,
--
Mark Lane
Hard Data Ltd.
mailto:[EMAIL PROTECTED]

Telephone: 01-780-456-9771
FAX: 01-780-456-9772

11060 - 166 Avenue
Edmonton, AB, Canada
T5X 1Y3

http://www.harddata.com/
--> Ask me about our Affordable Alpha Systems! <--




BEGIN:VCARD
VERSION:2.1
N:Lane;Mark
FN:Mark Lane
ORG:Hard Data Ltd.
TITLE:Sales
TEL;WORK;BUSINESS:780-456-9771
TEL;WORK;VOICE:780-456-9771
TEL;WORK;FAX:780-456-9772
ADR;WORK:;;11060 - 166 Avenue;Edmonton;AB;T5X1Y3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:11060-166 Avenue=0D=0AEdmonton, AB T5X1Y3=0D=0ACanada
URL;WORK:http://www.harddata.com
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20010222T231737Z
END:VCARD

Reply via email to