User manual

Appendix B
Backing up and recovering files
Power failures, hardware problems, and other factors can damage a
FileMaker Pro file. While the recover feature of FileMaker Pro may
be able to salvage your damaged file, it is strongly recommended that
you back up your important FileMaker Pro files on a regular basis.
Consistent and properly executed backups are the best protection
against damaged or corrupted databases.
This appendix describes:
1 why regular backups are important
1 how to automate database backups with FileMaker Pro scripting
1 some reasons why files may become corrupt
1 how to recover a FileMaker Pro database
Backing up files
Routine backups are imperative for any document stored on a
computer. Magnetic media has a sometimes transitory nature, and is
susceptible to a variety of problems. Extreme heat, cold, sunlight,
and the presence of electric and magnetic fields can all contribute to
the failure of magnetic storage media.
Keep in mind that it is easier to back up a database than it is to
recreate it. Whether you should be backing up every day, several
times a week, or less frequently is usually determined by the amount
of data you are adding to your database(s), and how difficult it would
be to recreate your files in the event they become corrupt.
A strong backup strategy is one that employs multiple media and backs
up on a consistent schedule. The multiple copies you create by backing
up your data to different media afford you some protection against the
failure of a single hard disk, removable disk, tape, or other media.
In its simplest form, backing up means copying your file(s) to
another disk for safe keeping. As your files become larger or more
numerous, you might need to use a third-party program to do a
proper backup.
A good third-party backup program should provide multiple copies
of a database as sources for restoration. A scheme involving rotating
backups can accomplish this. Typically, this method involves
separate backup copies over no less than a two-week rotation. The
file is backed up to a set on day one, a new set on day two, until ten
sets of backups exist (assuming a five-day work week). On the
eleventh day, the first set is reused. This type of rotation ensures that
a lurking problem will not spoil your chances of a complete file
restoration.
For very important files, it’s a good idea to store backups at an off-
site location. Fires, earthquakes, and other disasters can and do
occur, and there is added safety in securing copies of your vital files
off-site.
Using a backup script
You can use the following script to save automated backup copies of
a FileMaker Pro 5 or later database.
This script saves a copy of your database on the fifth close and every
fifth close thereafter. To make the script work, you will need to
define a number field called Count Field. You should define this
script in all solution files that require backups.
1. Choose Scripts menu > ScriptMaker.
2. For script name, type Backup.
3. Click Create.