What mission-critical really means

Speaking to 120 IT managers at the IT-Lyftet conference in 2001, the IT manager at Poolia, a Swedish staffing company, put it this way:

If our clients don't get their invoice at the end of the month, they don't complain. If our staff don't get paid on exactly the 25th, they complain a little. But if a client calls to ask whether we can send them x people tomorrow and doesn't get an answer, they call someone else. The only system we have at Poolia that is mission-critical is PASS, Poolia's Administrative Support System, and it's built on FileMaker.

The quote puts a finger on something that rarely shows up in a requirements document. The mission-critical system is the one that decides whether the customer stays. The accounting system can stand still for a day. Payroll can tolerate a delay. The system where salespeople, schedulers, or case handlers answer the customer in real time tolerates no delay at all.

Systems become mission-critical over time

Many systems become mission-critical over time. Some are from day one. Far more start out as support for one department or one task. The system is extended. More people use it. More processes are connected to it. One day the business can no longer function without it, even though nobody ever made the decision that it should be that way.

That's why I build from the start as if the system were already mission-critical, both in the data structure and in how it's hosted. Anyone who postpones that question until the day the system is indispensable ends up making the decision under time pressure, often after an incident.

A structure that holds for ten years

When I design the structure of a system, I always think long-term. In relational database normalization, I keep coming back to the question "one or many." Can a company have several contact persons? Can a company have several addresses? Can a contact person have several phone numbers? Those are easy to answer yes to.

Then come the questions that separate a system that lasts from one that has to be rebuilt. Can a waste room be linked to several properties? Can one contact person belong to several companies? That's where most off-the-shelf systems give up. In a system built on FileMaker, the developer decides the data model, so even those answers can be yes without duplicate storage or free-text fields nobody can search. A wrong answer to a question like that is something the business pays for over several years, in manual double entry or in a rebuild.

Hosting FileMaker

FileMaker Server can be hosted in three ways. The choice determines who is responsible for hardware, updates, and backup.

1. Your own server on your own premises. Full control over the data, including where it physically lives. Requires in-house skills for operations, security updates, and recovery.
2. A rented server with a hosting partner. The partner handles hardware, operating system, and often FileMaker Server updates as well. Many Claris partners have built redundancy and recovery into their service.
3. Cloud hosting with FileMaker Cloud. Claris runs the infrastructure. FileMaker Cloud is certified under SOC 2 Type 2, ISO/IEC 27001, and ISO/IEC 27018. The certifications apply to the cloud service, not to a server located at the customer or at a partner.

Backup in FileMaker Server

By default, FileMaker Server runs a scheduled backup at least once a day to a separate folder on the server. The backup can be directed to a different drive, which should be the baseline in any mission-critical installation. On top of the scheduled backup, progressive backup can be enabled. It saves two copies of the changes at intervals of a few minutes, so the recovery point sits minutes behind production instead of hours.

The server that FileMaker Server runs on must also be backed up in its own right, and in the right way. A database file copied by a general-purpose backup program while FileMaker Server has it open can end up corrupted. The backup program should therefore pick up FileMaker Server's own backup files, never the live database files. That mistake is common when an IT department treats FileMaker Server like any other file server.

Backup, disaster recovery, and business continuity

Claris distinguishes three levels of protection, a breakdown that is useful when setting requirements for a hosting provider.

• A backup is a point-in-time copy of the data that can be restored if the original is lost or damaged.
• Disaster recovery is about how quickly FileMaker Server and its data can be back up after a power outage, hardware failure, or a cyberattack.
• Business continuity goes one step further: the organization keeps working while the incident is still unfolding, even if the primary server has stopped responding.

A daily backup on the same machine is enough to undo an accidental deletion. It protects against neither a fire in the server room nor ransomware that encrypts everything stored locally. Claris notes that large organizations often have a partner handle backups, while smaller organizations may have a patched-together setup that relies too heavily on local infrastructure. What's at stake differs by industry. For a staffing company like Poolia, bookings stop. For a manufacturer, the production line stops. For a healthcare provider, the practice stops while patients still need care.

The 3-2-1 rule

Claris recommends the 3-2-1 rule, which has long been the industry standard for data protection.

• Three copies of the data, counting the original as one.
• Two different types of storage media, for example a local server combined with cloud storage.
• One copy in a separate geographic location, apart from the primary server.

The local copy gives fast recovery from everyday mistakes. The offsite copy protects you if the entire location is taken out. According to Claris, the rule also improves your footing for compliance with regulations such as GDPR.

Claris specifically warns against homegrown scripts that copy files to external storage. They work until something changes: a password expires, a path moves after an update, the person who built it leaves. The failure is often discovered on the very day the copy is needed.

Remote Backup and Standby Server in FileMaker Server 2026

With FileMaker Server 2026, Claris has built in two add-ons that together cover the 3-2-1 rule without scripts or third-party tools. Both are enabled from the FileMaker Server Admin Console in a few minutes. No additional software needs to be installed.

Remote Backup copies the database files every 20 minutes to storage that Claris operates. If Encryption at Rest is enabled on the file, the copy is stored encrypted end to end. Encryption at Rest is something the developer turns on, not a default setting, which makes it worth stating as a requirement. Backup status is visible in the Admin Console, so nobody has to guess whether the backups are running.

Standby Server keeps a second server in sync with the primary. If the primary goes down, you switch over in a few minutes so staff can keep working. Before FileMaker 2026, a standby server required specialist skills and ongoing maintenance that many smaller organizations didn't have. Local backups are still needed: they are the fastest way back from an accidental deletion, while Remote Backup and Standby Server handle whatever takes out the whole server.

Three questions for your hosting partner

If a hosting partner runs FileMaker Server for you, the conversation looks a little different. Many providers have already built redundancy into their service. Claris suggests three questions to ask, whoever handles the hosting.

1. What does recovery look like if something goes wrong?
2. What are the realistic timeframes, from the alarm to staff working again?
3. Are there scenarios the current setup doesn't cover?

The answers to those questions determine whether the hosting is secure enough for your particular business. In practice, the platform's stability is the sum of three things: the server software, the operations around it, and the plan that's in place before anything happens. Claris puts the goal simply: know your plan before you need it.

The platform behind it

FileMaker is developed by Claris International Inc., a wholly owned subsidiary of Apple. Organizations have run their daily operations on the platform for more than four decades. According to Claris, Remote Backup and Standby Server are native to FileMaker Server 2026 rather than third-party integrations, with infrastructure that Claris operates itself. That means there are no external storage accounts or credentials to maintain.

FileMaker 2026 (version 26) is the current release. For an IT manager, several of its new features bear directly on the question of stability and security.

• Certification for Windows Server 2025 and an upgrade to OpenSSL 3.5 LTS.
• Multiple parallel script engine processes on the server, plus automatic restart on failure.
• Save as XML, which lets the entire structure of the system be placed under standard version control. The old objection that FileMaker lacks version control no longer holds.
• Sign-in through Claris ID with support for Okta and Microsoft Active Directory, plus OAuth 2.0 for Microsoft Azure, Google, and Amazon.

Two things I want to be clear about. Encryption at Rest on your own FileMaker Server is something the developer enables, not a default. No software can be certified as compliant with GDPR or similar regulations; FileMaker is a tool for meeting the technical requirements, which places demands on how the system is built.

Checklist for decision makers

Sources

• Claris, Keeping your Claris FileMaker solution running 24/7 is mission-critical, May 13, 2026
• Claris, Resilient businesses plan ahead. Claris FileMaker Server 2026 makes it simple., June 9, 2026
• Claris, pricing page for Remote Backup and Standby Server