Backup and Restore Procedures.



In the world of Information Technology, a backup or the process of backing up, refers to the copying and archiving of computer data so that it may be used to restore the original in the event of data loss. The purpose of backups is to recover data after its loss, be it by data deletion or data corruption. Data deletion refers to users (accidentally or intentionally) deleting data within an application program (ie: a FileMaker database). Data corruption refers to errors in computer data that occur during writing (to a hard drive), reading, storage, transmission, or processing, which introduce unintended changes to the original data.

Our hosting environment employs a number of technologies that automate backup routines at a number of levels: Application Program; Operating System and; Server levels.

At the Application Program level, FileMaker Server has the ability to define backup schedules to be performed on desired databases, via it’s Admin Console. It also has the ability to define where these backup files are saved. When the backup schedule is performed, FileMaker Server will pause the databases and then make a copy of them to the backup folder that is defined. Backup folders can include folders on another hard drive and in any location specified. 

A backup is preserved to ensure the integrity and protection of data and these backups at this level are scheduled to occur:

  • Default schedule for FMServer v17+ – occur daily and midnight.  The last 7 copies are kept.  This is synced to AWS S3 storage at 1:40am each day, so the last 7 midnight backups are off-machine in AWS S3 storage.
  • At 20 minutes past the hour from 6:20am to 11:20pm, with the last 6 retained. On-machine only.
  • 3) At 6:40am, 10:40am, 2:40pm, 6:40pm, and 10:40pm, with the last 4 retained. On-machine only.

If a longer history is required off-machine, this can easily be changed using AWS S3 bucket settings and an adjustment to the copy script.  If the Hourly or Four-Hourly backups should be off-machine, that can be scripted and scheduled.  If additional weekly or monthly backups to AWS S3 are required, these can be scheduled. Please note that additional backups will increase storage usage, which will attract additional cost.


Restoring a backup from AWS S3 is carried out via access to the AWS Management Console.  Services > S3 > Select backup to be restored > select checkbox of backup to be downloaded > click download button and save backup to local computer.  This can then be pushed back up to the Server.

Any individual record or selection of records can be restored by import. The entire database can be “rolled back” to a point in time by replacing the current database with a backup copy on the server.  The key is to inform the FMStudio of the need for restoration as soon as possible.


2021 ADS|IJP| Backup&Restore_ 20211119