Live File Transfer
Copies a currently hosted .fmp12 file from one FileMaker Server to another server in its deploy chain. Unlike Host from Backup, the source is the live hosted file itself — not a backup — so the portal briefly pauses the file to get a consistent copy. The transfer runs natively in the portal over SSH and the FileMaker Admin API (no AWX job is involved). All pages in this flow show an Experimental warning banner.
The source file is never left paused. If anything fails mid-transfer, the portal resumes the file before reporting the error.
This workflow requires the portal’s 1Password integration: pausing, opening, and closing files go through the FM Admin API, whose credentials (and each server’s SSH key) are fetched from 1Password. If those credentials are not configured, the transfer stops immediately with a clear error before touching any file.
The wizard has four steps:
1. Select a client
From the homepage, click the Live File Transfer card (or pick it from the Tools menu in the navigation bar), then choose the client group. Only groups with transfer-eligible servers (those with a configured deploy chain) are shown.
2. Select the source host and file
The source host holds the live hosted file you want to copy. Production servers display a red badge.
Select the source server, then click Load databases to list its hosted .fmp12 files via the FileMaker Admin API (falling back to SSH). Select the file to copy.
3. Select the target host
The target host receives the copy. Only servers in the source’s deploy chain are listed — the source itself is excluded.
4. Review and confirm
The review page shows the source and target side by side, plus:
Disk space indicator
The same stacked bar as the hosting flow, showing the target’s databases volume:
| Segment | Meaning |
|---|---|
| Grey | Already used |
| Yellow | Backup copy of the existing target file (only when overwriting with backup enabled) |
| Blue | Space this transfer will occupy (red if it will not fit) |
| Light | Free space remaining at the transfer’s peak |
Under the bar, Used now / Peak during / After give the same story as percentages — see reading the disk figures.
The disk-capacity policy applies. Above 90% projected usage the Run File Transfer button stays disabled until you tick the acknowledgement below the bar; above 95% it is refused outright. The transfer re-verifies disk space on both servers before copying regardless — the snapshot copy on the source is judged by the same policy as the file landing on the target.
Target file
Defaults to the source filename; rename it here if needed (must end in .fmp12). If a file with that name already exists on the target, a warning appears and the file will be replaced:
- On a non-production target, Overwrite the file on the target is pre-selected so repeat transfers run without extra clicks. Unchecking it makes the transfer fail instead of replacing the file.
- On a production target, you must enable it yourself — the Run File Transfer button stays disabled until you do.
Optionally enable Back up the target file before overwriting (saved to a timestamped folder in the target’s backup directory).
Open database after transfer
Off by default — the file is placed in the target’s databases folder without being opened. Enable this to have FileMaker Server open the database as soon as the file is copied; an optional Encryption key (EAR) field appears while it is enabled. Enter the key for encrypted files, or leave it blank to have the key fetched automatically from 1Password (unencrypted files need no key).
Transfer method
| Method | How it works | Trade-off |
|---|---|---|
| Transfer a snapshot copy (recommended) | Pauses the hosted file just long enough to take a local snapshot copy, resumes it immediately, then transfers the snapshot. | The live file is paused only for seconds, but the source needs enough free disk space for the copy. |
| Pause the live file and transfer it directly | Pauses the hosted file for the entire transfer, then resumes it. | Uses no extra disk space, but users cannot write to the file while the transfer runs. |
Production confirmation
If either server is marked production, a confirmation modal appears when you click Run File Transfer:
- Production target — you are placing a file onto a production server.
- Production source — the live production file will be paused (briefly for a snapshot, or for the whole transfer in direct mode), during which users cannot write to it.
Monitoring the transfer
A progress card shows the current phase with a live progress bar, bytes-transferred statistics, and estimated time remaining.
Transfer phases
| Phase | What is happening |
|---|---|
| Initialising | Connecting to both servers and fetching paths |
| Pausing | The source file is paused via the FM Admin API |
| Taking a snapshot | Local copy of the paused file (snapshot method only) |
| Resuming | The source file is resumed |
| Closing existing database | FMS closes the current target file (overwrite only) |
| Backing up existing file | The target file is backed up before replacement |
| Copying file | The .fmp12 file is being transferred |
| Opening database | FMS opens the newly placed file, if Open database after transfer was enabled (using the EAR key you entered, or one fetched from 1Password for encrypted files) |
| Verifying | The file’s status is checked with fmsadmin |
The order above is for the snapshot method, where the source file resumes before the copy starts. With the pause and transfer directly method, resuming happens after the copy completes instead.
Disk usage before and after
A disk card on the progress page shows the target’s disk state before the transfer (with the projected impact) and after it completes (as actually measured).
Cross-server fallback
A direct server-to-server connection is attempted first — the file streams straight from source to target. 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.
Cancelling
Cancelling removes any partial file from the target and resumes the source file.
Completion
- Success — the file is on the target (and opened, unless you disabled that). Click View history for the audit record.
- Failure — the error message is shown, and the source file has been resumed. Common causes: insufficient disk space, the target file already existing without overwrite enabled, an incorrect EAR key, network interruption.
History
Navigate to History in the top navigation. The Transfers tab shows all transfers, with source, target, files, transfer time, and result. You can also filter the feed by server, user, result, or file name.