Server Technology PPNT Instrukcja Użytkownika Pobierz pdf (Strona 75)

Chapter 8 | Optimizing your FileMaker Server deployment 75

Setting up and configuring OS X

This table provides specific tips for the settings and configurations for FileMaker Server in OS X.

Configure virus scanning Avoid real-time or on-access virus scanning of databases when they are being

hosted to users. With real-time scanning, the virus scanner may spend large

amounts of time scanning the database files. This places a massive load on the

server’s disk, memory, and processor.

Defragment the hard drive Defragment the hard drive partition containing the live database files (not the backups)

routinely; however, don’t defragment the partition while files are being hosted.

Note Close any live hosted files with Admin Console before defragmenting. For

more information about how to close a file, see FileMaker Server Help.

Recommendation Do this

Avoid services that may

impact the live, hosted

database

Any service or application that allows the live, hosted database files to be touched,

copied, or accessed in any way may cause database corruption. Sometimes files

accessed directly while FileMaker Server is under load become corrupted. If you

remove the process that accesses the files, then they are no longer corrupted. Avoid

those services or applications that attempt to access the hosted files.

Don’t use file sharing FileMaker Server's database server accesses the FileMaker database files directly

and manages the network access by FileMaker clients. File sharing is not needed.

Turn off OS X Spotlight Spotlight indexing can impact FileMaker Server’s performance. The Spotlight

service automatically watches when information is written to the hard drive and

indexes the data to allow faster searches for files.

Don’t use Time Machine Time Machine is an application that automatically backs up files, but doesn’t back up

any files that are in use, such as the live FileMaker database files. If you use Time

Machine, it doesn’t corrupt the database files if it was configured to back up those

files, but can be very CPU intensive. You should add the locations where the

databases are stored to the “Do not back up” section of the Time Machine

Preferences to avoid problems.

Don’t enable FileVault FileVault is used to encrypt the entire OS X startup volume. Don’t enable FileVault

on your FileMaker Server machine. This requires an additional layer of software and

more processor work on any data being moved to or from the hard drive. Instead,

use FileMaker

Pro Advanced to encrypt databases. See “Encrypting databases” on

page 53.

Make sure the Dashboard is

not running

The OS X Dashboard allows small applications, called widgets, to run. Log out or

exit Dashboard. (Dashboard does quit when the user logs out.) By not running

Dashboard, server resources are not consumed with running widgets.

Configure the firewall The OS X firewall is disabled by default. You can enable the firewall by opening the

System Preferences application. Configure the firewall to allow incoming connections

to FileMaker Server. When FileMaker Server is initially deployed, OS X does ask

whether the FileMaker

Server component is allowed to accept incoming connections.

Disk Permissions and

S.M.A.R.T. Status

Because OS X is built on UNIX, the underlying permissions for hosted database files

are sometimes set incorrectly. Although the database files 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 file and to properly set the

file permissions. For more information, see FileMaker

Server Help.

Security By default when a computer running OS X starts, it immediately opens to the

desktop. FileMaker

Server doesn’t require anyone to be logged in for it to run.

Configure virus scanning Avoid real-time or on-access virus scanning of databases when they are being

hosted to users. With real-time scanning, the virus scanner may spend large

amounts of time scanning the database files. This places a massive load on the

server’s disk, memory, and processor.

Recommendation Do this

1 2 ... 70 71 72 73 74 75 76 77 78 79 80 81 82 83

Komentarze do niniejszej Instrukcji

Brak uwag

Server Technology PPNT Instrukcja Użytkownika Strona 75

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Oprogramowanie bazy danych Server Technology PPNT