- Home
- Site
- Docker Compose Apps
- Backups and Restore for Docker Compose Apps
Backups and Restore for Docker Compose Apps
The Backups page shows your app's backup settings, scheduled snapshots, and manual backups.
Backups aren't included on all plans. If your team's plan doesn't include backups, the page will notify you and you won't be able to turn on a schedule.

Set the schedule
Section titled “Set the schedule”- Open your app and go to Backups.
- Click Backup Settings. Only team owners and admins see this button.
- Under Destination, choose where to store your backups.
- Under Schedule, choose Off, Daily or Hourly, and pick the time for a daily backup.
- Set Keep backups for to your preferred retention period, from 1 to 365 days.
- Click Save.
Each backup briefly pauses any services that store data without a database copy. Because hourly backups pause those services every hour, choose a daily schedule if your app serves live traffic around the clock.
Manual backups and automated safety backups (taken before changes) aren't deleted after the retention window in Keep backups for.
If several backups in a row fail, FlyWP pauses the schedule and the page says "The schedule is paused". A backup that ends well (Create Manual Backup) starts the schedule again.
Where backups are stored
Section titled “Where backups are stored”FlyWP saves each backup in a folder at your destination. The folder is named after the app's main domain.
Each backup remembers the destination it was saved to. If you later switch the app to another destination, you can still download, delete and restore the older backups.
Remove the destination
Section titled “Remove the destination”To stop backing up an app, open Backup Settings, click Delete, then click Delete Destination. FlyWP stops the backups of this app. The backups already in the list stay. You can't delete the destination while a backup or restore is running.
A backup whose destination was removed shows "Destination removed: FlyWP cannot reach this backup." Deleting it removes only its row from the list. To restore one of the other backups, set a destination first, because a restore backs up the app as it is before it starts.
What FlyWP backs up
Section titled “What FlyWP backs up”Each backup holds the Compose file, environment variables, the version, and the data in the app's volumes and folders. Team owners and admins see the full list in Backup Settings, under What FlyWP backs up. Other members see it on the Backups page.
Each item shows how FlyWP copies it, such as no downtime or brief stop, and its size. For a database, the Brief stop switch makes the services that use it stop for a moment while FlyWP copies it. FlyWP does the same when it can't read the database password.
Back up now
Section titled “Back up now”Click Create Manual Backup, then confirm. The dialog tells you which services stop for a moment. The backup appears in the list as soon as it finishes. No deploy can start until the copy ends.
Safety backups
Section titled “Safety backups”FlyWP automatically takes a safety backup before every deploy, rollback, and restore. These snapshots let you revert to the previous working state if anything goes wrong. FlyWP keeps the five newest passed and the five newest failed safety backups for deploys and rollbacks, and the same for restores.
Restore a backup
Section titled “Restore a backup”- Open your app and go to Backups.
- Find the backup you want and click Restore in its row.
- Type the app's name to confirm, then click Restore.
Restoring replaces your app's current data with the data from the backup. FlyWP takes a safety backup right before the restore, so you can go back to the state from before the restore. Because of this, the app needs a working backup destination, even if the backup you restore is in another destination.
If the app now runs a different Compose file, environment variables or images than the backup's version, the dialog tells you which version to roll back to first. See Deploys.
Delete a backup
Section titled “Delete a backup”Click Delete in a backup's row, then confirm. FlyWP removes the backup file from the destination, and it can't be restored afterwards. You can also click Download to save a backup file.
Still stuck? How can we help?
View as Markdown