
Chapter 5 | Administering FileMaker Server 55
Scheduling database backups
Use the FileMaker Server Schedule assistant to create a scheduled task to:
1 back up all hosted databases
1 back up hosted databases that are in a specified folder
1 back up a specified database
To create a scheduled task for backing up databases, choose the Admin Console Schedules
pane, click
, and choose Create a Schedule. Then, choose Back up databases, and specify
whether you want to back up hourly, daily, weekly, or on a custom schedule. You can also select
the maximum number of database backups you want to keep for a scheduled backup.
Database backups are saved in the default backup folder or in a folder that you specify. You can
specify the default backup folder on the Admin Console Database Server > Folders tab.
Note If you are backing up a database to a volume that supports Windows ReFS, see “Creating
a backup to a Windows ReFS volume” on page 55 for more information.
When FileMaker Server backs up a database, it copies the database while it is active. Users can
continue to make modifications. When the copy is complete, the database is paused to
synchronize backup files with the current database and then the database is resumed. You can
set options to verify the backup, save a clone of the database without the data, and send email
notifications to clients.
Using progressive backup
To enable progressive backup and specify the folder for progressive backup files, choose the
Admin Console Database Server > Folders tab. For Progressive Backup Folder, select Enable
progressive backups. Enter the number of minutes for Save interval, and enter the location of
the progressive backup folder.
Creating a backup to a Windows ReFS volume
FileMaker Server can make full backups on any local volume that supports Windows Resilient File
System (ReFS); however, the backup process may take more time and require more disk space.
Note Creating backups on remote ReFS volumes is not supported. For more information, see
FileMaker
Server Help.
When backing up a database, FileMaker Server checks if the backup volume uses ReFS. If the
file is not being backed up to a ReFS volume, FileMaker
Server checks if the selected databases
have changed since the last time that scheduled backup ran. For each scheduled backup task,
FileMaker
Server creates a full copy of the databases that have changed and creates hard links
to the backed up databases without any changes.
Because ReFS doesn’t support hard links, FileMaker Server must create a full backup even if the
hosted database file is identical to the most recent backup file.
Commenti su questo manuale