MightyData

FileMaker and WordPress Consultants

  • Company
    • About
    • Contact
    • Team
    • Artists
  • Services
    • Consulting
    • Development
    • Our Process
    • Coaching
    • Training
  • Results
    • Customers
    • Success Stories
    • Testimonials
  • Blog

New Year’s Database Resolution: Backup! – Part 1

January 4, 2012 by Kirk Bowman 5 Comments

So, it is a brand new year and everyone is making resolutions for their personal and professional lives. Along with going to the gym and learning to fill-in-the-blank better, I want to challenge you to make a goal to backup your database better. (Hopefully, you are already backing up some.)

The easiest way to backup your FileMaker database is to use FileMaker Server. So, if you are not using FileMaker Server, why not? If you are using a hosting provider, then I will assume they are backing up the database for you. (Do you know how often they backup your database?) Otherwise, I assume you are hosting the database on your own server—with FileMaker Server.

FileMaker Server includes “Schedules”, the ability to automatically backup the live database at a regular interval. The database server comes with three schedules already created: Daily, Hourly and Weekly. However, only the Daily schedule is enabled by default. I am going to recommend some changes to the default schedules to improve your database backups.

Default backup schedules for FileMaker Server

To view schedules, login to the FileMaker Server Admin Console. Open a web browser directly on the server and type this URL http://localhost:16000. This should display a web page to launch the Admin Console. Of course, you will need the username and password for the Admin Console. Once you login, click on Schedules under Administration in the navigation tree.

To edit a schedule, right-click on it in the list of schedules and select Edit a Schedule. This launches a wizard to walk you through the various options for the schedule. These are the changes I recommend for the default schedules, which will backup the database once per hour for 24 hours, one per day for 7 days and once per week for 4 weeks.

Hourly Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 23
      Note: The daily schedule will take care of the 24th hour.
    • Verify backup integrity: Checked (by default)
      Note: For large databases you may need to uncheck this option due to the time required to verify the database each hour.
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Daily
    • Run every: 1 Hours
    • Start time: 12:00 AM
    • End time: 10:00 PM
  • Schedule Summary
    • Enable this schedule: Checked

Daily Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 6
      Note: The weekly schedule will take care of the 7th day.
    • Verify backup integrity: Checked (by default)
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Weekly
    • Select the days of the week: All days except Sunday
    • Once per day, Start time: 11:00pm
  • Schedule Summary
    • Enable this schedule: Checked (by default)

Modified daily backup schedule

Weekly Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 4
    • Verify backup integrity: Checked (by default)
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Weekly
    • Select the days of the week: Sunday
    • Once per day, Start time: 11:00pm
  • Schedule Summary
    • Enable this schedule: Checked

This is a great start for your New Year’s Database Resolution. In the next few articles, I will cover other ways to improve on this basic setup including email notification, offsite backup, and drive space. Together, we will help you get your database in good shape to start 2012.

Filed Under: FileMaker Server Tagged With: Admin console, Backup, Best practices

Comments

  1. Steven H. Blackwell says

    January 4, 2012 at 1:44 pm

    Do pay special attention to what Kirk has said here. It is vitally important that FileMaker systems have a rigorous backup protocol.

    And one important item: check that you can restore your system from a copy of the backup FileMaker Server has made.

    Reply
    • Kirk Bowman says

      January 4, 2012 at 1:59 pm

      Stephen, thanks for your comments. Database backup seemed like a great New Year topic.

      Reply
  2. Taylor Sharpe says

    January 5, 2012 at 7:32 am

    On a technical note… please make sure you do not backup live/open FileMaker databases except through the FileMaker Server backup schedules. For Mac Users, make sure Time Machine is not backing up the live FileMaker folder. And for you Windows Users, make sure your anti-virus software is not scanning live FileMaker databases…. it is guaranteed to corrupt data! However, please make sure you are backing up!

    And if you really consider your data to be mission critical, make sure you occasionally make a backup that you keep offsite. Yes, the tried and true “copy to disk and take it home” works. But if you want a better solution, look at 360Works SafetyNet that will do backups for you to the Amazon Cloud!

    Reply
    • Kirk Bowman says

      January 5, 2012 at 12:42 pm

      Taylor, thanks for stopping by. Your comments are exactly what I have in mind for future posts. Great minds think alike.

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Company
  • Services
  • Results
  • Blog

Copyright © 2026