Administrator’s Guide

42 FileMaker Server Administrator’s Guide
Protecting files with accounts and privileges
It is important to use the access privileges in FileMaker Pro when files
are shared on a network. Using FileMaker
Pro, you can restrict what
users see and do in a database file by defining accounts and privilege
sets.
Accounts authenticate clients who are attempting to open a
protected file.
Privilege sets specify a level of access to the database
file, limiting what clients can do with the layouts and fields they can
see.
Important Protect shared FileMaker Pro files by using FileMaker Pro
accounts and privilege sets. Although the shared FileMaker
Pro files
can reside on a file server, which may have its own security scheme,
any files available to FileMaker
Pro clients bypass network and file
server protection. For more information about protecting files, see the
FileMaker Pro User’s Guide or FileMaker Pro Help.
Restoring FileMaker Server default settings
To restore all default settings, uninstall and reinstall FileMaker Server.
For more information, see
chapter 3, “Installing FileMaker Server.”
How FileMaker Server behaves during
system sleep or abnormal shutdown
Windows supports Power Conservation mode, which can cause the
server computer to sleep (hibernate or enter Standby mode). This
suspends access to hosted databases.
Mac OS computers can suspend operation when they enter an energy-
saving system sleep state.
FileMaker Inc. recommends that you disable sleep mode on
computers running FileMaker Server.
To prevent your system from sleeping:
1 Windows: Clear Enable hibernation 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).