Database Reference
In-Depth Information
ging the hard-linked versions. To be safe, make the copy outside the FileMaker Server
folder structure.
Scheduling a Backup
One of FileMaker Server's primary advantages is the ability to perform automatic backups of
databases without disruption to the users. You can't overestimate the importance of this step.
Someday your server will crash, perhaps because a hard drive fails, the cleaning lady pulls
the server cord, or the power goes out, or for any of a dozen other reasons. When this hap-
pens, your best course of action is to take your lumps, restore from backup, and reenter any
missing data. The more often you back up, the less difficult that'll be.
If you want, you can configure FileMaker Server to back up to a location different from the
main hard drive on your server computer. It makes good sense, for example, to back up on a
second hard drive. This way if the main hard drive fails, you don't lose your database
and
your backup.
But you should also make offline backups that are stored in a remote location. This protects
against natural disaster scenarios where all the computers and drives in your office are lost.
FileMaker's automated backup gets the files cleanly copied to a drive of your choice, but
you'll need another process for copying those backups to CD, the cloud, or any other offsite
location you choose. You can copy the file manually, or use a third-party backup service. Just
make sure you're copying backups and not your live databases.
To configure the backup location, in the Admin Console sidebar, choose Database Server.
Then switch to the Folders tab. In the middle of this window, you see the backup folder loca-
tion (
Figure 19-13
).
In the Path box, type the full path to the folder where you want backups stored. The path has
to start with filewin: (Windows) or filemac: (Mac), and end with a slash. When you're done
typing, click Validate, and FileMaker tells you if your path is valid.
