I forgot: I could imagine a block based async kind of mirror, replicating sector changes. As long you have no total failure of the computer, it would even survive network issues.
But: what happens if you do a big import - or a MSC compact/repair, changing 50 or 100 GB of data? How long does your internet connection needs to upload 100 GB to resync the mirror? How long does it take to download 100 GB, to restore a disk failure? I could imagine a very long downtime for such issues... Normally we do recommend a set of 4D Server mirrors. Locally 4D Server + Mirror 1, maybe even Mirror 2 (to have minimum downtime, as you don't need to stop the system to bring a machine back into the mirror group). Remotely another mirror (could be a cheap VM somewhere, as far away as possible). That mirror is the worst disaster mirror, if an earth quake or big fire or similar destroys everything local. Remote restore takes more time, but you don't care, as you need to rebuild office first... Local restore goes still super fast. 4D Deutschland GmbH Geschäftsführer Laurent Ribardière Telefon: +49-89-856 33 43-0 Amtsgericht München HRB 92258 Fax: +49-89-856 33 43-99 Obere Hauptstrasse 2 E-Mail: [email protected] 85386 Eching - Deutschland Web: www.4D.com ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
