FileMaker Standby Server is a business-continuity feature available as an optional add-on for FileMaker Server 2026.
It maintains a second FileMaker Server installation that is regularly synchronized with the primary server. If the primary server becomes unavailable, an administrator can switch operations to the standby server and restore access more quickly than by installing a new server and restoring conventional backups.
Its primary objective is not to preserve historical copies of databases, but to reduce the duration of a service interruption.
How does FileMaker Standby Server work?
A Standby Server configuration uses two FileMaker Server installations:
- The primary server, which normally hosts the databases and accepts client connections
- The standby server, which receives replicated data and configuration from the primary server
The server roles are configured from the Connectors > Standby Server section of FileMaker Server Admin Console.
The available roles are:
- None, when the server does not belong to a standby configuration
- Primary, for the active production server
- Standby, for the secondary server
- Standby Snapshot, when the standby server is initialized using compatible virtual-machine snapshots
The primary server regularly transfers the data and configuration required to keep the standby environment ready to take over.
Switchover is not automatic
FileMaker Standby Server should not be confused with an automatic failover cluster.
If the primary server becomes unavailable, FileMaker Server does not automatically redirect users to the standby server. A server administrator must initiate the switchover.
The administrator may also need to manage infrastructure outside FileMaker Server, including:
- DNS records
- IP addresses
- SSL certificates
- Firewalls and network routing
- External authentication
- Monitoring systems
- Integrations that refer directly to the primary server
Standby Server considerably reduces the work required to make another FileMaker Server operational, but a complete switchover procedure must also account for these surrounding components.
This procedure should be documented and tested before an actual incident occurs.
What is replicated?
The primary server regularly replicates its databases and FileMaker Server configuration to the standby server.
This makes Standby Server more comprehensive than simply copying .fmp12 files to another location. However, administrators must still verify whether elements maintained outside FileMaker Server are present on the secondary machine.
These may include:
- Operating-system configuration
- DNS and network configuration
- SSL certificates
- Server-side plug-ins
- External scripts and utilities
- Custom web files
- Third-party monitoring agents
- External identity-provider configuration
- Other services installed on the machine
A standby architecture is only effective if the secondary environment contains everything required to resume the service.
Standby Server using virtual-machine snapshots
FileMaker Server 2026 also supports a Standby Snapshot role.
With this method, the primary server creates a live virtual-machine snapshot that can be used to initialize the standby server. This may be considerably faster than creating and transferring an initial full backup.
This option requires both servers to run on hypervisors capable of creating compatible live snapshots. Not every virtualization environment provides this capability.
The snapshot directory must also exist on the servers and grant the FileMaker Server system user the necessary read and write permissions.
Standby Server is not Remote Backup
Standby Server and FileMaker Server Remote Backup are complementary, but they solve different problems.
| Remote Backup | Standby Server | |
|---|---|---|
| Primary objective | Recover data | Resume operations |
| Maintains historical backups | Yes | No |
| Maintains another server | No | Yes |
| Protects against accidental deletion | Yes, by restoring an earlier backup | Not necessarily |
| Reduces server downtime | Indirectly | Yes |
| Requires an administrator to act | Yes | Yes |
| Automatic failover | No | No |
Remote Backup preserves recovery points. Standby Server maintains a secondary environment that can take over from the primary server.
If data is accidentally deleted and the deletion is replicated to the standby server, the standby copy does not provide the historical version required to recover that data. A separate backup policy therefore remains essential.
Standby Server is not a two-machine deployment
A standby configuration must also be distinguished from a two-machine FileMaker Server deployment.
In a two-machine deployment, both machines participate in the normal operation of the same FileMaker Server deployment. One machine hosts the Database Server, while the secondary machine typically runs web-publishing components.
A standby server does not normally share the production workload. It remains available as a redundant server that can take over if the primary server fails.
Standby Server therefore provides redundancy, not load balancing or additional processing capacity.
What does Standby Server protect against?
Standby Server can reduce downtime caused by incidents such as:
- Hardware failure
- Operating-system failure
- Storage failure
- Loss of the primary virtual machine
- An interruption affecting the primary host
- Maintenance requiring a controlled switchover
- Loss of the primary FileMaker Server installation
Its effectiveness depends on where the standby server is deployed.
A standby server located on the same physical host may protect against the loss of a virtual machine, but not against failure of the host itself. A standby server in the same data center may protect against a server failure, but not against loss of the entire data center.
For stronger resilience, the primary and standby environments should avoid sharing the same critical points of failure.
Infrastructure and licensing requirements
Standby Server requires FileMaker Server 2026 and is sold by Claris as an optional add-on.
The add-on does not provide the secondary infrastructure itself. The organization must also provide and operate:
- A second server or virtual machine
- Sufficient processor, memory, and storage resources
- A reliable network connection between the servers
- Monitoring for both environments
- A tested switchover procedure
- The network and DNS configuration required after switchover
Claris indicates that the price of Standby Server depends on the FileMaker Server configuration. The software add-on is therefore only one component of the total cost: the secondary infrastructure and its administration must also be considered.
Standby Server and disaster recovery
Standby Server can form an important part of a Disaster Recovery Plan, but installing a secondary server is not by itself a complete plan.
A practical plan should define:
- Which incidents trigger a switchover
- Who is authorized to initiate it
- How the failure of the primary server is confirmed
- How users are redirected
- How integrations are updated
- How the standby server is monitored
- How operations return to the original or a replacement primary server
- How backups remain available throughout the incident
The procedure should be tested regularly. A standby server that has never been tested may fail precisely when it is needed.
Standby Server and fmcloud.fm
fmcloud.fm already operates a Disaster Recovery Plan based on externalized backups and the ability to redeploy FileMaker Server infrastructure in another environment.
FileMaker Standby Server provides a different and potentially faster recovery model by maintaining a second FileMaker Server installation ready for a controlled switchover.
The appropriate architecture depends on the required recovery objectives:
- How much recent data can be lost, known as the Recovery Point Objective
- How long the service may remain unavailable, known as the Recovery Time Objective
- Whether the organization requires a dedicated secondary server
- Whether the infrastructure must survive the loss of an entire data center
- The budget available for permanently maintaining redundant infrastructure
Standby Server is particularly relevant for applications where several hours of unavailability would have a significant operational impact.
Learn more
- FileMaker Server Remote Backup and Standby Server overview
- Configuring a standby server
- Configuring the primary server
- Using virtual-machine snapshots with Standby Server
- What Is FileMaker Server Remote Backup?
- What Is FileMaker Server?
- What Is a Two-Machine FileMaker Server Deployment?
- fmcloud.fm Disaster Recovery Plan
