Help

Maintaining and recovering FileMaker Pro databases
F
ILEMAKER PRO HELP 1199
A strong backup strategy is one that employs multiple media and backs up on a consistent
schedule. This affords 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 files to another disk for safekeeping. 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.
Note To avoid possibly damaging the only backup of your database, make sure that you copy the
database file you want to restore and leave the original backup file unchanged in the backup folder.
Do not move the database file out of the backup folder, and do not use FileMaker
Pro to open the
database file that is stored in the backup folder.
Example backup script
You can use the following script to save automated backup copies of a FileMaker Pro database.
This script saves a copy of your database on the fifth close and every fifth close thereafter. To make
the script work, you need to define a global field called Count Field in one of the tables in your
database. If you do not define a global number field, FileMaker
Pro may increment a different record
each time you close the application. You should define this script in all solution files that require
backups.
To create the script:
1. Choose Scripts menu > Manage Scripts. Or, choose File menu > Manage > Scripts.
2. In the Manage Scripts dialog box, click New. For details on creating scripts, see Creating
and editing scripts.
3. In the Edit Script window, for Script Name, type Backup.
4. Enter the following script:
Set Field [<table name>::Count Field; <table name>::Count Field + 1]
If [<table name>::Count Field > 4]
Save a copy as ["Backup Copy.fmp12"; copy]
Set Field [<table name>::Count Field; 0]
End if
5. When you are finished, close the Edit Script window, then click Save.
6. Close the Manage Scripts dialog box.
7. Choose File menu > File Options, and click the Script Triggers tab.
8. Click the OnLastWindowClose script trigger, then click Select.
9. Select the Backup script.
10. Click OK.