Administrator’s Guide

30 FileMaker Server Administrator’s Guide
To prevent your system from sleeping:
1 Windows: Disable Hibernation and Standby Mode in the Power
options
control panel on the computer running FileMaker Server.
1 Mac OS: Disable system sleep in the Energy Saver pane by setting
the slider control to
Never in the Put the computer to sleep when it is
inactive for
area.
If sleep is enabled on the computer running FileMaker Server, it’s
important to understand how FileMaker
Server reacts, if the
computer enters sleep mode:
1 If there are no clients 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
opened 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 clients 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 clients 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 in the default database folder and the
additional database folder, 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) or
Event.log (Mac
OS).
Whenever FileMaker Server restarts after sleep or a forced
shutdown, you should always check the Application Log (Windows)
or Event.log (Mac
OS) for database corruption notifications. For
more information about viewing the events, see
“Viewing activities
in the Event Viewer (Windows)” or “Viewing activities in the
Event.log (Mac OS)” on page 39.
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.