A regular backup allows you to restore your server after a computer crash, a failed update, or a mistaken setting change. Make a separate copy before each update.
What to copy
Stop the server and then copy:
| What to copy | Why |
|---|---|
config/application.yml | Admin, port and initial path settings. |
palmorder.sqlite | Server service data, device bindings and event log. |
data/ | Exchange files and server technical data. |
The proper inbox and outbox | If devices or default paths are set outside the server directory. |
The logs directory can be added to the backup for diagnostics, but is not required for recovery.
On macOS, the files listed are located in ~/Library/Application Support/PalmOrder Server. On Windows and the portable JVM distribution, in the PalmOrderServer directory or in the paths of your choice.
Important Do not copy
palmorder.sqlitewhile the server is running. Stop it regularly first, otherwise the backup may be incomplete.
Create a backup copy
- Stop PalmOrder Server according to how it was started.
- Create a new directory with a date like
PalmOrder-backup-2026-08-12. - Copy the files and directories listed above.
- Make sure the copy contains
palmorder.sqlite,config/application.ymland the required exchange data. - Store the backup copy separately from the server computer or on secure network storage.
If there are documents in inbox or outbox that ERP has not yet processed, restore them carefully so as not to perform the exchange again.
Update the server
Before upgrading, read the relevant release notes. If the new version contains incompatible changes, follow the instructions for that particular release.
- End current exchanges and stop the server.
- Create a backup copy.
- Download the distribution for your operating system.
- Update program files without overwriting working data unnecessarily.
- Start the server and open the control panel.
- Check the Log, license status, device list and one test exchange.
Windows
Stop the service or server from the system tray menu. Unpack the new distribution into a separate temporary directory and replace only the program files in the working directory: executables, lib, runtime, service and service scripts. Keep config, data, logs and palmorder.sqlite current.
If the config/application.yml template has changed in the new distribution, compare it with your file and manually add the necessary new parameters. Then start the service or application.
macOS
From the PalmOrder menu, select Quit to stop the server. Replace PalmOrder Server.app in the Applications folder with the new version and run it. The data in ~/Library/Application Support/PalmOrder Server is stored separately from the application and should not be overwritten.
Portable JVM and Linux systemd
Extract the new version into a separate directory. Backup config, data and palmorder.sqlite to it, and for systemd update the path in the service file if needed. Do not mix lib or runtime from different versions in the same directory.
After the launch, make sure that there is a record of a successful launch in the Log. If there is a problem, stop the server, restore the backup and refer to Logs and Support.
Restore the backup
- Stop the server.
- Put the current
config,dataandpalmorder.sqlitein a separate directory without deleting them immediately. - Restore the files from the backup to their previous locations.
- Check directory permissions, especially if the server is running as a service.
- Start the server, login to the panel and check the devices and sharing.
If restoring a copy on another computer, please coordinate with PalmOrder support first.