Restored bookings
Restoring a saved backup brings its listings and bookings back. This attendee list shows Jane Doe and her email on the restored Summer Concert.
Backups and restore
Download your whole database as a single zip file, restore it from the admin panel, and know that updates refuse to deploy unless a backup was taken in the last hour.
One zip, everything included
A backup exports every database table into a single zip file, with one SQL file per table and a manifest listing each table's row count. The site owner can download it from the admin panel and keep it anywhere.
Attendee personal data stays encrypted inside the backup, exactly as it is stored in the database. A copy of the backup file on its own does not reveal attendee details.
A complete local snapshot
A site can also take a complete local snapshot of its database. For a self-hoster, this means a copy of everything without working through a cloud console.
Restore from the admin panel
To restore, the owner uploads a backup zip and confirms by typing a confirmation phrase. Chobble Tickets shows what the backup contains and warns if it was made under a different database schema before anything is changed.
Each site records which version of the code it is running. A backup carries that version with it, so after a restore Chobble Tickets shows the recorded version and the matching code can be redeployed, returning data and code to the same point. A restore also refuses to load a backup made by a newer version than the one running.
Updates require a fresh backup
The update button refuses to deploy a new version unless a backup of that site's database was taken within the last hour. This means there is always a recent restore point from before any update.
The site during an update
While an update runs, the site switches to a "being updated" mode. Pages still load, but bookings, check-ins and admin changes are refused with a message asking people to try again shortly, so the database stays still while it is upgraded. Payment provider notifications that arrive during the update get a "try again later" answer, so the provider can send them again once the update is done.
If the site does not switch into that mode within about a minute, the update stops before anything changes and the site takes bookings again. If the new version does not answer correctly after it is published, the site stays in update mode rather than taking bookings on a version that may be broken.
