.zip. Manual snapshots are available on every plan, with a daily limit per account that depends on the plan.
When to take one
- Before a deploy that changes data formats or runs migrations.
- Before a database Reset, a large import or a bulk delete.
- On a regular schedule, if the data matters to you.
Take a snapshot
1
Open the resource
Open the application or database and go to Snapshots.
2
Create it
Click Create snapshot. You can take one every 5 minutes and up to 5 a day per resource, and a number of them per day across the
account that grows with the plan (5 on Starter 1, up to 64 on Enterprise); above any of these limits the request is refused with
SNAPSHOT_RATE_LIMITED. Daily backups are automatic and don’t count.Restore
Pick a snapshot in the list and click Restore. The resource goes back to the content it had at that moment, so anything written after it is lost: take a fresh snapshot first if you may need the current state. Restores have a 30-second cooldown between them. A damaged snapshot file is refused before anything changes (INVALID_ZIP_STRUCTURE): the application’s files and the running database stay as they were.
Keep a copy outside the platform
Download any snapshot as a.zip and store it somewhere else. A download of an application
includes a vertracloud.config with its current settings, so it can be uploaded again as a new
project exactly as it was. Snapshots of any size can be downloaded. Downloading a very large project directly is refused with a clear message (DOWNLOAD_TOO_LARGE, above 300 MB of files): take a snapshot and download that instead.
Snapshot before deleting
The delete dialog for an application or a database has the option Create snapshot before deleting, off by default (it appears on plans with manual backups). When it is on, the panel creates the snapshot and deletes only if it succeeds; when it is off, the resource is deleted right away. Through the API,DELETE deletes right away: call
Create snapshot first if you want a backup. The snapshot is kept for
30 days and can be downloaded from Snapshots.
Resetting a database, deleting a whole stack and deleting a custom Docker image (which deletes its apps) still take a
safety snapshot automatically; if it fails, nothing is changed (SNAPSHOT_FAILED). When the platform deletes projects on
its own (an expired plan or an account without a plan), it also takes a snapshot first; if that fails, the project is
stopped and kept, not deleted.
Snapshot size limit
A snapshot can have at most 4 GB (the size of the snapshot file, already compressed). Above that, creating it is refused withSNAPSHOT_TOO_LARGE (HTTP 413). The limit applies to manual, daily and safety snapshots. Downloading
has no limit: any existing snapshot can be downloaded.
Automate it
Snapshots are also available through the API, the SDKs and the CLI, so a scheduled job (for example a GitHub Actions workflow with aschedule trigger) can take them on a routine.