FileMaker Server becomes unresponsive when running backup at the same time as heavy imports/deletes (1 Comment)

Issue report by André Vedgren

Product

FileMaker Server

Version

13.0.5.520

Operating system version

Windows Server 2012R2

Description of the issue

When running large imports or delete all requests from client and a server scheduled backup kicks in, the server becomes unresponsive. I.e. clients freezing up and when trying to modify scripts, error messages of users with name () already editing.

Clone or verify options don't seem to make a difference. We don't use progressive backups.

The files can not be closed or the users logged out using the admin console and even the command prompt FMSADMIN restart and stop commands are igonored by the server.

Using Task Manager to shut down server works but on restart, no schedules or databases are shown. A complete reboot of the server brings everything back to normal.

Steps to reproduce the problem

Run heavy script with delete all in large table (many records, many fields with indexes) and let scheduled backup script kick in.

Expected result

Slower but steady performance

Actual result

Server ignores commands without error messages, clients are unable to use open files

Configuration information

FileMaker files are anything from a few MB to several GB in size with tables spanning up to 250,000 records.

Workaround

We are now attempting running few backups while heavy schedules are performed. This is, however, not a permanent solution.