Setting up and configuring the operating system (Linux)

Recommendation	Do this
Avoid services that may impact the live, hosted database	Any service or application that allows the live, hosted databases to be copied or accessed may cause database corruption. Sometimes files accessed directly while FileMaker Server is under load become corrupted. To prevent corruption, remove processes, services, or applications that attempt to access the hosted files.
Don't use file sharing	The Database Server component of FileMaker Server accesses the FileMaker databases directly and manages the network access by FileMaker clients. File sharing is not needed.
Configure backup processes	Backup processes should exclude FileMaker Server files and database files. Interacting with files that are in active use can cause corruption.
Disk Permissions and S.M.A.R.T. Status	The underlying permissions for hosted databases are sometimes set incorrectly. Although the databases are placed in the right location, they can be inaccessible because FileMaker Server can't modify the permissions. Use FileMaker Pro to upload the database and to properly set the file permissions. See FileMaker Server Help.
Security	Require users to sign in instead of automatically viewing the desktop. FileMaker Server doesn't require anyone to be logged in for it to run.
Configure virus scanning	Do not allow antivirus software to scan the folders that contain hosted databases or the folders that contain files for container fields that store data externally. Antivirus software may cause file corruption if you allow real-time or on-access virus scanning while files are being hosted to users. With real-time scanning, the virus scanner takes a long time scanning the databases, which places a heavy load on the server's disk, memory, and processor.

Avoid services that may impact the live, hosted database

Any service or application that allows the live, hosted databases to be copied or accessed may cause database corruption. Sometimes files accessed directly while FileMaker Server is under load become corrupted. To prevent corruption, remove processes, services, or applications that attempt to access the hosted files.

Don't use file sharing

The Database Server component of FileMaker Server accesses the FileMaker databases directly and manages the network access by FileMaker clients. File sharing is not needed.

Configure backup processes

Backup processes should exclude FileMaker Server files and database files. Interacting with files that are in active use can cause corruption.

Disk Permissions and S.M.A.R.T. Status

The underlying permissions for hosted databases are sometimes set incorrectly. Although the databases are placed in the right location, they can be inaccessible because FileMaker Server can't modify the permissions. Use FileMaker Pro to upload the database and to properly set the file permissions. See FileMaker Server Help.

Security

Require users to sign in instead of automatically viewing the desktop. FileMaker Server doesn't require anyone to be logged in for it to run.

Configure virus scanning

Do not allow antivirus software to scan the folders that contain hosted databases or the folders that contain files for container fields that store data externally. Antivirus software may cause file corruption if you allow real-time or on-access virus scanning while files are being hosted to users. With real-time scanning, the virus scanner takes a long time scanning the databases, which places a heavy load on the server's disk, memory, and processor.