5 Replies Latest reply on Mar 27, 2013 12:00 PM by taylorsharpe

    2 questions, backup and auto closing


      Hi Everybody,


      1. I want to backup file that is located on the server daily, let's say at 11 PM. Due to company network restrictions we can open the file only one at the time using local FMs.

      Sharing doesn't work--file is not visible when somebody opens it. Maybe there is a way to see which user account has it opened. I know, I know -- use a server version of FM

      but for the reason above can't get our IS to install the server FM.


      Q1: Is there a way to write the backup script that won't overwrite exixting backup but just create a new backup file with date in the name. We want to keep all backups.


      2. Q2: What would be the script to close that file let's say after idling of 20 minutes, or if the iddling cannot be dedected just pop the message: "The file will close in 3 minutes"

      and then close it.


      Can't think of anything...





        • 1. Re: 2 questions, backup and auto closing

          Is this file on a shared network volume, or hosted with FMS? I'd guess it's on a shared network volume because your issues are EXACTLY those that FMS solves.


          FMS can backup files while they are opened by multiple users, and can keep multiple backups. All automatically. No scripts needed to close and reopen files or worry about idle time.


          Sharing FMP files on network volumes is the WORST way of doing it, it inevitably leads to data corruption.


          Get FMS.

          • 2. Re: 2 questions, backup and auto closing

            He said it was not on a server. You can do this with the Save A Copy As script step. If you're on a Mac you can use a cron job, schedule a shell script to run an Applescript that will check to make sure the file is open and start the backup script from the file itself. The FM script you can name your file variable with the date and time then they will always be different.


            I did things like this before. Much easier to fight with IT and get a FileMaker Server.





            Best regards,


            agnes b. riley

            filemaker and web development

            zeroblue (http://www.zerobluetech.com/)

            download vCard (http://www.zerobluetech.com/docs/Agnes%20B.%20Riley.vcf.zip)



            FileMaker Certified in 10 and 11 • Member, FileMaker Business Alliance

            T: 877 917-9079 . C: 917-660-7221

            Store (http://store.zerobluetech.com/) | Blog (http://blog.zerobluetech.com/) | Facebook (http://www.facebook.com/zerobluetech) | Twitter (http://www.twitter.com/zerobluetech) | LinkedIn (http://www.linkedin.com/company/zeroblue-technology-solutions)

            • 3. Re: 2 questions, backup and auto closing

              I agree with Agnes. Server was built for this. The impact on your hosting will be much less and it will be more reliable, stable and cope much better with traffic. The logs are better the backups are built in... there are so many reasons.


              If you absolutely have to stick with FMP. I suggest your database  itself can schedule the backups. You don't have to resort to externals just make each script have a check for the time and save a copy if > the last backup time (which you store) + the interval you want. If there are no scripts running, there is nothing much new to back up...


              - Lyndsay

              • 4. Re: 2 questions, backup and auto closing

                Take a look at this article from FileMaker Hacks:



                This is the method i use to create backups of files i am working on before they get uploaded to server. Normally i setup a script with InstallOnTimer to run every hour while im working on the file, but im sure it can be scripted differently for your needs.

                • 5. Re: 2 questions, backup and auto closing

                  I am going to make an assumption that this is relatively unimportant data since you are using peer-to-peer sharing from client app.  Matt Leach has a good link for you. 


                  If you ever decide your data is important enough to need real server services, FileMaker Server is designed to handle these types of things and much more.  Not only can you get regularly scheduled backups, you can get progressive backups.  FileMaker server is faster and designed for multi-connections and you don't have to leave a copy open on some client machine.  Additionally, you can encrypt all data between clients and the server, which is not possible with a peer-to-peer system like you have described. Not to mention that you can run scheduled scripts from the server.


                  If things are not too tight financially, I would seriously take a look at FileMaker server since it is designed to meet these needs.  It'll make life much better for you.  But if you can't, I understand and that is how I first ran FileMaker databases.