Thanks Jonathan, I’ll file both your and Lee’s solutions. When being constantly connected is vital then taking the proper measures is what I’ll have to do. I so appreciate those that know being willing to help.
John > On Sep 10, 2016, at 1:55 PM, Jonathan Fletcher <[email protected]> wrote: > > There are a few methods if you are primarily concerned with your FileMaker > Server files. > > 1. The native FileMaker way is to set up something called Standby Server. It > is an exact duplicate of your main machine that has a copy of FileMaker > server running on it (one license allows for both). The first copy saves all > changes to the the second one, so that if your first one fails, you can > configure your second one to be the primary and be up and running in a matter > of minutes. > > That said, the controls to manage this dual configuration approach are > strictly command line and are kind of a PITA. > > > 2. 360Works, a great company that provides a lot of tools for the FileMaker > community, has a product called Mirror Sync that does a similar thing, but > you can use both databases at the same time. You will need two licenses for > FMS and one for MirrorSync, so this is not the cheap approach, but is super > for having a data base running in two locations (for instance, two > geographically distant offices). > > It is easy to set up and can actually work between pretty much any two > database products, including FileMaker and a variety of SQL databases. The > downside, like I said, is that it is the more costly approach. > > > 3. Another approach is to have your files hosted in a data center where the > hardware is a lot less likely to have an issue. More and more FileMaker > developers are spinning up FileMaker servers in Amazon Web Services > instances, and many consider it the future of FileMaker hosting. There are > even ways to have the data only available on your internal network, totally > separated from the internet. > > > But, of course, Lee’s suggestion is a great one for a whole-machine approach > and one I use on all my machines, as well. > > Jonathan > > P.S. Oh, and TechTool Pro would have found your bad memory and saved you a > trip to the Apple Store, although that may have simply been an excuse to > visit your favorite haunt. > > > >> On Sep 10, 2016, at 12:00 PM, John Robinson <[email protected]> wrote: >> >> I guess things happen for a reason, nudging me to prepare for the unusual. >> >> At the office I had a MacMini start acting flaky, ran DiskWarrior, didn't >> help. Called Apple Tech support, fantastic lady from Canada spent at least >> an hour helping. s >> She felt I had some bad RAM and scheduled a Genius Bar appointment . At the >> Bar sure enough I had one of the Crucial ram that had gone bad. >> >> Ordered replacement & installed today, with the holiday I have been without >> a machine for a couple weeks. >> >> All this to ask this question. I am going to need redundancy very soon, so >> how do I set up a second Mini slave right beside the master? >> >> I can get the cabling working on both but how do you get the primary machine >> to feed every change, every app update, every change to the Filemaker >> database etc. etc. from the primary to the secondary? >> >> If one goes haywire I can't wait 2 weeks to get back in business, flip a >> switch and continue as normal until the damaged machine is repaired. Is >> there a way to do this? Maybe something built into the Mac OS? >> >> Thanks for any help. >> >> John >> > > -- > Jonathan Fletcher > [email protected] > > Kentuckiana FileMaker Developers Group > Next Meeting: 9/27/16 > > > _______________________________________________ > MacGroup mailing list > Posting address: [email protected] > Archive: <http://www.mail-archive.com/[email protected]/> > Answers to questions: <http://erdos.math.louisville.edu/macgroup/> _______________________________________________ MacGroup mailing list Posting address: [email protected] Archive: <http://www.mail-archive.com/[email protected]/> Answers to questions: <http://erdos.math.louisville.edu/macgroup/>
