Backups, restores and what fills your disk
What is backed up each day, how a restore stays safe, where the copies are kept, and the limit that stops an app’s logs from filling your server’s disk.
What is backed up every day
- Each database that 1ClickOps runs on your server.
- For an app that keeps files on your server, everything it keeps: uploads, settings and its own data. The app is paused for the moment the copy takes.
A backup is taken when none has succeeded in the last 24 hours, and you can press Back up now at any time. The 7 newest are kept on Free, 14 on Pro and 30 on Team.
How a restore stays safe
Press Restore next to a backup. The card asks Replace current data?. Press Yes, restore.
- A database backup is read from start to finish first. It is loaded into a spare database, and your real database is swapped for it only when all of it is there. If anything fails, your data is left as it was.
- For an app’s files, 1ClickOps first takes a copy of the current files, so a restore can be undone.
The steps are in Backups and restore.
Where the copies are kept
Backups are files on your own server. They never come to us. Beside each one, the card says off-site copy when a second copy exists somewhere else, or on this server only when it does not.
Logs cannot fill your disk
Docker keeps everything an app prints, for ever, unless it is told otherwise. An app that logs a lot, or crashes over and over, could slowly fill the disk, and a full disk stops every app on the server.
So every container 1ClickOps deploys keeps at most 3 log files of 10 MB each. When the newest is full, a new one starts and the oldest goes, which caps one container at about 30 MB and always leaves the newest lines to read. The limit is set at each deploy, so an app that is already running gets it the next time it is deployed. If a disk fills anyway, see When something goes wrong.