Host from Backup — On-Server
Copies a .fmp12 backup file from the server’s own disk into a FileMaker Server’s hosted databases folder. Transfers can be same-server or cross-server (via deploy chain). All pages in this flow show an Experimental warning banner.
This flow uses the backups a server keeps on its local disk, so it is the fastest option — but only reaches as far back as that server’s on-disk retention. To restore an older backup from off-site object storage, use Host from Backup — Object Storage instead (deeper history, but slower because the file must be pulled back from object storage first).
The process has four stages:
1. Select and browse
From the homepage, click the Host from Backup — On-Server card.
Select a client — choose the client group whose server you want to browse. Every client with at least one server you can access is listed.
Select a server — choose the FileMaker Server within that client whose backups you want to browse. Production servers display a red badge. Click Browse backups to continue.
Disk space indicator — after selecting a server, a bar shows how full the databases filesystem is (the volume where hosted files live), as a used percentage with the free space beside it. Hover for the exact path. This reflects the databases volume, not the backup volume — they may differ.
Navigate the backup directory — the portal connects over SSH and lists the backup directory contents.
- Click a folder to navigate into it.
- Use the breadcrumb trail to jump to a parent folder.
- Click .. to go up one level.
- Use Change server to return to the server list for the selected client.
Initiate a transfer — click the green Host button next to a .fmp12 file.
2. Configure the transfer
Destination server
If a deploy chain is configured, you can choose:
- Same server — file is copied within the same FileMaker Server.
- Peer servers — servers in the deploy chain (e.g. dev → prod).
If no deploy chain is configured, the file goes to the same server automatically.
Servers marked production display a red badge. Selecting a production server will trigger a confirmation dialog before the transfer proceeds.
Destination filename
Defaults to the original backup filename. Rename here if needed. The .fmp12 extension is added automatically if omitted.
Backup existing file
If a file with the same name already exists at the destination, an option appears to back it up before overwriting. When checked, the current file is saved to a timestamped folder in the backup directory before being replaced.
Open database after transfer
Check this to have FileMaker Server open the database immediately after the file is placed. An optional Encryption key (EAR) field appears — enter the key for encrypted files, leave blank otherwise.
Container data
Only shown when a peer destination server is selected.
If container data directories exist on the source server, they are listed as optional checkboxes. Select any you want synced to the destination alongside the database file.
3. Review and confirm
Shows source and destination side by side with a stacked disk usage bar:
| Segment | Meaning |
|---|---|
| Grey | Already used |
| Blue | Space this backup will occupy |
| Light | Free space remaining after the transfer |
Exact figures are shown below the bar.
The disk-capacity policy applies. Above 90% projected usage the Host File button stays disabled until you tick the acknowledgement below the bar; above 95% it is refused outright. The transfer re-checks the disk when it launches, so a review page left open while the disk filled up is re-judged rather than trusted.
Production confirmation — if the destination is a production server, a confirmation modal appears when you click Host File. Read it carefully before confirming.
Click Host File (or Overwrite & Host if overwriting an existing file) to begin.
4. Monitor the transfer
A progress card shows the current phase and a live progress bar.
Transfer phases
| Phase | What is happening |
|---|---|
| Initialising | Connecting to server(s) and fetching paths |
| Closing existing database | FMS is closing the current file (overwrite only) |
| Backing up existing file | Current file is moved to the backup location |
| Copying file | .fmp12 file is being transferred |
| Syncing container data | Container directories transferred (cross-server, if selected) |
| Opening database | FMS is instructed to open the newly placed file |
For cross-server transfers, live bytes-transferred statistics and estimated time remaining are shown.
Cross-server fallback
A direct server-to-server connection is attempted first. If unavailable, the portal falls back to relaying the file through the app server. A notice is displayed when relay mode is active. The transfer completes correctly either way but may be slower.
Completion
- Success — the file is in the destination’s databases folder. Click View history to see the audit record.
- Failure — the error message is shown. Common causes: insufficient disk space, incorrect EAR key, network interruption.
History
Navigate to History in the top navigation. The Host from Backup tab shows all transfers, with source, destination, time, and result. You can also filter the feed by server, user, result, or file name.