Database Reference
In-Depth Information
path is validated and you click Save, your first progressive backup will start. If you decide to
wait until a later time to start the progressive backups, be sure to click Revert.
Figure 19-17. Click “Enable progressive backups” and set a Save interval. Then enter a path for
FileMaker Server to save your backups in.
WARNING
After you select “Enable progressive backups,” if you close (or navigate away from) the Admin
Console without clicking Save or Revert, you will have to restart FileMaker server to regain access
to the Database Server pane.
Server Hardware
If you have lots of users or lots of data (or both), your database server needs all the power
you can give it. After all, FileMaker Server performs finds, edits records, sorts, imports, ex-
ports, and otherwise constantly busies itself with the work of
every user
. FileMaker Server is
multithreaded, which means that it can handle several requests at once. This means that if
one of the server's processors is busy doing a search for Don, Peggy doesn't have to wait un-
til Don's work is done. FileMaker Server routes Peggy's request to an open processor, and
both operations can be handled at one time. And FileMaker Server 13 is 64-bit compatible,
which means it's even faster than before. But you'll need a 64-bit computer and operating
system to take advantage of this speed increase.
The most important thing you can do to make FileMaker Server faster is give it faster access
to the data on the disk. This means you should
never
store the files on a file server. They
should always be on a hard drive on the host computer. If performance still isn't as fast as
you need it to be, your best upgrade may be a faster system that isn't a disk at all. Solid State
Drives, or SSDs, replace mechanical drives with memory chips that retain their contents even
when switched off. SSDs are orders of magnitude faster than hard drives and very appealing
