Backups

How we keep copies of your project data — what is copied, when, how many copies are kept and how to get them back.

What is copied

The named volumes of your compose project (databases, uploads, anything you keep in volumes) and the shared folders of the project.

What is not copied

Images and source code — they are rebuilt from your repository or ZIP on the next deployment. Files written inside a container outside volumes are lost when the container is recreated: keep data in volumes.

When

Every night at 01:00 UTC. You can also make a copy at any time with “Make a copy now” on the Backups tab of the project.

How

The project containers are stopped while the copy is made and started right after it, so that a database is copied whole and not halfway through a write. At night this takes seconds to minutes.

How many copies

A project on a personal VM keeps its last 7 copies. A project on the free plan (shared VM) keeps 1.

Where

On the server that runs your VM, and a second copy on our other server in another data center. Each copy is checked with a checksum when it is written and when it is used.

Download and restore

On the Backups tab: “Download” gives a one-time link valid for an hour; “Restore” stops the project, replaces its volumes and shared folders with the copy and starts it again — you confirm it by typing the project name.

When a project is deleted

Its copies are deleted with it. Download a copy before deleting a project if you may need the data later.

Service status

Live status of the site, deployments, shared VMs and mail — on a separate server, so it keeps working when something here is down.

uptime.jambotron.com