Thomas Maul writes: >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.
That's what we do. And every month we take Mirror 3 offline and do an MSC compact/repair. Balinder Walia writes: >In case of network is down I would imagine the system should work like the way >Dropbox works. >It keeps track of changes since last sync and then sync back up-to-date when >network comes back up...in theory at least. Another good reason to use 4D Server Mirroring. If the network to the remote mirror is down, you can save up the segmented log files until the connection is restored then the mirror is automatically brought up to date. Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 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] **********************************************************************
