Manage database storage and maintenance
Open Back Office → Database in the FMX EPOS desktop app on the terminal you are changing. Database changes affect every terminal and can pause trading. First finish any payments, unknown card results and print recovery, then check in the Terminals card that every online terminal runs a version of FMX EPOS with the same database model as this one.
Read the current status
Section titled “Read the current status”The Current Status card shows the active mode, whether the database can be reached, how many records on this terminal are still waiting to reach it (Pending local writes), and when it was last checked. Select Refresh Status to check again.
The Terminals card lists every terminal on the active database. For each one it shows the Version, whether its database model (Schema) is Up to date with this terminal’s, when it was Last Seen, its Pending Writes and its Maintenance answer. A terminal that has stopped reporting is marked Offline.
Terminals3
| Terminal | Version | Schema | Last Seen | Pending Writes |
|---|---|---|---|---|
| Front Till | 2.0.478 | Up to date | 14/10/2026 13:05:12 | 0 |
| Bar Till | 2.0.478 | Up to date | 14/10/2026 13:05:10 | 0 |
| Kitchen PC | 2.0.471 | Behind | Offline | — |
Illustration, not a screenshot. The real screen can differ with the theme or version.
If Review Pending Writes appears, open it before any migration, import or export. An unfinished or unknown payment or print result blocks maintenance until it is settled.
In Remote mode, Local Sensitive Data Remains means customer or order data is still in this PC’s old local database. Complete a verified Local to Remote migration before removing that local copy.
Configure storage
Section titled “Configure storage”Choose one mode under Database Storage:
- Local SQLite keeps the database on this PC in the Local SQLite File.
- Remote Database connects every terminal to SQL Server or MySQL 8.4.
Database Storage
Illustration, not a screenshot. The real screen can differ with the theme or version.
To connect to a remote database:
- Under Database Storage, choose Remote Database.
- Choose the Database Type and enter the Server Address, the Instance (SQL Server only, optional), Port, Database Name, Username and Password. With an instance name, leave Port blank to find the instance through SQL Server Browser. Choose whether to Encrypt Connection. For SQL Server, tick Trust Server Certificate only if the store has deliberately chosen to accept that server’s certificate. Connection Check Interval (5 to 300 seconds) sets how often this terminal checks that it can reach the database.
- Select Test Connection.
- Read the result: Structure Ready, Action Needed or Connection Failed.
- Select Check & Create Structure only if the selected database is meant to be a new FMX EPOS database. If it does not exist yet, FMX EPOS asks Create Database? before creating it and its tables.
- Select Save & Apply.
Connection settings belong to this terminal only. To change another terminal’s connection, do it on that terminal.
Add a Terminal
Section titled “Add a Terminal”Add a Terminal lets another PC join this till’s database through Guided Setup, without anyone typing the connection details.
- Select Generate Pairing Code. The card shows an eight-character code, this PC’s addresses under This PC and a 10-minute countdown under Expires In.
- On the new PC, in first-run setup, choose Guided Setup, Several Tills and Join Another Till, find this till or type one of its addresses, and enter the code. See Complete first-run setup.
- When the new PC has joined, the card says Code used by and the PC’s name.
Add a Terminal
Another PC joins this till’s database with a one-time code, valid for 10 minutes.
Illustration, not a screenshot. The real screen can differ with the theme or version.
Cancel withdraws the code. A code works once: it ends when a PC has used it, after five wrong attempts, when the countdown runs out or when you close the page. The card then says “The code expired.” or “The code was revoked after five wrong attempts.” Generate a new one when you need it.
Check the network type
Section titled “Check the network type”After you select Generate Pairing Code or Set Up MySQL on This PC, the card also names the networks this PC is connected to. If Windows treats one of them as a Public network, other tills cannot reach this PC on it, and the card says so. If it is the shop’s own network, select Make It Private in the desktop app and accept the Windows prompt. Or select Open Network Settings, choose Wi-Fi or Ethernet, open the network’s properties and set it to Private network. Back on the card, select Check Again.
FMX EPOS opens its firewall ports for private and domain networks only, never public ones.
If this PC’s address was set automatically by the router (DHCP), the card asks you to give the PC a fixed IP address, either by reserving its address in the router’s DHCP settings or by setting it in Windows. If the address changes, the other tills and phones lose their connection to it.
Set up MySQL on a Local SQLite till
Section titled “Set up MySQL on a Local SQLite till”A till on Local SQLite cannot share its data, so the card offers no pairing code. Instead it offers to put MySQL on this PC. The PC must run 64-bit Windows; on 32-bit Windows the card says so, and you can move the data to a database server on another PC with Data Migration instead. Windows asks for permission before MySQL is set up.
Add a Terminal
Another PC joins this till’s database with a one-time code, valid for 10 minutes.
Illustration, not a screenshot. The real screen can differ with the theme or version.
- Select Set Up MySQL on This PC. FMX EPOS first looks at what is already on this PC.
- Select the button it then offers:
- Install MySQL downloads MySQL 8.4 from Oracle (about 270 MB), installs it and opens its port to this network only. If an earlier MySQL install left databases in this till’s folder, choose Use These Databases to put MySQL back onto them, or Start Again to keep them aside, renamed with the date and time, and start with new ones.
- Prepare Database appears when MySQL is already installed. Enter its MySQL Root Password first; FMX EPOS creates the shop’s database on it.
- Continue appears when an earlier FMX EPOS installation of MySQL did not finish, and completes it.
- Wait for the progress line to finish. The remote connection fields are filled in and the Data Migration preview for Local to Remote opens. The till keeps trading on Local SQLite until you select Migrate & Switch.
- Check the preview, type
MIGRATEand select Migrate & Switch, as described under Migrate Local and Remote data below.
Once the data is on MySQL, the card offers Generate Pairing Code as usual.
This PC’s MySQL Server appears when FMX EPOS installed or prepared MySQL on this PC. Show Root Password shows the MySQL root password, which is needed only for maintenance; Hide hides it again. Each time it is shown, the audit log records it.
Remote continuity
Section titled “Remote continuity”In Remote mode, all business data is kept in the remote database. If it becomes unavailable, eligible till changes are kept on the terminal and sent once the database is back.
FMX EPOS treats the database as unavailable whenever it cannot sign in to it, so a changed database password or a renamed or removed database has the same effect as a network fault. Change those details in Database Storage on every terminal at a quiet time. A till that has already lost its connection can use Recover Connection: it finds the problem and offers what fits, such as Start MySQL or Reinstall MySQL for a server FMX EPOS installed on this PC, or Enter New Connection Details for a new address, login or password. See Recover Connection.
The Database page shows how many writes are still waiting. A write the database keeps refusing (for a reason other than being offline) is listed under Orders → Payment Review → Local Writes Needing Review. That list shows only the writes held on the terminal you are using, so open it on the terminal that recorded them. Retry Database Write tries the saved change again and never repeats a card terminal request. See Local Writes Needing Review before using Reconcile.
Choose the Emergency Terminal
Section titled “Choose the Emergency Terminal”In Remote mode, the Terminals card also has Emergency Terminal. While the database is unavailable, only that terminal can sign staff in, open tables and print kitchen tickets. Other tills keep their sales and send them once the database is back; their kitchen tickets wait until then. It is one setting for the whole store.
- Under Emergency Terminal, choose the till, or No Emergency Terminal.
- Select Save Emergency Terminal.
With No Emergency Terminal, Diagnostics warns that during an outage no terminal can sign staff in, open tables or print kitchen tickets. See Emergency terminal state.
Migrate Local and Remote data
Section titled “Migrate Local and Remote data”Data Migration copies all application records, checks the copy, switches this terminal to the new database, and only then clears the old one. Run it while the tills are idle.
- Choose Local to Remote or Remote to Local.
- Tick Replace All Application Data Already in the Target only if the target already holds data that you mean to overwrite. The preview says when the target contains data.
- Select Preview Migration.
- Check the source, target, record counts and message. You can go ahead only if the preview allows it.
- Type
MIGRATEexactly in Type MIGRATE to confirm. - Select Migrate & Switch and leave the terminal running until it reports the result.
Illustration, not a screenshot. The real screen can differ with the theme or version.
Migration pauses every terminal. After a successful switch the other terminals stay paused until an administrator moves each one to the new database from its Administrator Recovery page. Moving a terminal to another database can be done only in the desktop app on that terminal. A source that has been cleared is marked as retired. Reset Retired Database needs RESET typed to confirm, and makes a retired database usable again without deleting any records left in it.
Export data
Section titled “Export data”- Check that the active database is available.
- Select Export Data.
- Wait while every terminal pauses and the export is made.
- Save the
.eposdatafile in the store’s secure backup location.
The terminals say they are paused while the data is exported, and carry on by themselves when it finishes. An export whose file would be larger than the 512 MB import limit is refused.
The file is not encrypted and contains customer details and order history, so keep it where only trusted staff can reach it.
Export Data exports the business database only and is not a full backup of the PC. It leaves out this terminal’s licence, database connection, device and printer settings, Clover pairing, changes or emergency bills not yet sent, and customer display media. When replacing a computer, rely on the store’s normal secure backup for everything else on it.
Back up automatically
Section titled “Back up automatically”Automatic Backup, at the bottom of the page, saves an Export Data file on a schedule. It is a setting for the whole store, and the Integration Host makes the backup; the card names that till. With no Integration Host chosen, no backup is made. See Connect online ordering platforms.
Automatic Backup
The Integration Host saves an Export Data file on a schedule. Online terminals pause while the data is read. Backups do not wait for offline terminals.
Made by the Integration Host: Front Till (this terminal).
Illustration, not a screenshot. The real screen can differ with the theme or version.
- Choose the Schedule: Off, Daily or Weekly. For a weekly backup, choose the Day.
- Enter the Time. Choose a time when the shop is closed.
- Under Keep, enter how many of the newest backups to keep, from 1 to 100.
- Enter the Folder: a full path on the Integration Host’s PC, such as
D:\FMX EPOS Backups, or a network share. A copy kept away from that PC survives a broken disk. - Select Save Automatic Backup.
At the chosen time, online terminals pause while the data is read, as for Export Data; tills shown as offline (for example, switched off for the night) are not waited for. The Integration Host must be running then. If it starts within an hour of the chosen time, it still makes that backup; otherwise that backup is missed and the next scheduled one is made as usual. Older backup files beyond the Keep number are deleted from the folder; other files there are left alone. Export Data files saved by hand in that folder count as backups too, so keep them in another folder.
If the backup cannot start at that time, it is tried again within the hour: when the Integration Host is busy itself, or still has queued writes or emergency bills to send, at its next check; when another terminal does not confirm the pause, every terminal is released and the backup tries again after five minutes. A backup that starts and then fails is not tried again until the next scheduled time. Check the failure shown on the card. If the Integration Host stops during a backup, it releases the paused terminals when it starts again.
The card shows the last backup, with its file name, on every terminal. A failure shows as “Failed at” with the reason, and a missed backup as, for example, “The backup due 12/10/2026 03:30 was not made.” A failure or missed backup also shows on the Integration Host’s till and under Diagnostics → Automatic Backup until a backup succeeds.
Import and replace data
Section titled “Import and replace data”Importing replaces all application data in the active database.
Import Data
Replaces all application data after the package is checked. Up to 512 MB.
Illustration, not a screenshot. The real screen can differ with the theme or version.
- Under Import Data, choose Select File and pick a
.eposdatafile made with Export Data, up to 512 MB. It must have been made by a version of FMX EPOS with the same database model as this one. - Check the file name and size shown.
- Type
IMPORTexactly in Type IMPORT to confirm replacement. - Select Import & Replace and wait for the final message.
FMX EPOS checks the file before replacing anything. If the file is rejected, the database is left unchanged. After a successful import, the other terminals stay paused until an administrator resumes or moves each one from Administrator Recovery.
Remove an offline terminal
Section titled “Remove an offline terminal”In the Terminals card, Remove is available for any offline terminal other than this one. Confirm with Remove Terminal. It removes that terminal’s registration, its registered printers and their kitchen routes, fails any print jobs sent to those printers, and clears it as Integration Host or Emergency Terminal if it was one.
Its unsent local writes cannot be checked while it is offline. If it might come back, reconnect it and let it sync first. If it is gone for good, record that under the store’s own procedures before removing it.
Maintenance does not start
Section titled “Maintenance does not start”Migration, import, export and automatic backup all pause the terminals first. Before pausing, a terminal with local writes or emergency bills still waiting keeps sending them, and its Maintenance column reads Local writes must be synchronised first or Emergency bills must be synchronised first until they have reached the database.
FMX EPOS refuses to start maintenance while any online terminal runs a version of FMX EPOS with a different database model, does not pause, or still has an open card operation, an unknown card result, an active print job or an unknown print result. Deal with the terminal and item named in the message, then start again. For recovery after a disconnection or an uncertain save, see Database and continuity troubleshooting.