Administrator’s Guide

4-12 FileMaker Server Administrator’s Guide
If sleep is enabled on the computer running FileMaker Server, it’s
important to understand how FileMaker Server reacts, should the
computer enter sleep mode:
1 If there are no guests connected to hosted files when the operating
system notifies FileMaker Server that it is going to sleep,
FileMaker Server flushes the cache to disk and leaves hosted
databases open. Because the cache is saved to disk before the
computer sleeps, hosted databases experience no data loss and are
open when the operating system wakes up.
Note Database backups or scripts scheduled in FileMaker Server do
not run while the operating system is sleeping.
1 If there are guests connected to FileMaker Server when the
operating system notifies FileMaker Server that it is going to sleep,
FileMaker Server responds to the operating system, instructing that
it should not sleep while FileMaker Server is running.
If the operating system shuts down unexpectedly while guests are
connected and before the cache can be written to disk (for example,
because the battery is critically low, the computer is overheating, or
a user turns off the server computer in an emergency),
FileMaker Server attempts to recover the state of hosted files when
it restarts. As it opens the files located in the FileMaker Server 5
folder (or subfolders one level down), FileMaker Server performs a
consistency check on each file. If a file is found to be corrupt,
FileMaker Server logs a corruption event in the application log
(Windows 2000) or Server Event Log (Mac OS).
Important Files that were open but are not located in the
FileMaker Server folder (or subfolders one level down) are not
reopened or checked for consistency.
Whenever FileMaker Server restarts after sleep or a forced
shutdown, you should always check the application event log
(Windows 2000) or Server Event Log (Mac OS) for database
corruption notifications. For more information about viewing the
events, see “Viewing activities in the Event Viewer
(Windows 2000)” or “Viewing activities in the Server Event Log
(Mac OS)” on page 5-15.
Also, check your scheduled tasks to ensure that important backups or
scripts were not scheduled to run while the operating system was
asleep or off. These tasks will not run until the next scheduled time
when FileMaker Server is running and the operating system is
awake.
To find out the last time a scheduled task ran:
1. Open the FileMaker Server console (Windows 2000) or bring
FileMaker Server to the foreground (Mac OS).
2. Click Schedules in the FileMaker Server Console Tree (Windows)
or choose Window menu > Schedule Window (Mac OS).
3. Look at the time and date displayed in the Last Run column.